I was also getting random freeze (multiple times a day), and using the
ahci.mobile_lpm_policy=0 appears to solve the issue as well (didn't try another
value).
BTW, I am using Debian (kernel 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3
(2019-05-15))
Laptop: HP 15-ay005nf (core i3 5005U with Intel grap
Fixed with the next update.
** Changed in: xorg (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) => Manu Cogolludo (makova)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x
To me is bug:
On press S: open Gnome Help
On press L: open Contrast
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1574629
Title:
bug letters s and l
To manage notifications about this bug go
Exactly @OlegKrikun
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1574629
Title:
bug letters s and l
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xor
Solution at the moment :
sudo ppa-purge ppa:gnome3-team/gnome3-staging
sudo ppa-purge ppa:gnome3-team/gnome3
sudo apt-get install ubuntu-gnome-desktop^
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
bug letters s and l gnome-shell 3.20
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
BootLog:
CompizPlug
Public bug reported:
i don't know (automatic generated report)
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libgl1-mesa-dri 10.1.3-0ubuntu0.2
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nv
Public bug reported:
crashed
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic i686
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
ApportVersion: 2.13.
Public bug reported:
every time when i start ubuntu 14.04 and it is already loaded, it pops
up that ubuntu encountered an error.
ExecutablePath
/usr/share/apport/apport-gpu-error-intel.py
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-intel 2:2.99.909-0ubuntu2
Proc
I have same problem with additional symptoms as as post #9 suggested my
Xorg occasionally crashes, restarts, and I have to log back in. This is
costing me lots of WAF points at the moment. Crashes usually a few
minutes after wake from standby.
--
You received this bug notification because you are
259.49 worked for me with Nvidia Geforce 7150M / 630
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/982485
Title:
[regression] Nvidia 295.40: Unity 3D does not work at all with the new
nvidia
For me updating the driver with NVidia .run file does not work.
If I remove all nvidia drivers first, the system uses nouveau after I execute
the .run file.
If I keep the 295.33 driver and execute the .run file, the kernel module stays
in 295.33 version.
I also tried to create /etc/modprobe.d/nvi
#39 @Matt
If you can login with guest account but cannot login with your own account,
have you tried removing the .Xauthority file from your home directory? For me
messing around with these versions corrupted the Xauth files and removing them
let me login again.
Ctrl-Alt-F1
rm .Xauthority
Or y
*** This bug is a duplicate of bug 982485 ***
https://bugs.launchpad.net/bugs/982485
I pre-installed the 12.04 Beta2 system and run all the updates - there were no
problems.
After update I installed the proprietary NVidia driver (295.40) from Additional
Drivers.
The problem only exist if I a
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/986576
Title:
NVidia Driver (7150M) is broken after beta2 updates
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
Public bug reported:
I have HP Pavilion dv6500 with NVidia 7150M.
After installing Beta2 and updates the desktop does not work anymore.
Unity breaks - no bar, no panel, nothing.
If I select Unity 2D the system still works.
I propably already reported this as unity error (Bug #985768) but I now fo
*** This bug is a duplicate of bug 811762 ***
https://bugs.launchpad.net/bugs/811762
despite that its not been fixed till date. I have been having this problem
sonce last 1 yr!!!
Thank you.
Regards
--
Manu Luv Shahalia
Advocate
On Fri, Feb 10, 2012 at 9:14 AM, Daniel van Vugt wrote
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/929460
Title:
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx
kernel module failed to build
To manage notifications
Public bug reported:
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel
module failed to build
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21
Uname: Linux 2.6.32-38-gener
*** This bug is a duplicate of bug 811762 ***
https://bugs.launchpad.net/bugs/811762
no matter how many times i report this bug, i have never been presented
with a solution.
SO WHATS THE USE. UBUNTU is ignoring my problems.
Thank you.
Regards
--
Manu Luv Shahalia
Advocate
On Sat, Dec
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/902086
Title:
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx
kernel module failed to build
To manage notifications
Public bug reported:
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel
module failed to build
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-36.79-generic 2.6.32.46+drm33.20
Uname: Linux 2.6.32-36-gener
k you.
Regards
--
Manu Luv Shahalia
Advocate
On Sun, Jul 31, 2011 at 1:17 PM, Daniel van Vugt wrote:
> *** This bug is a duplicate of bug 811762 ***
>https://bugs.launchpad.net/bugs/811762
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/818455
Title:
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx
kernel module failed to build
To manage notifications
Public bug reported:
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel
module failed to build
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-33.71-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-gener
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in Ubuntu.
https://bugs.launchpad.net/bugs/818006
Title:
package nvidia-173 173.14.22-0ubuntu11 failed to install/upgrade:
nvidia-173 kernel module failed to build
T
Public bug reported:
cant update 2.6.31-14-generic
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-173 173.14.22-0ubuntu11
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Uname: Linux 2.6.31-14-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CurrentDmesg:
[ 23.2
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-96 in Ubuntu.
https://bugs.launchpad.net/bugs/818001
Title:
package nvidia-96 96.43.17-0ubuntu1 failed to install/upgrade:
nvidia-96 kernel module failed to build
To man
Public bug reported:
I cant update 2.6.31-14-generic to later.
Also, While booting, it shows "mount: mounting none on /dev failed: No such
device
init: ureadahead main process (291) terminated with status 5
.
.
.
."
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: nvidia-96 96.43.17-0ub
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/814251
Title:
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx
kernel module failed to build
To manage notifications
Public bug reported:
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel
module failed to build
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-gener
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/811762
Title:
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx
kernel module failed to build
To manage notifications
Public bug reported:
package fglrx 2:8.723.1-0ubuntu5 failed to install/upgrade: fglrx kernel
module failed to build
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-gener
Hmm it's been a while. I have sent the patch upstream, so I know it has been
fixed there.
Here is the commit msg.From e808e40278ee315eb6759dd40dc947e6fb2e642f Mon Sep 17
00:00:00 2001
From: Zhenyu Wang
Date: Wed, 11 Nov 2009 10:22:01 +0800
Subject: [PATCH] drm/i915: Fix CRT hotplug detect by che
Well if you feel like compiling your kernel you can have a look at the
patch I posted it definitely works for me, but YMMV...
--
after first splash boot, screen flickers displaying a bunch of drm: failed to
restore crtc configuration
https://bugs.launchpad.net/bugs/467841
You received this bug n
Any news on this???
--
after first splash boot, screen flickers displaying a bunch of drm: failed to
restore crtc configuration
https://bugs.launchpad.net/bugs/467841
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in ubunt
Do you use kernel modesetting? If yes you should not be able even to boot
normally, not even talking about starting Xorg, if you have the same problem.
But if i understand correctly the kms driver check if something is actually
attached to the port and if not bails out appropriately ;-)
You might
Just to be clear: I added the !IS_G33(dev) in the if clause to avoid the
detect_hotplug methode for my chipset.
--
after first splash boot, screen flickers displaying a bunch of drm: failed to
restore crtc configuration
https://bugs.launchpad.net/bugs/467841
You received this bug notification be
** Attachment added: "Patch against mainline"
http://launchpadlibrarian.net/35067134/intel_crt-no-hotplug-for-g33.patch
--
after first splash boot, screen flickers displaying a bunch of drm: failed to
restore crtc configuration
https://bugs.launchpad.net/bugs/467841
You received this bug not
I found a work-around for this bug, you can see bug #467841, at the end
there is a patch (sortof) that enables normal boot with KMS and intel
driver and X startx normally with no problem after that.
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/42
Found a work-around change in drivers/gpu/drm/i915/intel_crtc.c in function
intel_crt_detect
if (IS_I9XX(dev) && !IS_I915G(dev) && !IS_I915GM(dev) && !IS_G33(dev)) {
^^^
w
Sorry for the constant flood of mesages ;-)
But looking at the code in drivers/gpu/drm/i915 it is clear that the culprit is
the _detect_hotplug function which is called for 945 and everything
"higher". Would the temporary patch be to do _detect_ddc instead?
--
after first splash boot, s
Oh men, trying vesa driver and every thing is fine, it reads edid correctly via
edid. I had booted in single mode and with i915.modeset=0. I will try booting
directly not using kms (i915.modeset=0) and vesa to see how it goes: and it
works!
OK Next try: booting normally (no i915.modeset=0) and v
I also tried get-edid/parse-edid and it works great, I can see the modes
returned by my monitor, they look sane. So how is it that I get this
error?
--
after first splash boot, screen flickers displaying a bunch of drm: failed to
restore crtc configuration
https://bugs.launchpad.net/bugs/467841
Hmm I tried ddcprobe which gets my monitor characteristics correctly,
very odd. See attachment.
** Attachment added: "ddcprobe"
http://launchpadlibrarian.net/34888648/ddcprobe
--
after first splash boot, screen flickers displaying a bunch of drm: failed to
restore crtc configuration
https://
I think my bug is very similar to bug #429369. But it seems like this one is
still open.
Is ther anyway to tell kms or X that there is a monitor connected to VGA even
if it is not able to find one?
--
after first splash boot, screen flickers displaying a bunch of drm: failed to
restore crtc co
OK I'll also post my theory about this one.
First I obtained the xorg log by booting the kernel in recovery mode and
resuming the normal boot process to get a normal text console. No failed to
restore crtc has appeared, but the connectors have no mode is still there in
dmesg.
Then I tried startx
** Attachment added: "dmesg"
http://launchpadlibrarian.net/34885096/dmesg
--
after first splash boot, screen flickers displaying a bunch of drm: failed to
restore crtc configuration
https://bugs.launchpad.net/bugs/467841
You received this bug notification because you are a member of Ubuntu-X
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/34884955/Xorg.0.log
--
after first splash boot, screen flickers displaying a bunch of drm: failed to
restore crtc configuration
https://bugs.launchpad.net/bugs/467841
You received this bug notification because you are a member o
** Attachment added: "lspci-vvnn"
http://launchpadlibrarian.net/34884927/lspci-vvnn
--
after first splash boot, screen flickers displaying a bunch of drm: failed to
restore crtc configuration
https://bugs.launchpad.net/bugs/467841
You received this bug notification because you are a member o
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/34884897/xorg.conf
--
after first splash boot, screen flickers displaying a bunch of drm: failed to
restore crtc configuration
https://bugs.launchpad.net/bugs/467841
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I have a G33 MB, and I read all the reports with this problem, but even
now with karmic fully updated I cant get to X.
Oddly I used to be able by switching VT and it would finallyy start X but now
it is impossible.
I tried to ad
Oh well, I will not be able to comment more on this bug as my MB just died RIP
;-)
At least I can confirm that with my new one sporting an intel G33, the same
mplayer command works beautifully, so it is related to 965.
Sorry
--
XOrg freezes when playing mpeg2 file with mplayer and i965 xvmc
htt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/34505546/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/34505547/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34505548/Dependencies.txt
** A
Public bug reported:
Binary package hint: xserver-xorg-video-intel
First I can watch videos (and the mpeg2 file I used to get the freeze) using
textured Xv with no problem.
It is my first try with i965 xvmc and mplayer support for it so I cant compare
with anything.
Also the freeze is "total":
Only tested in my computer, so use it at your own risk. Open a console
and write:
cd ~
rm -f .xsession-errors
ln -s /dev/null .xsession-errors
Now .xsession-errors will always be zero size. If you ever need to check
the errors or revert this, you do 'rm -f .xsession-errors" and it will
be created
56 matches
Mail list logo
