[Desktop-packages] [Bug 1830914] Re: software-properties-gtk does not run at all!
** Changed in: software-properties (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1830914
Title:
software-properties-gtk does not run at all!
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
software-properties-gtk does not even start!
$ software-properties-gtk --debug
ENABLED COMPS: {'universe', 'main'}
INTERNET COMPS: {'universe', 'main'}
MAIN SOURCES
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: http://archive.ubuntu.com/ubuntu
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: http://archive.ubuntu.com/ubuntu
CHILD SOURCES
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
URI: http://archive.ubuntu.com/ubuntu
Comps: ['main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI: http://security.ubuntu.com/ubuntu/
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu|security.ubuntu.com
BaseURI: http://security.ubuntu.com/ubuntu/
URI: http://archive.ubuntu.com/ubuntu
Comps: ['universe', 'main']
Enabled: True
Valid: True
MatchURI: archive.ubuntu.com/ubuntu
BaseURI: None
CDROM SOURCES
SOURCE CODE SOURCES
DISABLED SOURCES
ISV
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 200, in __init__
self.init_livepatch()
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 1482, in init_livepatch
self.livepatch_page = LivepatchPage(self)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/LivepatchPage.py", line
51, in __init__
self._lps = LivepatchService()
File
"/usr/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line
93, in __init__
self._session = requests_unixsocket.Session()
NameError: name 'requests_unixsocket' is not defined
{Exited with code 1.}
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
$ dpkg-query -l software-properties-gtk python3-requests-unixsocket
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion Architecture Description
+++-===---===
ii python3-requests-unixsocket 0.1.5-3 all Use requests to
talk HTTP via a UNIX domain socket - Python 3.x
ii software-properties-gtk 0.97.11 all manage the
repositories that you install software from (gtk)
$ sudo apt-get update
{Works.}
$ sudo apt-get dist-upgrade
{Works.}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1830914/+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 562005] Re: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers
there is plenty of similar reports around and forums discussions about that. Why not post them here? -- 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/562005 Title: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers Status in Ubuntu Certification Programme: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Invalid Bug description: The brightness controls of laptops with NVIDIA NVS 3100M or Quadro FX 880M GPUs work while running Nouveau or when using a text mode VT, but not while running X and using proprietary NVIDIA drivers. It is possible to force the NVIDIA driver to control the backlight by adding [Option RegistryDwords EnableBrightnessControl=1] to the Devices section of xorg.conf . While this allows the backlight to be controlled, the increments are inconsistent and often result in a buzzing noise from the LED backlight on Lenovo ThinkPad T510s and W510s. Since this did not occur while running nouveau or when switching in text VT, something is wrong. This bad backlight behaviour has been confirmed on ThinkPad models T510 and W510 with NVIDIA NVS 3100m and Quadro FX 880M chipsets, respectively, via http://www.thinkwiki.org/wiki/Category:T510 Because this issue is related to NVIDIA's proprietary video driver, this issue can only be solved by them. An NVIDIA developer has said he will investigate the issues, which are discussed on the nvnews.net forums at http://www.nvnews.net/vbulletin/showthread.php?t=145105 and http://www.nvnews.net/vbulletin/showthread.php?t=150069 . For future reference, the latest NVIDIA drivers can be found in the Ubuntu X-Swat X updates PPA: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.15-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Apr 12 23:48:02 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.32-19-generic, x86_64: installed EcryptfsInUse: Yes GdmLog1: MachineType: LENOVO 4313CTO ProcCmdLine: BOOT_IMAGE=/bhostnamet/vmlinuz-2.6.32-19-generic rhostnamet=UUID=0b95b314-337f-49aa-86f9-6423e76e9f20 ro ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers XorgLogOld: dmi.bios.date: 02/22/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET49WW (1 tp-smapi, 0.40, 2.6.32-19-generic, x86_64: installed vboxnetadp, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxnetflt, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxdrv, 3.1.6, 2.6.32-19-generic, x86_64: installed.12 ) dmi.board.name: 4313CTO 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:bvr6MET49WW(1.12):bd02/22/2010:svnLENOVO:pn4313CTO:pvrThinkPadT510:rvnLENOVO:rn4313CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4313CTO dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-19-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+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 562005] Re: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers
What version is no longer supported? Really? We need to open up a new bug report for a bug that's 5 years old and counting? This has never been fixed, and likely never will be by nvidia. I'm currently on the last supported version, 340.76, in Xubuntu 14.04. Still doesn't work. But we *should* keep a bug report open on this, at least as a monument to nvidia's apathy. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Invalid = Confirmed -- 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/562005 Title: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers Status in Ubuntu Certification Programme: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: The brightness controls of laptops with NVIDIA NVS 3100M or Quadro FX 880M GPUs work while running Nouveau or when using a text mode VT, but not while running X and using proprietary NVIDIA drivers. It is possible to force the NVIDIA driver to control the backlight by adding [Option RegistryDwords EnableBrightnessControl=1] to the Devices section of xorg.conf . While this allows the backlight to be controlled, the increments are inconsistent and often result in a buzzing noise from the LED backlight on Lenovo ThinkPad T510s and W510s. Since this did not occur while running nouveau or when switching in text VT, something is wrong. This bad backlight behaviour has been confirmed on ThinkPad models T510 and W510 with NVIDIA NVS 3100m and Quadro FX 880M chipsets, respectively, via http://www.thinkwiki.org/wiki/Category:T510 Because this issue is related to NVIDIA's proprietary video driver, this issue can only be solved by them. An NVIDIA developer has said he will investigate the issues, which are discussed on the nvnews.net forums at http://www.nvnews.net/vbulletin/showthread.php?t=145105 and http://www.nvnews.net/vbulletin/showthread.php?t=150069 . For future reference, the latest NVIDIA drivers can be found in the Ubuntu X-Swat X updates PPA: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.15-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Apr 12 23:48:02 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.32-19-generic, x86_64: installed EcryptfsInUse: Yes GdmLog1: MachineType: LENOVO 4313CTO ProcCmdLine: BOOT_IMAGE=/bhostnamet/vmlinuz-2.6.32-19-generic rhostnamet=UUID=0b95b314-337f-49aa-86f9-6423e76e9f20 ro ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers XorgLogOld: dmi.bios.date: 02/22/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET49WW (1 tp-smapi, 0.40, 2.6.32-19-generic, x86_64: installed vboxnetadp, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxnetflt, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxdrv, 3.1.6, 2.6.32-19-generic, x86_64: installed.12 ) dmi.board.name: 4313CTO 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:bvr6MET49WW(1.12):bd02/22/2010:svnLENOVO:pn4313CTO:pvrThinkPadT510:rvnLENOVO:rn4313CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4313CTO dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-19-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+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 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
@dino99 This is not fixed with nvidia-340. I have Xubuntu 14.04 with nvidia-340 and nvidia-304-uvm installed from the xorg-edgers PPA. It seems nvidia- libopencl1-340 depends on nvidia-340-uvm. I just installed the 3.19.3 vivid kernel from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.3-vivid/ And got the usual error: Unpacking linux-image-3.19.3-031903-generic (3.19.3-031903.201503261036) ... Setting up linux-headers-3.19.3-031903 (3.19.3-031903.201503261036) ... Setting up linux-headers-3.19.3-031903-generic (3.19.3-031903.201503261036) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.19.3-031903-generic /boot/vmlinuz-3.19.3-031903-generic Error! Bad return status for module build on kernel: 3.19.3-031903-generic (x86_64) Consult /var/lib/dkms/nvidia-340/340.76/build/make.log for more information. I tried examining /var/lib/dkms/nvidia-340/340.76/build/make.log, but the file does not exist. The usual: $ sudo dpkg-reconfigure nvidia-340 and: $ sudo dpkg-reconfigure nvidia-340-uvm seem to have worked: $ sudo dpkg-reconfigure nvidia-340 Stopping nvidia-persistenced nvidia-persistenced: no process found Done. Removing all DKMS Modules Done. update-initramfs: deferring update (trigger activated) update-initramfs: Generating /boot/initrd.img-3.16.0-33-generic INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad Loading new nvidia-340-340.76 DKMS files... Building for 3.16.0-33-generic and 3.19.3-031903-generic Building for architecture x86_64 Building initial module for 3.16.0-33-generic Done. nvidia_340: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-33-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 3.19.3-031903-generic Done. nvidia_340: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.19.3-031903-generic/updates/dkms/ depmod DKMS: install completed. $ sudo dpkg-reconfigure nvidia-340-uvm Removing all DKMS Modules Done. Loading new nvidia-340-uvm-340.76 DKMS files... Building for 3.16.0-33-generic and 3.19.3-031903-generic Building for architecture x86_64 Building initial module for 3.16.0-33-generic Done. nvidia-340-uvm: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-33-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 3.19.3-031903-generic Done. nvidia-340-uvm: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.19.3-031903-generic/updates/dkms/ depmod DKMS: install completed. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New = Confirmed ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340-updates package in Ubuntu: New Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Bug description: **WARNING:** This bug has been widely reported and has *many* automatic subscribers. Please be considerate. **If you need help:** try searching and asking on http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a nearby user group (see http://loco.ubuntu.com or search for LUG in your area). Link back to this bug for clarity. --- This seems to fix it (at least for one version upgrade) for many people $ sudo dpkg-reconfigure nvidia-331 after that... $ sudo dpkg-reconfigure nvidia-331-uvm (some users may be on the versions of these packages suffixed with -updates ) --- **If you want to unsubscribe:** see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-331-updates/+bug/1268257/+subscribe. You can also change your settings so you don't get comments but do get notified when the bug is
[Desktop-packages] [Bug 1410548] [NEW] nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build
Public bug reported: Apport popped up a message that the nvidia driver installation failed during today's kernel update on my Xubuntu 14.04 installation. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-44-generic Date: Tue Jan 13 12:45:41 2015 InstallationDate: Installed on 2014-06-25 (202 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1410548 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: Apport popped up a message that the nvidia driver installation failed during today's kernel update on my Xubuntu 14.04 installation. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-44-generic Date: Tue Jan 13 12:45:41 2015 InstallationDate: Installed on 2014-06-25 (202 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1410548/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad
I'm seeing something similar, but noticeably different on my Thinkpad W510 (Quadro FX 880M), Nvidia 331.38, Xubuntu 14.04 amd64. Maybe once a week, while using the synaptics touchpad in firefox, the entire screen turns a solid colour, either green or grey. Switcing virtual terminals doesn't seem to work, nor does closing the lid (doesn't suspend). After unplugging and plugging my external mouse, the red light on the mouse doesn't turn back on. So this seems like more of a hard lock. All I can do is a hard reset. I was on a more recent nvidia driver until a while ago, from xorg- edgers, and I don't think I had the problem then, but it's hard to tell because it's so hard to reproduce. I had to go back to the default 331.38 for Trusty because of an OpenGL corruption problem in one of my programs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in “nvidia-graphics-drivers-319” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-331” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-343” package in Ubuntu: Triaged Status in “nvidia-prime” package in Ubuntu: Triaged Bug description: I'm using an Optimus laptop (Asus N43SL) nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is in use. Once in a while, my screen will freeze, only when I use my touchpad. This does not happen with my USB mouse. This does not happen either when I uninstall nvidia-prime and use my intel integrated graphics (HD3000). I can temporarily solve the issue by doing a VT switch. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426/+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 1068940] Re: package sni-qt 0.2.6-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is different from other instances of package sni-
I was getting the same error message while installing skype on Xubuntu 14.04 amd64. sni-qt:i386 wouldn't install as a result. Jean-Pierre's solution worked for me (although I renamed sni-qt.conf instead of deleting it outright). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sni-qt in Ubuntu. https://bugs.launchpad.net/bugs/1068940 Title: package sni-qt 0.2.6-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is different from other instances of package sni-qt:i386 Status in “sni-qt” package in Ubuntu: Confirmed Bug description: I have no desktop after the upgrade to 12.10 ProblemType: Package DistroRelease: Ubuntu 12.10 Package: sni-qt 0.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 19 22:34:48 2012 ErrorMessage: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is different from other instances of package sni-qt:i386 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: sni-qt Title: package sni-qt 0.2.6-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is different from other instances of package sni-qt:i386 UpgradeStatus: Upgraded to quantal on 2012-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sni-qt/+bug/1068940/+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 1347272] Re: Several XFCE applications appear unresponsive after communicating with a daemon
Should bug #1222356 (** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply.) perhaps be marked as a duplicate? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear unresponsive after communicating with a daemon Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Confirmed Status in xfce4-appfinder: Confirmed Status in Xfce4 Power Manager: Confirmed Status in xfce4-settings: Fix Released Status in Volume management daemon for Xfce: Confirmed Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1347272/+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 965953] Re: Indicator menus are too short and scroll when opened from screen bottom
I've had this problem for years. Currently, I'm using Xubuntu 14.04 with my panel located at the bottom edge of the screen. I see this most often with nm-applet, skype, and sometimes the sound applet. Really annoying! Thanks Lannoxx for opening a bug at GTK+'s bugzilla, and submitting the patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/965953 Title: Indicator menus are too short and scroll when opened from screen bottom Status in GTK+ GUI Toolkit: New Status in Indicator Applet: Invalid Status in “gnome-panel” package in Ubuntu: Invalid Bug description: The indicator applet, installed by default in classic session of Precise, appears with just some up and down scroll arrows, and I have to scroll down before it fills in and shows the 3 items, and then the scroll arrows disappear. Is it possible to fix this annoying behaviour? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-panel 1:3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Tue Mar 27 08:39:06 2012 SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/965953/+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 1347272] Re: Several XFCE applications appear unresponsive after communicating with a daemon
@ Alistair, I don't explicitly have Unity installed (I'm on Xubuntu 14.04), but a search via synaptic shows that I do have these Unity-related packages installed, possibly as dependencies for some piece of software I was compiling: gir1.2-unity-5.0 7.1.4+14.04.20140210-0ubuntu1 libunity-protocol-private0 7.1.4+14.04.20140210-0ubuntu1 libunity-scopes-json-def-desktop 7.1.4+14.04.20140210-0ubuntu1 libunity9 7.1.4+14.04.20140210-0ubuntu1 unity-gtk-module-common 0.0.0+14.04.20140403-0ubuntu1 unity-gtk2-module 0.0.0+14.04.20140403-0ubuntu1 unity-gtk3-module 0.0.0+14.04.20140403-0ubuntu1 Also, I don't have any overlay-scrollbar packages installed, but I do have these dbusmenu packages installed: gir1.2-dbusmenu-glib-0.4 12.10.3+14.04.20140612-0ubuntu1 libdbusmenu-qt-dev 0.9.3+14.04.20140314-0ubuntu1 libdbusmenu-qt2 0.9.3+14.04.20140314-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear unresponsive after communicating with a daemon Status in pixbuf library for gtk+: New Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Confirmed Status in xfce4-appfinder: Confirmed Status in Xfce4 Power Manager: Confirmed Status in xfce4-settings: Fix Released Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+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 1347272] Re: Several XFCE applications appear irresponsible after communicating with a daemon
It seems to me that bug #1254881 ( xfce session starts multiple instances of xfce4-power-manager and xfce4-volumed) is another duplicate, so I've marked it as such. I might be wrong though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear irresponsible after communicating with a daemon Status in pixbuf library for gtk+: New Status in One Hundred Papercuts: Triaged Status in System policy: Confirmed Status in Thunar file manager: Confirmed Status in xfce4-appfinder: Confirmed Status in Xfce4 Power Manager: Confirmed Status in xfce4-settings: Confirmed Status in Volume management daemon for XFCE 4: Invalid Status in Volume management daemon for Xfce: Confirmed Status in “gdk-pixbuf” package in Ubuntu: Triaged Status in “policykit-1” package in Ubuntu: Triaged Status in “thunar” package in Ubuntu: Triaged Status in “xfce4-appfinder” package in Ubuntu: Triaged Status in “xfce4-power-manager” package in Ubuntu: Triaged Status in “xfce4-settings” package in Ubuntu: Triaged Status in “xfce4-volumed” package in Ubuntu: Triaged Bug description: Several programs in Xfce have a daemon mode call gtk_init() before fork()ing. This is unsafe, and when it goes wrong this will typically manifest as the daemon hanging shortly after forking, and appearing to simply do nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+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 976638] Re: pkexec does not find any authentication agent
By the way, I find this is a transient issue. It went away after a reboot, but perhaps it'll come back after enough suspend/resume cycles, or on some subsequent reboot. Again, smells like a race condition. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent Status in System policy: Unknown Status in “policykit-1” package in Ubuntu: Triaged Bug description: I am using xubuntu, but I am pretty sure that other variants are affected too. My problem started with being unable to start synaptic from the menu. So far, I have found out that synaptic is started with pkexec. When I test starting pkexec /usr/sbin/synaptic in a terminal, it asks for the password in text mode. With another test pkexec --disable-internal-agent /usr/sbin/synaptic in the terminal, it says it has not found any authentication agent. I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the PC's and the laptop. Comparing the /etc directory trees of the PC's showed many differences, but I could not find anything suspicious about the polycikit configuration. For the moment, using gksu instead of pkexec is a workaround. Thanks and Regards, Markus ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: policykit-1 0.104-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 17:05:34 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120330) ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/976638/+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 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*
Thanks Alberto! OK, I've submitted a new bug report against dbus: Bug #1347272 (DBus communication problems affecting multiple packages) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1193236 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* Status in pixbuf library for gtk+: Fix Released Status in “gdk-pixbuf” package in Ubuntu: Fix Released Bug description: Since a few days, xsession-errors is fullfilled by that kind of errors: ** (nautilus:22621): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused Similar errors are reported all over the net, but Debian have tried to fix it already: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517 But some other devs seems to blame an atk-bridge: https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA And some others suggest a dbus/gdbus race; the good thing is that seems not disturbing that much the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Fri Jun 21 08:35:40 2013 MarkForUpload: True SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1193236/+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 976638] Re: pkexec does not find any authentication agent
On the advice of AlbertoSalvia Novella , I've submitted a new bug report against dbus with links to all the bugs (in my install of Xubuntu 14.04) that I vaguely suspect are related to one another: Bug #1347272 (DBus communication problems affecting multiple packages) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent Status in System policy: Unknown Status in “policykit-1” package in Ubuntu: Triaged Bug description: I am using xubuntu, but I am pretty sure that other variants are affected too. My problem started with being unable to start synaptic from the menu. So far, I have found out that synaptic is started with pkexec. When I test starting pkexec /usr/sbin/synaptic in a terminal, it asks for the password in text mode. With another test pkexec --disable-internal-agent /usr/sbin/synaptic in the terminal, it says it has not found any authentication agent. I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the PC's and the laptop. Comparing the /etc directory trees of the PC's showed many differences, but I could not find anything suspicious about the polycikit configuration. For the moment, using gksu instead of pkexec is a workaround. Thanks and Regards, Markus ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: policykit-1 0.104-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 17:05:34 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120330) ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/976638/+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 976638] Re: pkexec does not find any authentication agent
I'm seeing the same thing in Xubuntu 14.04: pkexec works in text mode, but not GUI mode. If I run it with the --disable-internal-agent flag, it raises Error executing command as another user: No authentication agent found. polkitd is running, as is polkit-gnome-authentication-agent-1. This is a fresh install. This wasn't a problem in Xubuntu 12.10. I have installed some gnome-related packages in order to compile various programs. Policykit Authentication Agent in Session Startup in the settings is enabled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent Status in “policykit-1” package in Ubuntu: Confirmed Bug description: I am using xubuntu, but I am pretty sure that other variants are affected too. My problem started with being unable to start synaptic from the menu. So far, I have found out that synaptic is started with pkexec. When I test starting pkexec /usr/sbin/synaptic in a terminal, it asks for the password in text mode. With another test pkexec --disable-internal-agent /usr/sbin/synaptic in the terminal, it says it has not found any authentication agent. I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the PC's and the laptop. Comparing the /etc directory trees of the PC's showed many differences, but I could not find anything suspicious about the polycikit configuration. For the moment, using gksu instead of pkexec is a workaround. Thanks and Regards, Markus ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: policykit-1 0.104-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 17:05:34 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120330) ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/976638/+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 976638] Re: pkexec does not find any authentication agent
I have an unsubstantiated hunch that Bug #1314782 (multimedia keys don't work when xfce4-volumed is run in daemon mode) is related. Something to do with a dbus race condition. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent Status in “policykit-1” package in Ubuntu: Confirmed Bug description: I am using xubuntu, but I am pretty sure that other variants are affected too. My problem started with being unable to start synaptic from the menu. So far, I have found out that synaptic is started with pkexec. When I test starting pkexec /usr/sbin/synaptic in a terminal, it asks for the password in text mode. With another test pkexec --disable-internal-agent /usr/sbin/synaptic in the terminal, it says it has not found any authentication agent. I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the PC's and the laptop. Comparing the /etc directory trees of the PC's showed many differences, but I could not find anything suspicious about the polycikit configuration. For the moment, using gksu instead of pkexec is a workaround. Thanks and Regards, Markus ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: policykit-1 0.104-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 17:05:34 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120330) ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/976638/+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 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*
I still get this error in Xubuntu 14.04 when I run sudo gnome-disks, and possibly other commands that I can't recall at the moment: $ sudo gnome-disks [sudo] password for mspacek: ** (gnome-disks:474): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-xW1zTsGFKW: Connection refused Bug #1314782 suggests there's a dbus race condition affecting lots of packages in Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1193236 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* Status in pixbuf library for gtk+: Fix Released Status in “gdk-pixbuf” package in Ubuntu: Fix Released Bug description: Since a few days, xsession-errors is fullfilled by that kind of errors: ** (nautilus:22621): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused Similar errors are reported all over the net, but Debian have tried to fix it already: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517 But some other devs seems to blame an atk-bridge: https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA And some others suggest a dbus/gdbus race; the good thing is that seems not disturbing that much the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Fri Jun 21 08:35:40 2013 MarkForUpload: True SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1193236/+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 1224732] Re: Custom default keyboard shortcuts don't work
Notice that I reported this bug against Unity/GNOME 3 not against Xfce4. Unless you can prove that the bugs are coming from the same /common/ code (shared by both projects), it would be nicer if you reported a new bug against Xfce4. @Edwin, yes, I noticed. You filed this bug against gnome-control-center. I might ask the same of you, to prove that these system keybinding issues are indeed due to that package, and not some other, perhaps lower level, package. Given the very similar symptoms we're seeing (or have seen), and given that not a single dev has yet to chime in, which package to file this against is anyone's guess right now. Why not pool our reasonable guesses together in one place, so that the issue gets more attention? IIRC, last time a used Trusty/Utopic the original bug wasn't present and I've never had any problem with the default shortcuts (either on Unity or Xfce4). And for that matter, I've never had problems with Xfce4 custom keyboard shortcuts. So please, report a new bug against Xfce4 if it haven't been filed before. So because you were the first to report this bug, you own it, and decide what is and isn't relevant, despite (apparently) not being a developer? Race conditions are a vicious sort of randomness. For some people, a race condition bug may never show up. For others, all the time. And for others still, only once in a while, all dependent on how the stars align on your system. You may have been in 2nd group, and then later in the 1st, while I'm in the 3rd, yet we could all easily still be subject to the same bug. You're making hasty conclusions about a complex system that no one here knows enough about. As James Cameron wrote in #28: I fixed it by delaying the xmodmap by two seconds. I speculate that the X server initialisation of keyboard mapping changed in a way to introduce a race condition, and so setting the keyboard mapping later worked around the race. So, perhaps we should add X to the packages affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+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 1224732] Re: Custom default keyboard shortcuts don't work
Martin, the bug as described in the bug description is not random and does not affect default shortcuts. Then perhaps the bug description should be ammended, given the slightly wider set of reports here from a variety of people. See my comment above on race conditions. Just because the original description fits you and Edwin best does not mean that it is fully accurate. Any other problems should be reported separately, whatever others have commented. And who is to define what exactly is a different problem? Where do you draw the line? Did your problem happen at exactly the same time of day as the original in the bug description? Did it happen on exactly the same hardware, with exactly the same configuration? If not, then I suggest you open a separate bug report. /sarcasm The answer is, devs are the only ones capable of deciding which problems are related, and which aren't. Apart from anything else it is always better to report a new bug unless it is absolutely clear that one is seeing identical symptoms to those in the bug description. It is best left to the developers to decide whether a slightly different symptom is actually caused by the same bug. References please. Who, other than a dev (at best), can be absolutely clear? If a handful of similar yet slightly different bug reports are scattered all over the place, with nothing linking them save perhaps the odd keyword, how is a dev supposed to get a handle on the scope of the problem? The slight differences can be key to solving the problem. You see them only as distraction. What you propose is fragmentation and purity. What I propose is practicality. Also unless anyone is still seeing the bug (as described at the top) on 14.04 it should probably be marked as fixed. If you'd feel inclined enough to go through some of the reports here, you'd know that the bug is alive and well in 14.04, both Ubuntu and Xubuntu. See #19, #22, #25, #27, #28, #29, plus my own (#34). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “libxkbcommon” package in Ubuntu: New Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+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 1224732] Re: Custom default keyboard shortcuts don't work
** Also affects: libxkbcommon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “libxkbcommon” package in Ubuntu: New Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+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 1224732] Re: Custom keyboard shortcuts don't work
I just hit this issue for the first time after a fresh install of Xubuntu 14.04 amd64 on a Thinkpad W510 with nvidia binaries about a week ago. At the moment, none of the shortcuts in Settings-Keyboard-Application Shortcuts work, including the few that I left at their defaults. This is after a suspend/resume cycle. I think prior to that they were fine. Note that keyboard shortcuts in Settings-Window Manager-Keyboard work fine, including the ones I customized. Also, note that I don't even have gnome-control-center installed, so I'll add xfce4-keyboard-settings to the list of affected packages. I get no error messages when I run it from the terminal and try changing keybindings. After changing them, they still don't work. xfce4-keyboard- settings probably isn't the real source of the issue, but it's a start. I'm removing custom from the bug title because it seems application shortcuts left at their defaults also don't work, for me and for others reported previously. Given the apparent randomness of this bug, is there anything I can do at the moment to help debug? Once I suspend/resume again or logout/login, it might go away. Any particular logs I should post? ** Summary changed: - Custom keyboard shortcuts don't work + Custom default keyboard shortcuts don't work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224732/+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 1224732] Re: Custom default keyboard shortcuts don't work
** Also affects: libxfce4ui Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+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 1224732] Re: Custom default keyboard shortcuts don't work
Nuts. xfce4-keyboard-settings isn't registered in launchpad for some reason, so I can't add it as an affected package. I've added libxfce4ui instead, although it needs to have a bug opened for it upstream for anyone to be notified. I couldn't find any relevant existing ones here: https://bugzilla.xfce.org/buglist.cgi?quicksearch=libxfce4ui%20shortcuts Here's a related XFCE forum posting from 2012, with a reply near the end from jeromeg, an XFCE dev: Keyboard Shortcuts not working http://forum.xfce.org/viewtopic.php?id=7138 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+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 1224732] Re: Custom default keyboard shortcuts don't work
Colin, #17 and #22 imply that default shortcuts also did not work, at least at some point. Since no one here seems to know exactly where this bug is occurring, and since it seems to be random (and therefore perhpas a race condition), it's not much of a stretch to assume that the same bug manifests slightly differently for different people. Whether a keybinding is default or customized seems unlikely to me to make much of a difference wherever these system-wide keybindings are implemented in code. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+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 1224732] Re: Custom default keyboard shortcuts don't work
FYI, suspending and resuming didn't fix the issue for me, but logging out and back in did. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+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 562005] Re: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers
For my future reference, and possibly others: After installing Xubuntu 14.04 on my Thinkpad W510, generating /etc/X11/xorg.conf with nvidia-settings and adding the EnableBrightnessControl line to the Devices section and rebooting did not work (it worked in Xubuntu 12.10). Instead, I had to create a /usr/share/X11/xorg.conf.d/10-nvidia-brightness.conf file and add the Devices section to that. It's described in this blog post: http://blog.pearce.org.nz/2012/08/enabling-external-monitor-on- lenovo.html You should probably change the BoardName to whatever it is for your system (mine is Quadro FX 880M). -- 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/562005 Title: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers Status in Ubuntu Certification Programme: Invalid Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Bug description: The brightness controls of laptops with NVIDIA NVS 3100M or Quadro FX 880M GPUs work while running Nouveau or when using a text mode VT, but not while running X and using proprietary NVIDIA drivers. It is possible to force the NVIDIA driver to control the backlight by adding [Option RegistryDwords EnableBrightnessControl=1] to the Devices section of xorg.conf . While this allows the backlight to be controlled, the increments are inconsistent and often result in a buzzing noise from the LED backlight on Lenovo ThinkPad T510s and W510s. Since this did not occur while running nouveau or when switching in text VT, something is wrong. This bad backlight behaviour has been confirmed on ThinkPad models T510 and W510 with NVIDIA NVS 3100m and Quadro FX 880M chipsets, respectively, via http://www.thinkwiki.org/wiki/Category:T510 Because this issue is related to NVIDIA's proprietary video driver, this issue can only be solved by them. An NVIDIA developer has said he will investigate the issues, which are discussed on the nvnews.net forums at http://www.nvnews.net/vbulletin/showthread.php?t=145105 and http://www.nvnews.net/vbulletin/showthread.php?t=150069 . For future reference, the latest NVIDIA drivers can be found in the Ubuntu X-Swat X updates PPA: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.15-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Apr 12 23:48:02 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.32-19-generic, x86_64: installed EcryptfsInUse: Yes GdmLog1: MachineType: LENOVO 4313CTO ProcCmdLine: BOOT_IMAGE=/bhostnamet/vmlinuz-2.6.32-19-generic rhostnamet=UUID=0b95b314-337f-49aa-86f9-6423e76e9f20 ro ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers XorgLogOld: dmi.bios.date: 02/22/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET49WW (1 tp-smapi, 0.40, 2.6.32-19-generic, x86_64: installed vboxnetadp, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxnetflt, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxdrv, 3.1.6, 2.6.32-19-generic, x86_64: installed.12 ) dmi.board.name: 4313CTO 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:bvr6MET49WW(1.12):bd02/22/2010:svnLENOVO:pn4313CTO:pvrThinkPadT510:rvnLENOVO:rn4313CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4313CTO dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-19-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+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 1281019] Re: 10de:0dda [HP EliteBook 8560w] Brightness controls are not working nvidia-319 and nvidia-331
Ingo Gerth, is this a new problem that occurs only in the more recent nvidia blobs, or does it also occur with older ones (say 304)? If the latter, since you have a Quadro 2000M, this bug should probably be marked as a duplicate of Bug #562005: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/562005 -- 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/1281019 Title: 10de:0dda [HP EliteBook 8560w] Brightness controls are not working nvidia-319 and nvidia-331 Status in “xorg” package in Ubuntu: Incomplete Bug description: The Brightness keys (FN+F9 and FN+FN10) are doing 'something' in the right corner of the screen the brightness control window does show-up and changes, but the brightness of the screen itself does not via Nvidia drivers version 319 or 331. There is the bugreport at the official Nvidia forums: https://devtalk.nvidia.com/default/topic/539462/linux/-nvidia-319-12-brightness-controls-not-working-on-laptop-ubuntu-13-03-/2/ ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia appassure_vss .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is een map: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 17 10:05:44 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: appassure-vss, 5.3.6, 3.11.0-15-generic, x86_64: installed nvidia-331, 331.38, 3.11.0-15-generic, x86_64: installed nvidia-331-uvm, 331.38, 3.11.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1631] MachineType: Hewlett-Packard HP EliteBook 8560w MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=caf0bb2d-fbef-46ff-be64-0ec601243262 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt~saucy version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.0~git20140215.1020d893-0ubuntu0sarvatt~saucy version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.0~git20140215.1020d893-0ubuntu0sarvatt~saucy version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.99+git20140206.8de6f7b2-0ubuntu0sarvatt~saucy version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910+git20140210.5142d1ca-0ubuntu0sarvatt~saucy version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9+git20130730.300c5a32-0ubuntu0sarvatt xserver.bootTime: Mon Feb 17 10:03:57 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1281019/+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 562005] Re: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers
I just tried messing with nvidiabl for my Thinkpad W510, without success. I've opened a bug report here: https://github.com/guillaumezin/nvidiabl/issues/89 -- 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/562005 Title: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers Status in Ubuntu Certification Programme: Invalid Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Bug description: The brightness controls of laptops with NVIDIA NVS 3100M or Quadro FX 880M GPUs work while running Nouveau or when using a text mode VT, but not while running X and using proprietary NVIDIA drivers. It is possible to force the NVIDIA driver to control the backlight by adding [Option RegistryDwords EnableBrightnessControl=1] to the Devices section of xorg.conf . While this allows the backlight to be controlled, the increments are inconsistent and often result in a buzzing noise from the LED backlight on Lenovo ThinkPad T510s and W510s. Since this did not occur while running nouveau or when switching in text VT, something is wrong. This bad backlight behaviour has been confirmed on ThinkPad models T510 and W510 with NVIDIA NVS 3100m and Quadro FX 880M chipsets, respectively, via http://www.thinkwiki.org/wiki/Category:T510 Because this issue is related to NVIDIA's proprietary video driver, this issue can only be solved by them. An NVIDIA developer has said he will investigate the issues, which are discussed on the nvnews.net forums at http://www.nvnews.net/vbulletin/showthread.php?t=145105 and http://www.nvnews.net/vbulletin/showthread.php?t=150069 . For future reference, the latest NVIDIA drivers can be found in the Ubuntu X-Swat X updates PPA: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.15-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Apr 12 23:48:02 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.32-19-generic, x86_64: installed EcryptfsInUse: Yes GdmLog1: MachineType: LENOVO 4313CTO ProcCmdLine: BOOT_IMAGE=/bhostnamet/vmlinuz-2.6.32-19-generic rhostnamet=UUID=0b95b314-337f-49aa-86f9-6423e76e9f20 ro ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers XorgLogOld: dmi.bios.date: 02/22/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET49WW (1 tp-smapi, 0.40, 2.6.32-19-generic, x86_64: installed vboxnetadp, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxnetflt, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxdrv, 3.1.6, 2.6.32-19-generic, x86_64: installed.12 ) dmi.board.name: 4313CTO 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:bvr6MET49WW(1.12):bd02/22/2010:svnLENOVO:pn4313CTO:pvrThinkPadT510:rvnLENOVO:rn4313CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4313CTO dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-19-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+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 1281019] Re: 10de:0dda [HP EliteBook 8560w] Brightness controls are not working nvidia-319 and nvidia-331
** Changed in: xorg (Ubuntu) Status: Incomplete = Confirmed -- 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/1281019 Title: 10de:0dda [HP EliteBook 8560w] Brightness controls are not working nvidia-319 and nvidia-331 Status in “xorg” package in Ubuntu: Confirmed Bug description: The Brightness keys (FN+F9 and FN+FN10) are doing 'something' in the right corner of the screen the brightness control window does show-up and changes, but the brightness of the screen itself does not via Nvidia drivers version 319 or 331. There is the bugreport at the official Nvidia forums: https://devtalk.nvidia.com/default/topic/539462/linux/-nvidia-319-12-brightness-controls-not-working-on-laptop-ubuntu-13-03-/2/ ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia appassure_vss .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is een map: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 17 10:05:44 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: appassure-vss, 5.3.6, 3.11.0-15-generic, x86_64: installed nvidia-331, 331.38, 3.11.0-15-generic, x86_64: installed nvidia-331-uvm, 331.38, 3.11.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1631] MachineType: Hewlett-Packard HP EliteBook 8560w MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=caf0bb2d-fbef-46ff-be64-0ec601243262 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt~saucy version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.0~git20140215.1020d893-0ubuntu0sarvatt~saucy version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.0~git20140215.1020d893-0ubuntu0sarvatt~saucy version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.99+git20140206.8de6f7b2-0ubuntu0sarvatt~saucy version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910+git20140210.5142d1ca-0ubuntu0sarvatt~saucy version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9+git20130730.300c5a32-0ubuntu0sarvatt xserver.bootTime: Mon Feb 17 10:03:57 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1281019/+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 1214508] Re: nvidia-settings =319 segfaults on close
** Summary changed: - nvidia-settings segfaults on close after official update of drivers from 310 to 319 + nvidia-settings =319 segfaults on close -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-settings-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1214508 Title: nvidia-settings =319 segfaults on close Status in “nvidia-settings-319-updates” package in Ubuntu: Confirmed Bug description: After installation of the latest updates of the nvidia proprietary blob from 310.14 to 319.32 nvidia-settings crashes when pressing the quit button. dmesg shows this: [ 95.183668] nvidia-settings[2292]: segfault at 7f650be5c8a0 ip 7f650be5c8a6 sp 7fff69e6f5b8 error 7 in libpixbufloader-xpm.so[7f650be58000+6000] and this: [ 459.549845] nvidia-settings[3534]: segfault at 7f88dba4c8a0 ip 7f88dba4c8a6 sp 761e6b98 error 7 in libpixbufloader- xpm.so[7f88dba48000+6000] Crash reports are caught by apport and sent (I hope) to Canonical ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-settings-experimental-310 319.32-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17 Uname: Linux 3.5.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Tue Aug 20 20:48:24 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings-319-updates UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings-319-updates/+bug/1214508/+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 1214508] Re: nvidia-settings =319 segfaults on close
I just marked a few other bugs as duplicates of this. As I wrote in one of them, I see this in nvidia-settings 331.20 on my Thinkpad W510 (Nvidia Quadro FX 880M) on Xubuntu 12.10, using the xorg-edgers PPA, which brings in Linux 3.7.0.7-generic. I'm pretty sure I don't see this on Xubuntu 13.10, with the same version 331.20 of nvidia-settings, using the ubuntu-x-swat/x-updates PPA. Maybe this suggests the specific version of some pixbuf library is the culprit. User ssm suggests it's gtk2-engines-pixbuf (https://bugs.launchpad.net/ubuntu/+source/nvidia- settings/+bug/1268027/comments/21). Here's what I get in Xubuntu 12.10 while running it in gdb and then hitting close: user@box:~$ gdb nvidia-settings GNU gdb (GDB) 7.5-ubuntu Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/nvidia-settings...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/nvidia-settings [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffecb5d700 (LWP 3402)] [New Thread 0x7fffe7fff700 (LWP 3403)] Program received signal SIGILL, Illegal instruction. 0x7fffd6e46909 in ?? () from /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so (gdb) q A debugging session is active. Inferior 1 [process 3399] will be killed. Quit anyway? (y or n) y -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-settings-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1214508 Title: nvidia-settings =319 segfaults on close Status in “nvidia-settings-319-updates” package in Ubuntu: Confirmed Bug description: After installation of the latest updates of the nvidia proprietary blob from 310.14 to 319.32 nvidia-settings crashes when pressing the quit button. dmesg shows this: [ 95.183668] nvidia-settings[2292]: segfault at 7f650be5c8a0 ip 7f650be5c8a6 sp 7fff69e6f5b8 error 7 in libpixbufloader-xpm.so[7f650be58000+6000] and this: [ 459.549845] nvidia-settings[3534]: segfault at 7f88dba4c8a0 ip 7f88dba4c8a6 sp 761e6b98 error 7 in libpixbufloader- xpm.so[7f88dba48000+6000] Crash reports are caught by apport and sent (I hope) to Canonical ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-settings-experimental-310 319.32-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17 Uname: Linux 3.5.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Tue Aug 20 20:48:24 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings-319-updates UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings-319-updates/+bug/1214508/+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 1218408] Re: nvidia-settings 319.32 Crash on exit (segmentation fault) (core dumped)
*** This bug is a duplicate of bug 1214508 *** https://bugs.launchpad.net/bugs/1214508 ** This bug has been marked a duplicate of bug 1214508 nvidia-settings =319 segfaults on close -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-settings-319 in Ubuntu. https://bugs.launchpad.net/bugs/1218408 Title: nvidia-settings 319.32 Crash on exit (segmentation fault) (core dumped) Status in “nvidia-settings-319” package in Ubuntu: Confirmed Bug description: Ubuntu 12.04.3 Nvidia GTX 460 768MB BUG: Nvidia 319.32 (Current-319-Updates) X Server Settings is hanging and then crashing on Exit. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-settings (not installed) ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17 Uname: Linux 3.5.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Thu Aug 29 17:17:50 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True SourcePackage: nvidia-settings-304 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings-319/+bug/1218408/+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 1214508] Re: nvidia-settings =319 segfaults on close
seems to apply to all versions since 319 ** Package changed: nvidia-settings-319-updates (Ubuntu) = nvidia- settings (Ubuntu) ** Also affects: nvidia-drivers-ubuntu Importance: Undecided Status: New ** No longer affects: nvidia-drivers-ubuntu ** Also affects: gdk-pixbuf Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-settings-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1214508 Title: nvidia-settings =319 segfaults on close Status in pixbuf library for gtk+: New Status in “nvidia-settings” package in Ubuntu: Confirmed Bug description: After installation of the latest updates of the nvidia proprietary blob from 310.14 to 319.32 nvidia-settings crashes when pressing the quit button. dmesg shows this: [ 95.183668] nvidia-settings[2292]: segfault at 7f650be5c8a0 ip 7f650be5c8a6 sp 7fff69e6f5b8 error 7 in libpixbufloader-xpm.so[7f650be58000+6000] and this: [ 459.549845] nvidia-settings[3534]: segfault at 7f88dba4c8a0 ip 7f88dba4c8a6 sp 761e6b98 error 7 in libpixbufloader- xpm.so[7f88dba48000+6000] Crash reports are caught by apport and sent (I hope) to Canonical ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-settings-experimental-310 319.32-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17 Uname: Linux 3.5.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Tue Aug 20 20:48:24 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings-319-updates UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1214508/+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 930563] Re: NM Applet menu entries not responding
*** This bug is a duplicate of bug 1011073 *** https://bugs.launchpad.net/bugs/1011073 David, I would hazard it's marked as low importance because fixing it wouldn't be as sexy and controversial as, say, Ubuntu Edge, or Mir, or Unity. It would, however, be damned well useful. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/930563 Title: NM Applet menu entries not responding Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: When i click on the NM applet, the menu appears correct but when i click eg on disconnect or edit connection, nothing happens. This is the behavior for all menu entries. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.2.0+git.20120126t000800.5151959-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic-pae 3.2.5 Uname: Linux 3.2.0-15-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sat Feb 11 09:04:44 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) IpRoute: default via 192.168.178.1 dev wlan0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.20 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-02-03 (8 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.3.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/930563/+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 1011073] Re: NetworkManager submenus sometimes unpopulated
@mdeslaur, will Quantal get fixed too? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated Status in DBus Menu: New Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: New Status in OEM Priority Project quantal series: New Status in OEM Priority Project raring series: Triaged Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “network-manager-applet” package in Ubuntu: Invalid Status in “libdbusmenu” source package in Precise: Triaged Status in “network-manager-applet” source package in Precise: Invalid Status in “libdbusmenu” source package in Quantal: Triaged Status in “network-manager-applet” source package in Quantal: Invalid Status in “libdbusmenu” source package in Raring: Triaged Status in “network-manager-applet” source package in Raring: Invalid Bug description: [Impact] * Affected applications with a high number of menu updates reach the maximum value allowed for the ID of a menuitem, and rejects further menu changes. Because the application underneath the menu has already removed the underlying actual GtkMenuItem objects, it is impossible to activate the items -- to effect the actions linked to the menuitems. * Some indicators have a relatively high and climbing memory usage due to the way they build menus to be displayed in the panel. [Test Case] * Run nm-applet for a while (multiple days without shutdown, without killing the application), notice whether the menus are still usable. * Run indicators for a while, observe memory usage. [Regression Potential] Indicators with a very high amount of updates may be affected as circling back past the maximum value, if a new menu item is created with an ID still in use by a menuitem that has not been removed yet, neither or only one of the two menu items might be available to be clicked -- this could confuse users or cause error messages to be displayed. Risk is low however since network-manager-gnome (nm-applet) is currently the application with the most menu updates. [Other Info] Submenus in Network Manager are sometimes unusable as they are not populated. This happens both with the list of available networks and with the VPN list. When the bug happens, it occurs for *both* the wireless submenu and the VPN menu. I know there are entries for those submenus as I can see them with other network UI mechanisms. The issue is intermittent. Expected: Dropping down the menu then hovering over the submenu trigger-point (example: More networks) shows the additional expected entries (example: more wifi networks to choose from). Actual: Dropping down the menu and hovering over the submenu trigger displays a submenu but the submenu has nothing in it and is unusable. Ubuntu 12.04 network-manager 0.9.4.0-0ubuntu4.1 Apple Macbook Pro 8,1 03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe (rev 10) To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1011073/+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 562005] Re: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers
Xubuntu 12.10 updated to nvidia 304.88 a day or so ago, and now brightness controls are even more uneven than before. I've tried regenerating xorg.conf using nvidia-settings, and re-adding [Option RegistryDwords EnableBrightnessControl=1] to the Device section, but that hasn't helped. I also tried nvidia 313.30 from xorg-edgers, but brightness controls seemed to be just as uneven. 3 years and this still hasn't been fixed. I'm waiting hopefully for nouveau to finally implement proper power management implemented, so I can ditch this nvidia crap for good. Linus perfectly expressed my frustration with this company with his simple gesture: http://www.youtube.com/watch?v=YxHqi8tx048 -- 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/562005 Title: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers Status in Ubuntu Certification Programme: Invalid Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Bug description: The brightness controls of laptops with NVIDIA NVS 3100M or Quadro FX 880M GPUs work while running Nouveau or when using a text mode VT, but not while running X and using proprietary NVIDIA drivers. It is possible to force the NVIDIA driver to control the backlight by adding [Option RegistryDwords EnableBrightnessControl=1] to the Devices section of xorg.conf . While this allows the backlight to be controlled, the increments are inconsistent and often result in a buzzing noise from the LED backlight on Lenovo ThinkPad T510s and W510s. Since this did not occur while running nouveau or when switching in text VT, something is wrong. This bad backlight behaviour has been confirmed on ThinkPad models T510 and W510 with NVIDIA NVS 3100m and Quadro FX 880M chipsets, respectively, via http://www.thinkwiki.org/wiki/Category:T510 Because this issue is related to NVIDIA's proprietary video driver, this issue can only be solved by them. An NVIDIA developer has said he will investigate the issues, which are discussed on the nvnews.net forums at http://www.nvnews.net/vbulletin/showthread.php?t=145105 and http://www.nvnews.net/vbulletin/showthread.php?t=150069 . For future reference, the latest NVIDIA drivers can be found in the Ubuntu X-Swat X updates PPA: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.15-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Apr 12 23:48:02 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.32-19-generic, x86_64: installed EcryptfsInUse: Yes GdmLog1: MachineType: LENOVO 4313CTO ProcCmdLine: BOOT_IMAGE=/bhostnamet/vmlinuz-2.6.32-19-generic rhostnamet=UUID=0b95b314-337f-49aa-86f9-6423e76e9f20 ro ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers XorgLogOld: dmi.bios.date: 02/22/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET49WW (1 tp-smapi, 0.40, 2.6.32-19-generic, x86_64: installed vboxnetadp, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxnetflt, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxdrv, 3.1.6, 2.6.32-19-generic, x86_64: installed.12 ) dmi.board.name: 4313CTO 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:bvr6MET49WW(1.12):bd02/22/2010:svnLENOVO:pn4313CTO:pvrThinkPadT510:rvnLENOVO:rn4313CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4313CTO dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-19-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+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 933300] Re: nm-applet needs restart after resume
*** This bug is a duplicate of bug 780602 *** https://bugs.launchpad.net/bugs/780602 ** This bug has been marked a duplicate of bug 780602 nm-applet leaks memory and stops functioning after a while -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/933300 Title: nm-applet needs restart after resume Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: STR: 1) Resume from suspend, nm-applet displays no network connection (that has been the case on this computer for a long while, other computers on my network reconnect automatically) 2) Click on nm-applet and select the network ER: * nm applet starts animating and connects AR: * Nothing happens. I need to `pkill nm-applet nm-applet `, then I can choose my network and continue. I'm not sure when it started, I think only a few days ago ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.2.0+git.20120126t000800.5151959-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5 Uname: Linux 3.2.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CheckboxSubmission: f26299558349e6bfa9a64225e1770925 CheckboxSystem: 669b662da410063cc918e0f60cf6cddf Date: Thu Feb 16 08:45:17 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100224.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.10 metric 2 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-01-16 (30 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.3.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/933300/+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 1117730] Re: nm-applet becomes unresponsive to interactions and submenus such as 'VPN Connections' show completely empty
** Summary changed:
- nm-applet becomes unresponsive to interactions and submenus such as 'VPN
Connections' show completly empty
+ nm-applet becomes unresponsive to interactions and submenus such as 'VPN
Connections' show completely empty
** Changed in: oem-priority/quantal
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1117730
Title:
nm-applet becomes unresponsive to interactions and submenus such as
'VPN Connections' show completely empty
Status in OEM Priority Project:
Confirmed
Status in OEM Priority Project precise series:
New
Status in OEM Priority Project quantal series:
Confirmed
Status in OEM Priority Project raring series:
New
Status in “network-manager-applet” package in Ubuntu:
Confirmed
Bug description:
broken out of bug 780602, because we believe the root cause to be
different. From that bug report:
I experience exactly the same symptoms as the bug report description
has.
After some time nm-applet stops reacting to user input and submenu
entries do not populate. This is with latest 12.10 packages.
I noticed that the indicator tries to get the menu but it fails -
dbus-monitor output below:
method call sender=:1.12 - dest=:1.67 serial=14296
path=/com/canonical/Unity/Panel/Service;
interface=com.canonical.Unity.Panel.Service; member=ShowEntry
string 0x26ef470
uint32 0
int32 1147
int32 24
uint32 1
uint32 1356027813
method return sender=:1.67 - dest=:1.12 reply_serial=14296
method call sender=:1.67 - dest=:1.14 serial=107621
path=/org/ayatana/NotificationItem/nm_applet/Menu;
interface=com.canonical.dbusmenu; member=AboutToShowGroup
array [
int32 80799
]
error sender=:1.14 - dest=:1.67
error_name=org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0
reply_serial=107621
string The IDs supplied '[80799]' do not refer to any menu items we have
When some item is clicked (e.g. disconnect for current wifi AP) the following
happens:
signal sender=:1.67 - dest=(null destination) serial=107704
path=/com/canonical/Unity/Panel/Service;
interface=com.canonical.Unity.Panel.Service; member=EntryActivated
string
struct {
int32 0
int32 0
uint32 0
uint32 0
}
method call sender=:1.67 - dest=:1.14 serial=107705
path=/org/ayatana/NotificationItem/nm_applet/Menu;
interface=com.canonical.dbusmenu; member=EventGroup
array [
struct {
int32 80846
string clicked
variant int32 0
uint32 106251172
}
]
error sender=:1.14 - dest=:1.67
error_name=org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0
reply_serial=107705
string The IDs supplied '[80846]' do not refer to any menu items we have
So this looks like like dbus menu is losing the IDs or nm-applet is
using the ids that are no longer valid.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1117730/+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 930563] Re: NM Applet menu entries not responding
@hadware, #27: Apparently this problem only appears after an upgrade.It seems I never got this kind of problem with fresh installs, and people here appear to be in the same situation... Not true. I have this bug, with the very same dbus-monitor reports as in #8, on my fresh Xubuntu 12.10 install on a Thinkpad W510. As others have mentioned, this seems to happen after one (or maybe several) suspend- resume cycles. In fact, I've had this bug for years, I think starting from a fresh install of Ubuntu 11.04. Sad really... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/930563 Title: NM Applet menu entries not responding Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: When i click on the NM applet, the menu appears correct but when i click eg on disconnect or edit connection, nothing happens. This is the behavior for all menu entries. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.2.0+git.20120126t000800.5151959-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic-pae 3.2.5 Uname: Linux 3.2.0-15-generic-pae i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sat Feb 11 09:04:44 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) IpRoute: default via 192.168.178.1 dev wlan0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.20 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: Upgraded to precise on 2012-02-03 (8 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.3.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/930563/+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 780602] Re: nm-applet leaks memory and stops functioning after a while
What's the status of this bug for quantal? Surely if there's a fix for precise, there should be one for quantal, no? In Xubuntu 12.10, after a day of running on WiFi, my submenus still show up as empty and the network shows as disconnected, even though I'm still connected to the same access point and networking still works. Also, more recently I've noticed that the nm-applet status icon in the indicator plugin stops showing signal levels around the same time, or maybe a few days later (I'm using the dark Blackbird theme). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory and stops functioning after a while Status in OEM Priority Project: Fix Committed Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project quantal series: Fix Committed Status in “network-manager-applet” package in Ubuntu: Fix Released Status in “network-manager-applet” source package in Precise: Fix Committed Status in “network-manager-applet” source package in Quantal: Incomplete Bug description: [Impact] This issue affects most and any users of nm-applet, especially in environments (such as offices) where the detected wireless networks change a lot, and where roaming can occur frequently. [Test Case] Run nm-applet for multiple hours: - Observe that the VPN Connections submenu still opens and lists connections (if VPN connections are configured) - Observe that the More networks submenu for additional detected wireless networks still opens and lists networks. A common failure case is where such a submenu will open but show an empty list (a piece of menu a few milimeters long). [Regression Potential] Minimal, the fixes have been available for a while in the development release (and in other recent releases) with no regressions; furthermore, this corrects obviously wrong memory handling without changing the effective behavior of the application. Possible issues could be introducing new memory leaks with the changes however, and although the risk is minimal, this could cause the same failure behavior as listed above under [Test Case]. -- nm-applet leaks memory in a fresh install of Natty, increasing to over 200 Mb in 6-8 hours. In addition the nm-applet embedded in the task bar becomes unresponsive after several hours. Clicking on the applet will still show the popup menu, but none of the menu entries respond to mouse clicks. When this happens, the VPN connections and Other networks menus also show up completely empty (only a small menu stub is displayed). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager-gnome 0.8.4~git.20110318t152954.9c4c9a0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4 Uname: Linux 2.6.38-9-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Tue May 10 11:53:09 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) IpRoute: 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.12 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.2.1 dev eth0 proto static Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/780602/+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 780602] Re: nm-applet leaks memory and stops functioning after a while
I've switched from natty (Ubuntu 11.04) to a fresh install of quantal (Xubuntu 12.10), so I'm now running network-manager 0.9.6.0-0ubuntu7 and network-manager-gnome 0.9.6.2-0ubuntu6 (not sure why they're different versions). It looks like the massive memory leaks in nm-applet are gone. nm-applet tends to hover around 6MB of memory usage. However, after running for a couple of days, the applet stops responding. I think, though I'm not sure, that network connectivity eventually breaks some time later. As before, when nm-applet becomes unresponsive, I can still click the nm-applet icon in the indicator plugin in the panel to bring up the menu, but the VPN submenu only shows a stub, clicking on Information or Edit does nothing, and I suspect clicking on any of the other available networks doesn't do anything either. Killing and then restarting nm-applet fixes it for another couple of days. As many others, I'm always on WiFi, I suspend and resume often, and there tend to be a lot of wireless networks within range. Which, if any, of these factors makes a difference in causing nm-applet to become unresponsive remains unknown. Has anyone tried the latest 0.9.6.4 release from http://projects.gnome.org/NetworkManager ? It has some hopeful points about stability in the release notes: http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.9/NetworkManager-0.9.6.4.news -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory and stops functioning after a while Status in OEM Priority Project: Fix Committed Status in OEM Priority Project precise series: Confirmed Status in OEM Priority Project quantal series: Fix Committed Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: nm-applet leaks memory in a fresh install of Natty, increasing to over 200 Mb in 6-8 hours. In addition the nm-applet embedded in the task bar becomes unresponsive after several hours. Clicking on the applet will still show the popup menu, but none of the menu entries respond to mouse clicks. When this happens, the VPN connections and Other networks menus also show up completely empty (only a small menu stub is displayed). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager-gnome 0.8.4~git.20110318t152954.9c4c9a0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4 Uname: Linux 2.6.38-9-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Tue May 10 11:53:09 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) IpRoute: 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.12 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.2.1 dev eth0 proto static Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/780602/+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 1069207] Re: Unable to edit or add items to main menu
@Marcel, I think I've noticed the same. I copied the system's xfce- applications.menu (either from /etc/xdg/menus/xfce-applications.menu or /etc/xdg/xdg-xubuntu/menus/xfce-applications.menu, I don't remember which) to my ~/.config/menus folder, and have been editing that file by hand. In the Applications Menu dialog that pops up when you right click the menu and choose properties, I have the custom menu file option selected, and I have it set to ~/.config/menus/xfce-applications.menu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1069207 Title: Unable to edit or add items to main menu Status in “alacarte” package in Ubuntu: Confirmed Bug description: On a fresh install of XUbuntu 64bit I am unable to add items to the main menu. All the buttons seem to work but when you hit New Item or New Menu, type in your settins and click create nothing happens. Also attempted to disable some menu items and while the menu editor shows the changes there are no changes to the actual menu, even after restarting X. Let me know if you need anything else, Westin Shafer ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xubuntu-default-settings 12.10.7 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Sat Oct 20 15:42:51 2012 InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) PackageArchitecture: all SourcePackage: xubuntu-default-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1069207/+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 562005] Re: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers
I just tried installing 304.60 from https://launchpad.net/~noobslab/+archive/nvidia-quantal on my fresh install of Xubuntu 12.10 amd64 with no xorg.conf. Brightness controls did *not* work, as usual, so I'd say it isn't fixed. Note that the packages at that PPA are labelled as 304.60-0ubuntu1~precise~xup2, so maybe they're not ideal for quantal, but they do seem to work. I couldn't find any other PPA with quantal packages for 304.60. At least not yet. -- 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/562005 Title: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers Status in Ubuntu Certification Programme: Invalid Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Bug description: The brightness controls of laptops with NVIDIA NVS 3100M or Quadro FX 880M GPUs work while running Nouveau or when using a text mode VT, but not while running X and using proprietary NVIDIA drivers. It is possible to force the NVIDIA driver to control the backlight by adding [Option RegistryDwords EnableBrightnessControl=1] to the Devices section of xorg.conf . While this allows the backlight to be controlled, the increments are inconsistent and often result in a buzzing noise from the LED backlight on Lenovo ThinkPad T510s and W510s. Since this did not occur while running nouveau or when switching in text VT, something is wrong. This bad backlight behaviour has been confirmed on ThinkPad models T510 and W510 with NVIDIA NVS 3100m and Quadro FX 880M chipsets, respectively, via http://www.thinkwiki.org/wiki/Category:T510 Because this issue is related to NVIDIA's proprietary video driver, this issue can only be solved by them. An NVIDIA developer has said he will investigate the issues, which are discussed on the nvnews.net forums at http://www.nvnews.net/vbulletin/showthread.php?t=145105 and http://www.nvnews.net/vbulletin/showthread.php?t=150069 . For future reference, the latest NVIDIA drivers can be found in the Ubuntu X-Swat X updates PPA: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.15-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Apr 12 23:48:02 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.32-19-generic, x86_64: installed EcryptfsInUse: Yes GdmLog1: MachineType: LENOVO 4313CTO ProcCmdLine: BOOT_IMAGE=/bhostnamet/vmlinuz-2.6.32-19-generic rhostnamet=UUID=0b95b314-337f-49aa-86f9-6423e76e9f20 ro ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers XorgLogOld: dmi.bios.date: 02/22/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET49WW (1 tp-smapi, 0.40, 2.6.32-19-generic, x86_64: installed vboxnetadp, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxnetflt, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxdrv, 3.1.6, 2.6.32-19-generic, x86_64: installed.12 ) dmi.board.name: 4313CTO 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:bvr6MET49WW(1.12):bd02/22/2010:svnLENOVO:pn4313CTO:pvrThinkPadT510:rvnLENOVO:rn4313CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4313CTO dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-19-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+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 268845] Re: Yelp 100% loads processor when reading gnumeric-help or About Ubuntu
I noticed this as well, after installing GNU PSPP, clicking HelpReference Manual, and then quitting. yelp info:pspp showed 100% in gnome-system-monitor. After killing yelp, then repeating what I did above in GNU PSPP, yelp showed up again, but wasn't using any CPU, and exited after I quite PSPP. This is on natty (Ubuntu 11.04) on a Core2 Quad core. 2.6.38-16-generic yelp 3.0.0-0ubuntu2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/268845 Title: Yelp 100% loads processor when reading gnumeric-help or About Ubuntu Status in The Yelp Help Browser for Gnome: New Status in “gnumeric” package in Ubuntu: Invalid Status in “yelp” package in Ubuntu: Invalid Bug description: When opening help in Gnumeric, it starts to 100% load the processor. When closing the help window, the load ends. To manage notifications about this bug go to: https://bugs.launchpad.net/yelp/+bug/268845/+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 1069207] Re: Unable to edit or add items to main menu
I've also noticed this (Xubuntu 12.10 amd64). Nothing in alacarte actually does anything. Deleting items doesn't do anything, except sometimes it does work for the top two entries (Web Browser and Mail Reader). Hiding items doesn't work. Showing hidden items doesn't work. After changing the show toggle, the settings mysteriously revert back after a couple of seconds. Adding new menus or menu items doesn't do anything either. It's obvious from within alacarte that's something's wrong. I've also tried running alacarte from the command line, to see if any error messages print out. Nothing. I tried running it using sudo and gksudo, but those both failed in different ways. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1069207 Title: Unable to edit or add items to main menu Status in “alacarte” package in Ubuntu: Confirmed Bug description: On a fresh install of XUbuntu 64bit I am unable to add items to the main menu. All the buttons seem to work but when you hit New Item or New Menu, type in your settins and click create nothing happens. Also attempted to disable some menu items and while the menu editor shows the changes there are no changes to the actual menu, even after restarting X. Let me know if you need anything else, Westin Shafer ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xubuntu-default-settings 12.10.7 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Sat Oct 20 15:42:51 2012 InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) PackageArchitecture: all SourcePackage: xubuntu-default-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1069207/+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 562005] Re: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers
The latest certified nvidia blob (304.60) mentions this: Added support for the Backlight RandR output property for configuring the brightness of some notebook internal panels. http://www.nvidia.com/object/linux-display-amd64-304.60-driver.html Could it be this is finally the fix we've been waiting for? Anyone tried this latest version yet? I just installed Xubuntu 12.10 and with nvidia 304.51 I still need to add EnableBrightnessControl=1 to xorg.conf, and the brightness increments on my Thinkpad W510 are large and uneven, as always. -- 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/562005 Title: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers Status in Ubuntu Certification Programme: New Status in “nvidia-graphics-drivers” package in Ubuntu: Confirmed Bug description: The brightness controls of laptops with NVIDIA NVS 3100M or Quadro FX 880M GPUs work while running Nouveau or when using a text mode VT, but not while running X and using proprietary NVIDIA drivers. It is possible to force the NVIDIA driver to control the backlight by adding [Option RegistryDwords EnableBrightnessControl=1] to the Devices section of xorg.conf . While this allows the backlight to be controlled, the increments are inconsistent and often result in a buzzing noise from the LED backlight on Lenovo ThinkPad T510s and W510s. Since this did not occur while running nouveau or when switching in text VT, something is wrong. This bad backlight behaviour has been confirmed on ThinkPad models T510 and W510 with NVIDIA NVS 3100m and Quadro FX 880M chipsets, respectively, via http://www.thinkwiki.org/wiki/Category:T510 Because this issue is related to NVIDIA's proprietary video driver, this issue can only be solved by them. An NVIDIA developer has said he will investigate the issues, which are discussed on the nvnews.net forums at http://www.nvnews.net/vbulletin/showthread.php?t=145105 and http://www.nvnews.net/vbulletin/showthread.php?t=150069 . For future reference, the latest NVIDIA drivers can be found in the Ubuntu X-Swat X updates PPA: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.15-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Apr 12 23:48:02 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.32-19-generic, x86_64: installed EcryptfsInUse: Yes GdmLog1: MachineType: LENOVO 4313CTO ProcCmdLine: BOOT_IMAGE=/bhostnamet/vmlinuz-2.6.32-19-generic rhostnamet=UUID=0b95b314-337f-49aa-86f9-6423e76e9f20 ro ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers XorgLogOld: dmi.bios.date: 02/22/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET49WW (1 tp-smapi, 0.40, 2.6.32-19-generic, x86_64: installed vboxnetadp, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxnetflt, 3.1.6, 2.6.32-19-generic, x86_64: installed vboxdrv, 3.1.6, 2.6.32-19-generic, x86_64: installed.12 ) dmi.board.name: 4313CTO 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:bvr6MET49WW(1.12):bd02/22/2010:svnLENOVO:pn4313CTO:pvrThinkPadT510:rvnLENOVO:rn4313CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4313CTO dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-19-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+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 1003128] Re: Brightness controls not working on Thinkpad W510
*** This bug is a duplicate of bug 562005 *** https://bugs.launchpad.net/bugs/562005 ** This bug has been marked a duplicate of bug 562005 Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers -- 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/1003128 Title: Brightness controls not working on Thinkpad W510 Status in “nvidia-graphics-drivers” package in Ubuntu: New Bug description: I have a Lenovo Thinkpad W510 and the hardware brightness keys activate the brightness slider but the screen does not respond. Neither does the brightness slider in the system settings. It does appear that if I set the slider and then restart the system then the display corresponds to the location of the slider just before restart. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 295.40 Thu Apr 5 21:37:00 PDT 2012 GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,vpswitch,snap,move,resize,gnomecompat,grid,place,dbus,imgpng,compiztoolbox,regex,unitymtgrabhandles,mousepoll,session,animation,wall,fade,scale,workarounds,expo,ezoom,unityshell] CompositorRunning: compiz Date: Tue May 22 17:02:42 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-current, 295.40, 3.2.0-23-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. nvidia-current, 295.40, 3.2.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: NVIDIA Corporation GT216 [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2145] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use) xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: LENOVO 43192RU ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=2fc7d468-f87f-49c5-95cd-2044ed5c49b2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6NET74WW (1.34 ) dmi.board.name: 43192RU 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:bvr6NET74WW(1.34):bd10/27/2010:svnLENOVO:pn43192RU:pvrThinkPadW510:rvnLENOVO:rn43192RU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 43192RU dmi.product.version: ThinkPad W510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.8-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1003128/+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 160311] Re: Resizing windows by grabbing window borders is difficult
Inexplicably, I think Canonical wants to clone MacOS as much as possible, without getting sued. Worstinterface..ever. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity 2D: Confirmed Status in “human-gtk-theme” package in Ubuntu: Invalid Status in “light-themes” package in Ubuntu: Fix Released Status in “metacity” package in Ubuntu: Fix Released Status in “human-gtk-theme” source package in Maverick: Invalid Status in “light-themes” source package in Maverick: Triaged Status in “metacity” source package in Maverick: Triaged Bug description: * No more comments needed This should mostly be fixed for Natty and might get backported to earlier releases as well. * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+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 780602] Re: nm-applet leaks memory and stops functioning after a while
I tried live usb booting into Precise amd64 a few days before final release, left it running overnight while bittorrenting. Didn't notice much of an increase in memory usage in nm-applet, maybe 10% at most, which is far far better than what I'm seeing in natty. Also, I never encountered the little menu stub that's common in Natty after a long enough time. So things have obviously improved. The version in Precise (0.9.4.1 ish) is a fair bit newer than the one in Natty (0.8.4 ish). Again, any chance some patch(es) might get backported? This really is a security issue, in a networking component no loess, and Natty is supposed to remain supported until October 2012. ** Changed in: network-manager-applet (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory and stops functioning after a while Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: nm-applet leaks memory in a fresh install of Natty, increasing to over 200 Mb in 6-8 hours. In addition the nm-applet embedded in the task bar becomes unresponsive after several hours. Clicking on the applet will still show the popup menu, but none of the menu entries respond to mouse clicks. When this happens, the VPN connections and Other networks menus also show up completely empty (only a small menu stub is displayed). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager-gnome 0.8.4~git.20110318t152954.9c4c9a0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4 Uname: Linux 2.6.38-9-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Tue May 10 11:53:09 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) IpRoute: 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.12 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.2.1 dev eth0 proto static Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/780602/+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 684599] Re: Memory leak in nm-applet
As commented in bug #780602, this is most definitely *not* fixed in Natty. Since this was originally reported against Natty, and since Natty remains supported, shouldn't the status be Confirmed, and not Fix Released. Or if the status only applies to the latest release, how do we mark that it's still broken for a previous release like Natty? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/684599 Title: Memory leak in nm-applet Status in elementary OS: Fix Released Status in Network Manager GNOME Applet: Invalid Status in “network-manager-applet” package in Ubuntu: Fix Released Bug description: Binary package hint: network-manager the nm-applet is eating my ram (149MB) not that much when freshly booted. im using wifi connection via b43 driver for broadcom 4311/12 hardware (on Lenovo N100 laptop) on Ubuntu 11.04 natty 32-bit with 2.6.37-7-generic kernel indicator applet version 0.4.6-0ubuntu1 rest of the packages are up to date with proposed and backports enabled - no PPAs To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/684599/+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 780602] Re: nm-applet leaks memory and stops functioning after a while
I've been living with this bug for nearly a year. Luckily, I have 16GB of RAM, but I still need to restart nm-applet every few days when the more networks and VPN submenus stop working (which correlates very well to extreme memory usage). Are there no patches that can be combined/backported to finally fix this in Natty? Are there any new insights from Precise in Bug #930491 that might apply to Natty? Does anyone have a PPA I can try? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory and stops functioning after a while Status in “network-manager-applet” package in Ubuntu: Triaged Bug description: nm-applet leaks memory in a fresh install of Natty, increasing to over 200 Mb in 6-8 hours. In addition the nm-applet embedded in the task bar becomes unresponsive after several hours. Clicking on the applet will still show the popup menu, but none of the menu entries respond to mouse clicks. When this happens, the VPN connections and Other networks menus also show up completely empty (only a small menu stub is displayed). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager-gnome 0.8.4~git.20110318t152954.9c4c9a0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4 Uname: Linux 2.6.38-9-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Tue May 10 11:53:09 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) IpRoute: 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.12 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.2.1 dev eth0 proto static Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/780602/+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 780602] Re: nm-applet leaks memory and stops functioning after a while
Also, maybe -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory and stops functioning after a while Status in “network-manager-applet” package in Ubuntu: Triaged Bug description: nm-applet leaks memory in a fresh install of Natty, increasing to over 200 Mb in 6-8 hours. In addition the nm-applet embedded in the task bar becomes unresponsive after several hours. Clicking on the applet will still show the popup menu, but none of the menu entries respond to mouse clicks. When this happens, the VPN connections and Other networks menus also show up completely empty (only a small menu stub is displayed). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager-gnome 0.8.4~git.20110318t152954.9c4c9a0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4 Uname: Linux 2.6.38-9-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Tue May 10 11:53:09 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) IpRoute: 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.12 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.2.1 dev eth0 proto static Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/780602/+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 780602] Re: nm-applet leaks memory and stops functioning after a while
Oops. Also, maybe this should be marked as a duplicate of Bug #684599 ? That one's a fair bit older, and has a lot more activity on it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory and stops functioning after a while Status in “network-manager-applet” package in Ubuntu: Triaged Bug description: nm-applet leaks memory in a fresh install of Natty, increasing to over 200 Mb in 6-8 hours. In addition the nm-applet embedded in the task bar becomes unresponsive after several hours. Clicking on the applet will still show the popup menu, but none of the menu entries respond to mouse clicks. When this happens, the VPN connections and Other networks menus also show up completely empty (only a small menu stub is displayed). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager-gnome 0.8.4~git.20110318t152954.9c4c9a0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic-pae 2.6.38.4 Uname: Linux 2.6.38-9-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Tue May 10 11:53:09 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110413) IpRoute: 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.12 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.2.1 dev eth0 proto static Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/780602/+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 684599] Re: Memory leak in nm-applet
Perhaps bug # 780602 be marked as a duplicate of this one? I'd love to see this finally fixed in natty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/684599 Title: Memory leak in nm-applet Status in elementary OS: Fix Released Status in Network Manager GNOME Applet: Invalid Status in “network-manager-applet” package in Ubuntu: Fix Released Bug description: Binary package hint: network-manager the nm-applet is eating my ram (149MB) not that much when freshly booted. im using wifi connection via b43 driver for broadcom 4311/12 hardware (on Lenovo N100 laptop) on Ubuntu 11.04 natty 32-bit with 2.6.37-7-generic kernel indicator applet version 0.4.6-0ubuntu1 rest of the packages are up to date with proposed and backports enabled - no PPAs To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/684599/+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
