[Desktop-packages] [Bug 1377847] Re: unity screen saver no longer blanks nor locks automatically
Still having the same problem. However, after issuing `gnome- screensaver-command -l` once, the screen saver seems to be active during the rest of the session. (Ctrl+Alt+L still doesn't work, though.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1377847 Title: unity screen saver no longer blanks nor locks automatically Status in gnome-desktop3 package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Utopic: Triaged Status in unity-settings-daemon source package in Utopic: Fix Released Bug description: After updating over the weekend the screen saver is no longer blanking or locking. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 09:44:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (472 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2013-11-10 (329 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1377847/+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 1377847] Re: unity screen saver no longer blanks nor locks automatically
Same here: No locking with Ctrl+Alt+L, on timeout or after standby. Installing light-locker didn't help either. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1377847 Title: unity screen saver no longer blanks nor locks automatically Status in “gnome-desktop3” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-desktop3” source package in Utopic: Triaged Status in “unity-settings-daemon” source package in Utopic: Fix Released Bug description: After updating over the weekend the screen saver is no longer blanking or locking. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 09:44:32 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (472 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2013-11-10 (329 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1377847/+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 1185299] Re: X crashes when attaching a monitor using the DVI interface
The issue has disappeared after I installed Bumblebee from the PPA, and the NVIDIA driver. Issue can be closed. -- 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/1185299 Title: X crashes when attaching a monitor using the DVI interface Status in “xorg-server” package in Ubuntu: Incomplete Bug description: I am having problems connecting a monitor to my Lenovo T430 using the DVI interface of the docking station. Starting X fails with a segmentation fault. This does not happen when - no external monitor is connected - the same monitor is connected to the VGA interface of either the docking station or the computer itself (when undocked) I have tested with no success: - changing the output DVI port - booting a different kernel (generic vs. lowlatency) - using nomodeset boot setting - connecting a monitor of a different kind I have attached a bad log (with the segmentation fault) and a good log (when the same monitor is connected to the VGA interface). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-22.15-lowlatency 3.8.11 Uname: Linux 3.8.0-22-lowlatency x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed May 29 09:51:47 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] InstallationDate: Installed on 2013-05-07 (21 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 2349I17 MarkForUpload: True 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.8.0-22-lowlatency root=UUID=19c36375-8b1f-494b-96a4-9b6fcd308b13 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349I17 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2349I17:pvrThinkPadT430:rvnLENOVO:rn2349I17:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2349I17 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Wed May 29 09:32:06 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1185299/+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 1185299] Re: X crashes when attaching a monitor using the DVI interface
Actually the problem disappeared after I installed drivers from the Bumblebee PPA (https://launchpad.net/~bumblebee/+archive/stable). Switching to NVIDIA finally allowed me to use switchable graphics, see http://askubuntu.com/a/303897/30266. -- 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/1185299 Title: X crashes when attaching a monitor using the DVI interface Status in “xorg-server” package in Ubuntu: New Bug description: I am having problems connecting a monitor to my Lenovo T430 using the DVI interface of the docking station. Starting X fails with a segmentation fault. This does not happen when - no external monitor is connected - the same monitor is connected to the VGA interface of either the docking station or the computer itself (when undocked) I have tested with no success: - changing the output DVI port - booting a different kernel (generic vs. lowlatency) - using nomodeset boot setting - connecting a monitor of a different kind I have attached a bad log (with the segmentation fault) and a good log (when the same monitor is connected to the VGA interface). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-22.15-lowlatency 3.8.11 Uname: Linux 3.8.0-22-lowlatency x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed May 29 09:51:47 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] InstallationDate: Installed on 2013-05-07 (21 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 2349I17 MarkForUpload: True 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.8.0-22-lowlatency root=UUID=19c36375-8b1f-494b-96a4-9b6fcd308b13 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349I17 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2349I17:pvrThinkPadT430:rvnLENOVO:rn2349I17:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2349I17 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Wed May 29 09:32:06 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1185299/+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 1185299] [NEW] X crashes when attaching a monitor using the DVI interface
Public bug reported: I am having problems connecting a monitor to my Lenovo T430 using the DVI interface of the docking station. Starting X fails with a segmentation fault. This does not happen when - no external monitor is connected - the same monitor is connected to the VGA interface of either the docking station or the computer itself (when undocked) I have tested with no success: - changing the output DVI port - booting a different kernel (generic vs. lowlatency) - using nomodeset boot setting - connecting a monitor of a different kind I have attached a bad log (with the segmentation fault) and a good log (when the same monitor is connected to the VGA interface). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-22.15-lowlatency 3.8.11 Uname: Linux 3.8.0-22-lowlatency x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed May 29 09:51:47 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] InstallationDate: Installed on 2013-05-07 (21 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 2349I17 MarkForUpload: True 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.8.0-22-lowlatency root=UUID=19c36375-8b1f-494b-96a4-9b6fcd308b13 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349I17 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2349I17:pvrThinkPadT430:rvnLENOVO:rn2349I17:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2349I17 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Wed May 29 09:32:06 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ubuntu ** Attachment added: Log with the crash https://bugs.launchpad.net/bugs/1185299/+attachment/3689480/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1185299 Title: X crashes when attaching a monitor using the DVI interface Status in “xorg” package in Ubuntu: New Bug description: I am having problems connecting a monitor to my Lenovo T430 using the DVI interface of the docking station. Starting X fails with a segmentation fault. This does not happen when - no external monitor is connected - the same monitor is connected to the VGA interface of either the docking station or the computer itself (when undocked) I have tested with no success: - changing the output DVI port - booting a different kernel (generic vs. lowlatency) - using nomodeset boot setting - connecting a monitor of a different kind I have attached a bad log (with the segmentation fault) and a good log (when the same monitor is connected to the VGA interface). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-22.15-lowlatency 3.8.11 Uname: Linux 3.8.0-22-lowlatency x86_64
[Desktop-packages] [Bug 1185299] Re: X crashes when attaching a monitor using the DVI interface
** Attachment added: Xorg.0.log with the crash (monitor attached to DVI port) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1185299/+attachment/3689501/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1185299 Title: X crashes when attaching a monitor using the DVI interface Status in “xorg” package in Ubuntu: New Bug description: I am having problems connecting a monitor to my Lenovo T430 using the DVI interface of the docking station. Starting X fails with a segmentation fault. This does not happen when - no external monitor is connected - the same monitor is connected to the VGA interface of either the docking station or the computer itself (when undocked) I have tested with no success: - changing the output DVI port - booting a different kernel (generic vs. lowlatency) - using nomodeset boot setting - connecting a monitor of a different kind I have attached a bad log (with the segmentation fault) and a good log (when the same monitor is connected to the VGA interface). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-22.15-lowlatency 3.8.11 Uname: Linux 3.8.0-22-lowlatency x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed May 29 09:51:47 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] InstallationDate: Installed on 2013-05-07 (21 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 2349I17 MarkForUpload: True 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.8.0-22-lowlatency root=UUID=19c36375-8b1f-494b-96a4-9b6fcd308b13 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349I17 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2349I17:pvrThinkPadT430:rvnLENOVO:rn2349I17:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2349I17 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Wed May 29 09:32:06 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1185299/+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 1185299] Re: X crashes when attaching a monitor using the DVI interface
** Attachment added: Xorg.0.log without the crash (monitor attached to VGA port) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1185299/+attachment/3689500/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1185299 Title: X crashes when attaching a monitor using the DVI interface Status in “xorg” package in Ubuntu: New Bug description: I am having problems connecting a monitor to my Lenovo T430 using the DVI interface of the docking station. Starting X fails with a segmentation fault. This does not happen when - no external monitor is connected - the same monitor is connected to the VGA interface of either the docking station or the computer itself (when undocked) I have tested with no success: - changing the output DVI port - booting a different kernel (generic vs. lowlatency) - using nomodeset boot setting - connecting a monitor of a different kind I have attached a bad log (with the segmentation fault) and a good log (when the same monitor is connected to the VGA interface). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-22.15-lowlatency 3.8.11 Uname: Linux 3.8.0-22-lowlatency x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed May 29 09:51:47 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] InstallationDate: Installed on 2013-05-07 (21 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 2349I17 MarkForUpload: True 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.8.0-22-lowlatency root=UUID=19c36375-8b1f-494b-96a4-9b6fcd308b13 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349I17 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2349I17:pvrThinkPadT430:rvnLENOVO:rn2349I17:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2349I17 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Wed May 29 09:32:06 2013 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1185299/+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 1179062] [NEW] OpenVPN: Buggy config dialog for Password with Certificates (TLS) authentication
Public bug reported: For an OpenVPN connection, the VPN tab of the configuration dialog is buggy when choosing Password with Certificates (TLS) authentication. Choosing a certificate file for one of the three User|CA|Private sometimes clears, sometimes sets the entries for the two other certificates that are not affected. Also, a passphrase for the private key is mandatory but shouldn't be. Another option is to use one single PKCS#12 certificate (--pkcs12 switch for /usr/sbin/openvpn). It took me two hours to figure out that the .p12 file I was given actually can be converted to three .pem files using these commands: openssl pkcs12 -nocerts -in YOUR_CERT.p12 -out userkey.pem openssl pkcs12 -nokeys -clcerts -in YOUR_CERT.p12 -out usercert.pem openssl pkcs12 -nokeys -cacerts -in YOUR_CERT.p12 -out userca.pem (taken from http://blog.stracca.net/?p=73). It would be very, very helpful to have at least a note with a helpful link in the dialog concerning PKCS#12 certificates, or, at best, if the GUI supported this type of certificate right away (perhaps through yet another authentication type Password with Certificates (TLS) with PKCS#12 key). ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1179062 Title: OpenVPN: Buggy config dialog for Password with Certificates (TLS) authentication Status in “network-manager” package in Ubuntu: New Bug description: For an OpenVPN connection, the VPN tab of the configuration dialog is buggy when choosing Password with Certificates (TLS) authentication. Choosing a certificate file for one of the three User|CA|Private sometimes clears, sometimes sets the entries for the two other certificates that are not affected. Also, a passphrase for the private key is mandatory but shouldn't be. Another option is to use one single PKCS#12 certificate (--pkcs12 switch for /usr/sbin/openvpn). It took me two hours to figure out that the .p12 file I was given actually can be converted to three .pem files using these commands: openssl pkcs12 -nocerts -in YOUR_CERT.p12 -out userkey.pem openssl pkcs12 -nokeys -clcerts -in YOUR_CERT.p12 -out usercert.pem openssl pkcs12 -nokeys -cacerts -in YOUR_CERT.p12 -out userca.pem (taken from http://blog.stracca.net/?p=73). It would be very, very helpful to have at least a note with a helpful link in the dialog concerning PKCS#12 certificates, or, at best, if the GUI supported this type of certificate right away (perhaps through yet another authentication type Password with Certificates (TLS) with PKCS#12 key). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1179062/+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 1042907] Re: LightDM doesn't handle Lock Screen or Switch Session for GNOME Shell 3.5
Works for me in Ubuntu GNOME 13.04. I have changed to lightdm using the following: apt-get install --no-install-recommends lightdm unity-greeter After that, Lock and Switch user works correctly. I have the alternative status menu plugin installed (see http://askubuntu.com/a/115207/30266), don't know if this affects matters. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1042907 Title: LightDM doesn't handle Lock Screen or Switch Session for GNOME Shell 3.5 Status in GNOME Shell: Fix Released Status in “gnome-shell” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Won't Fix Bug description: With GNOME Shell 3.5.90, gnome-shell depends on GDM or at least some GDM methods for the lock screen and user switching functionality. With GDM installed and using LightDM, it's possible to log into GNOME Shell. The Switch Session button doesn't do anything. If you lock the screen, you won't be able to unlock it. It would be great if LightDM could support this so we don't have to try to find an ugly hack to work around it. It would need to work in at least unity-greeter, but it would be cool if the KDE GTK greeters would work too as they're being shipped by Kubuntu Xubuntu. I pushed the gnome-shell packaging updates to https://code.launchpad.net/~ubuntu-desktop/gnome-shell/ubuntu ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 CheckboxSubmission: 201084ed41ea7548f8becd47fa4d1e6c CheckboxSystem: c541d13ea4f205f2fd751f76ed21105b Date: Tue Aug 28 14:50:44 2012 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1042907/+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 884666] [NEW] Mouse wheel doesn't scroll pages anymore
Public bug reported: When displaying a PDF in non-continuous mode, the mouse wheel does not scroll the pages anymore. This used to work in Natty, now it's broken in Oneiric. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/884666 Title: Mouse wheel doesn't scroll pages anymore Status in “evince” package in Ubuntu: New Bug description: When displaying a PDF in non-continuous mode, the mouse wheel does not scroll the pages anymore. This used to work in Natty, now it's broken in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/884666/+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 9441] Re: the locate pointer option breaks other keybindings
Ctrl key events are not passed to Virtualbox 4.1.2 if the Locate pointer feature is enabled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/9441 Title: the locate pointer option breaks other keybindings Status in GNOME Control Center: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Triaged Bug description: If 'Locate pointer' mouse feature is enabled (Computer-Desktop preferences-Mouse-Cursors-Locate Pointer), and you try to copy file by Ctrl+dragging, nautilus will stop responding when you release Ctrl or left mouse button to drop copy to destination folder. This effectively disables all desktop operations and panels until nautilus is killed from console. Exact sequence to reproduce: 0) Enable 'Locate pointer' mouse feature 1) press Ctrl 2) drag file to destinaton 3) release Ctrl or left mouse button You must FIRST press Ctrl, and THEN begin to drag file - if order is reverse operation will success. http://bugzilla.gnome.org/show_bug.cgi?id=125618: http://bugzilla.gnome.org/show_bug.cgi?id=125618 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/9441/+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
