[Desktop-packages] [Bug 1438306] Re: External monitors receive no signal over DisplayPort
** Changed in: xorg-server (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1438306 Title: External monitors receive no signal over DisplayPort Status in xorg-server package in Ubuntu: Invalid Bug description: Upon running updates ( which included many related to systemd - so that's my best guess as to the right package - feel free to reclassify ) I can't get an external monitor to actually receive a signal from my laptop anymore. I've tried both displayport and HDMI with no luck. You can flip the switch to turn the monitor on, but it doesn't actually send any data to the monitor ( it reports No signal ). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-5ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Mar 30 10:55:00 2015 InstallationDate: Installed on 2015-03-11 (19 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150306) MachineType: System76, Inc. Galago UltraPro ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=44e9ad95-1beb-46e2-abaf-8960ae76bcff ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1438306/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1438306] Re: External monitors receive no signal over DisplayPort
Ugh - really funky hardware issue. Sorry for the inconvenience. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1438306 Title: External monitors receive no signal over DisplayPort Status in xorg-server package in Ubuntu: New Bug description: Upon running updates ( which included many related to systemd - so that's my best guess as to the right package - feel free to reclassify ) I can't get an external monitor to actually receive a signal from my laptop anymore. I've tried both displayport and HDMI with no luck. You can flip the switch to turn the monitor on, but it doesn't actually send any data to the monitor ( it reports No signal ). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-5ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Mar 30 10:55:00 2015 InstallationDate: Installed on 2015-03-11 (19 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150306) MachineType: System76, Inc. Galago UltraPro ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=44e9ad95-1beb-46e2-abaf-8960ae76bcff ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1438306/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
I'm still seeing this issue when Google Chrome is the last open ( and focused ) application upon suspend. When I typed my password in it didn't work - so I did the switch account hack and logged in - and found my password sitting in the Chrome address bar. I've installed the latest proposed updates and have the following compiz version: $ apt-cache policy compiz compiz: Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1 Let me know if I'm missing anything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, you can't enter your password in the lockscreen. [Test case] This will work only in the case that your lockscreen is set (from unity control center, lock pane) to lock immediately (when screen turns off). 1. Open a window that will hold the grab, such as the ssh password dialog or a virtual machine (such as virtualbox in fullscreen). 2. Wait for the lock screen to activate [1]. 3. The screen won't be locked, since it's not possible to steal drag to another window. [Regression potential] For the same reason of lp:49579, we can't lock the screen (yet) if something takes the grab in X, or we won't able to get input back. This is not a regression because it has never been possible in Ubuntu before, while when we tried that, it caused this bug. A possible source of regression might be that we now try to grab/ungrab the screen (the only X reliable way for grab checking), when showing the dash/hud or the lockscreen itself, and this might slow things down a little, but from measurements done this slow down is generally about 2ms, so nothing to worry about. * Compiz Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff * [1] You can use this to reduce the locking delay: gsettings set org.gnome.desktop.session idle-delay 5 and resetting it with: gsettings reset org.gnome.desktop.session idle-delay --- Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
This also happens in Chromium. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, you can't enter your password in the lockscreen. [Test case] This will work only in the case that your lockscreen is set (from unity control center, lock pane) to lock immediately (when screen turns off). 1. Open a window that will hold the grab, such as the ssh password dialog or a virtual machine (such as virtualbox in fullscreen). 2. Wait for the lock screen to activate [1]. 3. The screen won't be locked, since it's not possible to steal drag to another window. [Regression potential] For the same reason of lp:49579, we can't lock the screen (yet) if something takes the grab in X, or we won't able to get input back. This is not a regression because it has never been possible in Ubuntu before, while when we tried that, it caused this bug. A possible source of regression might be that we now try to grab/ungrab the screen (the only X reliable way for grab checking), when showing the dash/hud or the lockscreen itself, and this might slow things down a little, but from measurements done this slow down is generally about 2ms, so nothing to worry about. * Compiz Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff * [1] You can use this to reduce the locking delay: gsettings set org.gnome.desktop.session idle-delay 5 and resetting it with: gsettings reset org.gnome.desktop.session idle-delay --- Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
And my Unity version: $ apt-cache policy unity unity: Installed: 7.2.2+14.04.20140714-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, you can't enter your password in the lockscreen. [Test case] This will work only in the case that your lockscreen is set (from unity control center, lock pane) to lock immediately (when screen turns off). 1. Open a window that will hold the grab, such as the ssh password dialog or a virtual machine (such as virtualbox in fullscreen). 2. Wait for the lock screen to activate [1]. 3. The screen won't be locked, since it's not possible to steal drag to another window. [Regression potential] For the same reason of lp:49579, we can't lock the screen (yet) if something takes the grab in X, or we won't able to get input back. This is not a regression because it has never been possible in Ubuntu before, while when we tried that, it caused this bug. A possible source of regression might be that we now try to grab/ungrab the screen (the only X reliable way for grab checking), when showing the dash/hud or the lockscreen itself, and this might slow things down a little, but from measurements done this slow down is generally about 2ms, so nothing to worry about. * Compiz Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff * [1] You can use this to reduce the locking delay: gsettings set org.gnome.desktop.session idle-delay 5 and resetting it with: gsettings reset org.gnome.desktop.session idle-delay --- Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 576648] Re: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.)
Hey Don - When your computer boots up, go ahead and make sure an Ethernet cable is plugged in. Then hold down control and alt and press F1 - you'll be prompted to login with the user account you created. Then run this command exactly: sudo apt-get install linux-headers-generic It will prompt you for your password and such. I'm not sure that will completely fix it - you may also have to remove the nvidia driver from your system as well - if that's the case type the following: sudo apt-get remove nvidia- BUT DO NOT HIT ENTER. Hit tab twice - it should show you the available packages to remove... something along the lines of nvidia-313-updates Go ahead and complete the line with whatever is shown ( ignore the packages with settings and common in the name ). Reboot and you should have you desktop back. Once you've done that you should be able to install the nvidia driver again and it should be fine - I suggest the 313 package as that is the one I've gotten to work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/576648 Title: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.) Status in NVIDIA Drivers Ubuntu: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-173” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-313-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-96” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-experimental-304” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-updates” package in Ubuntu: Triaged Bug description: WORKAROUND: Revert back to the kernel version that your Ubuntu release came with: Ubuntu 10.04 -- kernel 2.6.32 Ubuntu 11.04 -- kernel 2.6.38 TEST CASE FOR 10.04: Starting with a fresh Ubuntu 10.04.3 installation... sudo add-apt-repository ppa:kernel-ppa/ppa sudo apt-get update sudo apt-get install linux-image-3.0.0-8-generic sudo apt-get install linux-headers-3.0.0-8-generic # or should that be: install linux-lts-backport-oneiric ? # REBOOT sudo apt-get install nvidia-173 # The above command fails with an error. # Check the exact error: cat /var/lib/dkms/nvidia-173/*/build/make.log ORIGINAL DESCRIPTION: Brand new install of 10.04 onto a formatted hard drive. The upgrade icon said there was a restricted driver available - I clicked it. When I was running a Windows XP VMWare image, the video seemed to completely reset. I had to shut down and restart. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.15-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu May 6 16:43:59 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.32-21-generic, x86_64: installed nvidia-current, 195.36.15, 2.6.32-22-generic, x86_64: installed ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) MachineType: LENOVO 64576DU PackageVersion: 195.36.15-0ubuntu3 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=e48c7906-adfe-4aef-b42f-afbb2328f9c3 ro quiet splash SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 195.36.15-0ubuntu3 failed to install/upgrade: nvidia-current kernel module failed to build dmi.bios.date: 08/22/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 7LET51WW (1.21 ) dmi.board.name: 64576DU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LET51WW(1.21):bd08/22/2007:svnLENOVO:pn64576DU:pvrThinkPadT61:rvnLENOVO:rn64576DU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 64576DU dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/576648/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1100360] Re: [raring][sandybridge-m-gt2+] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001
Confirmed that it occurs with both UXA and SNA - tested with xorg-edgers PPA on raring. xserver-xorg-video-intel: Installed: 2:2.20.18-0ubuntu1 Candidate: 2:2.20.18-0ubuntu1 Version table: *** 2:2.20.18-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status 2:2.20.17+git20130110.8a8edfe4-0ubuntu0sarvatt 0 500 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ raring/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1100360 Title: [raring][sandybridge-m-gt2+] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: This looks like LP 1041790, however I am having the issues only on 13.04 (12.04, 12.10 were fine). The lockup happens several times a day and it has just happened with UXA AccelMethod too. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-intel 2:2.20.17-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Chipset: sandybridge-m-gt2+ Date: Wed Jan 16 18:25:54 2013 DistroCodename: raring DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2+] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 13.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Several times a week InstallationDate: Installed on 2013-01-04 (12 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130104) InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 1141PZ5 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-0-generic root=UUID=0e822d3c-f45d-4f15-a2c9-7968357ac544 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu4 libdrm2 2.4.40-1 xserver-xorg-video-intel 2:2.20.17-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2+] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/03/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8HET40WW(1.22) dmi.board.asset.tag: Not Available dmi.board.name: 1141PZ5 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8HET40WW(1.22):bd11/03/2011:svnLENOVO:pn1141PZ5:pvrThinkPadE420:rvnLENOVO:rn1141PZ5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1141PZ5 dmi.product.version: ThinkPad E420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1100360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 862813] Re: Power Managment settings are being ignored
Is configuring to suspend, closing power configuration, opening it again, setting to never ... able to solve the issue ? That doesn't work for me - I've tried just about every combination of opening and closing the power settings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/862813 Title: Power Managment settings are being ignored Status in “gnome-power-manager” package in Ubuntu: Confirmed Bug description: My current power settings are as follows: On Battery: Suspend when inactive for 30 minutes; Suspend when lid is closed When Plugged In: Dont suspend when inactive; dont suspend when lid is closed However, even though my Thinkpad x201 is plugged in, the settings are being ignored and the system is suspending the system after periods of inactivity. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-power-manager 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Thu Sep 29 17:33:26 2011 GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GnomeSessionSuspendInhibited: Unknown InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110915.1) MachineType: LENOVO 3626R3U ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=4757e1d7-4888-4a33-bfbe-8ec8fd9d19bc ro quiet splash vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET46WW (1.16 ) dmi.board.name: 3626R3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET46WW(1.16):bd06/07/2010:svnLENOVO:pn3626R3U:pvrThinkPadX201:rvnLENOVO:rn3626R3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3626R3U dmi.product.version: ThinkPad X201 dmi.sys.vendor: LENOVO gnome-power-bugreport: Error: [Errno 2] No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/862813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
