[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
Possible duplicates: Bug #1612010 and Bug #1594989 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: [ATTENTION] This bug report is strictly for lockscreen. When user activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from indicator-session the screen should blank off after a couple seconds. The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't turn off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1292041] Re: Lockscreen doesn't turn off the screen
Same problem as everyone else: Locking the screen with Win+L turns off the monitors (I get "Signal lost" warnings on them) but after a minute or so, something turns them back on. xset q reports: DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On Note: The same happens when I force the monitors to turn off with xset dpms force off In the journal, I see these entries after shutting off the monitors at 13:57:51: Jun 21 13:58:16 linux01 /usr/lib/gdm3/gdm-x-session[2471]: (II) modeset(0): EDID vendor "HWP", prod id 12816 Jun 21 13:58:16 linux01 /usr/lib/gdm3/gdm-x-session[2471]: (II) modeset(0): Using hsync ranges from config file Jun 21 13:58:16 linux01 /usr/lib/gdm3/gdm-x-session[2471]: (II) modeset(0): Using vrefresh ranges from config file Jun 21 13:58:16 linux01 /usr/lib/gdm3/gdm-x-session[2471]: (II) modeset(0): Printing DDC gathered Modelines: Jun 21 13:58:16 linux01 /usr/lib/gdm3/gdm-x-session[2471]: (II) modeset(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP) ... Jun 21 13:58:19 linux01 gnome-shell[2611]: STACK_OP_RAISE_ABOVE: sibling window 0x54017c3 not in stack Jun 21 13:58:19 linux01 gnome-shell[2611]: STACK_OP_RAISE_ABOVE: sibling window 0x54017c3 not in stack Jun 21 13:58:19 linux01 gnome-shell[2611]: STACK_OP_RAISE_ABOVE: sibling window 0x54017c3 not in stack -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: [ATTENTION] This bug report is strictly for lockscreen. When user activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from indicator-session the screen should blank off after a couple seconds. The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't turn off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1612010] Re: Lockscreen doesn't turn off the screen
Duplicate of Bug #1292041 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1612010 Title: Lockscreen doesn't turn off the screen Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: Lockscreen doesn't turn off the screen (saw it via Bug # 1292041 now closed) Ctrl=Alt+L or Super+L shortcut works and blanks the screen requiring me to type my password again to activate session. However my System-Settings -> Brightness & Lock is set to: Turn screen off when inactive for: 30 minutes Lock: OFF Lock screen after: Screen turns off (is grayed out) Require my password when waking from suspend (unchecked and grayed out) I have dual monitors. Both are Samsung and this feature is highly intermittent, meaning sometimes it works and often it doesn't. For example it hasn't worked for days but I changed the System-Settings from 30-minutes to 1-min. and it started working without a reboot. Is it possible that a kernel update changes some value that alters the setting? Then when I change the time in the window it repopulates a value? I am on Ubuntu 16.04.1 but I have seen this issue for years now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1612010/+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 1594989] Re: Turn off screen after n minutes does not work in Ubuntu 16.04
Duplicate of Bug #1292041 https://bugs.launchpad.net/ubuntu/+source /gnome-screensaver/+bug/1292041 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1594989 Title: Turn off screen after n minutes does not work in Ubuntu 16.04 Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: After I upgraded to Ubuntu 16.04, the feature of turning off screen when inactive for a certain period of time, does not work. I have tested it several times, changing the duration, without any avail. This is happening in all the three machines I use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1594989/+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 1223181] Re: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging
Related bug in Eclipse's Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=421073 ** Bug watch added: Eclipse bugs #421073 https://bugs.eclipse.org/bugs/show_bug.cgi?id=421073 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1223181 Title: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging Status in “gtk+2.0” package in Ubuntu: Confirmed Bug description: to reproduce, I open the "Variables" view in eclipse and step through the application. the eclipse jvm crashes with: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f3dea4082aa, pid=11567, tid=139905336198912 # # JRE version: 7.0_21-b11 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgtk-x11-2.0.so.0+0x2202aa] gtk_tree_view_get_background_area+0x8a # # Core dump written. Default location: /home/juergen/core or core.11567 # # An error report file with more information is saved as: # /home/juergen/hs_err_pid11567.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # This did not happen in ubuntu 13.04. using KDE as a desktop (installed ubuntu, installed kde packages) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk2.0-0 2.24.20-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Tue Sep 10 07:25:17 2013 InstallationDate: Installed on 2010-11-24 (1020 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MarkForUpload: True SourcePackage: gtk+2.0 UpgradeStatus: Upgraded to saucy on 2013-08-29 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/+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 1035517] Re: package nvidia-current 302.17-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I just got this error after upgrading to 12.10 (quantal). My nvidia-current version is 304.51.really.304.43-0ubuntu1 I have python-xkit 0.5.0 installed The source of the problem is that the files in /usr/lib/python2.7/dist- packages/Quirks/* want "XKit" (first two letters uppercase) but the python package exports "xkit" (all lowercase). The workaround was pretty simple: Replace all "XKit" with "xkit" in all *.py files in the Quirks folder. -- 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/1035517 Title: package nvidia-current 302.17-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in “nvidia-graphics-drivers” package in Ubuntu: Expired Bug description: It appeared some python modules were not found -- Setting up nvidia-current (302.17-0ubuntu2) ... update-alternatives: using /usr/lib/nvidia-current/ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode update-alternatives: warning: skip creation of /usr/lib32/libOpenCL.so because associated file /usr/lib32/nvidia-current/libOpenCL.so (of link group i386-linux-gnu_gl_conf) doesn't exist update-alternatives: warning: skip creation of /usr/lib32/vdpau/libvdpau_nvidia.so.1 because associated file /usr/lib32/nvidia-current/vdpau/libvdpau_nvidia.so.1 (of link group i386-linux-gnu_gl_conf) doesn't exist update-alternatives: warning: skip creation of /usr/lib32/libvdpau_nvidia.so because associated file /usr/lib32/nvidia-current/vdpau/libvdpau_nvidia.so (of link group i386-linux-gnu_gl_conf) doesn't exist update-alternatives: using /usr/lib/nvidia-current/alt_ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode update-initramfs: deferring update (trigger activated) update-initramfs: Generating /boot/initrd.img-3.2.0-27-generic-pae Traceback (most recent call last): File "/usr/bin/quirks-handler", line 26, in import Quirks.quirkapplier File "/usr/lib/python2.7/dist-packages/Quirks/quirkapplier.py", line 26, in import XKit.xutils ImportError: No module named XKit.xutils dpkg: error processing nvidia-current (--configure): subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 12.10 Package: nvidia-current 302.17-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 .tmp.unity.support.test.1: ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Aug 10 19:14:42 2012 DistUpgraded: 2012-08-05 10:01:27,632 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu ErrorMessage: subprocess installed post-installation script returned error exit status 1 GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 140M] [10de:0429] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T61 [17aa:20d8] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: LENOVO 766303U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-27-generic-pae root=UUID=60fb3c3d-57ae-4168-b0fd-b0f9e63ef824 ro quiet splash vt.handoff=7 SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 302.17-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to quantal on 2012-08-05 (5 days ago) XorgConf: Section "Device" Identifier "Default Device" Option "NoLogo""True" EndSection dmi.bios.date: 05/11/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC6WW (2.26 ) dmi.board.name: 766303U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: 0372761 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC6WW(2.26):bd05/11/2009:svnLENOVO:pn766303U:pvrThinkPadT61:rvnLENOVO:rn766303U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 766303U dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1.2 version.libdrm2: libdrm2 2.4.37-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.1.902-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 version.xserver-xorg-video-ati
