[Bug 1575655] Re: the network indicator shows the wrong status
I have this problem in Xubuntu 16.04 with HWE kernel, on my Thinkpad X1 carbon 4th gen (2016). uname -a: Linux Godel 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux lspci | grep -i network: 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) I've been using: killall nm-applet; nm-applet & very regularly in the past couple of weeks when I've been using a different wifi router. I don't think this was happening to me in the past. Has anyone seen a change in behaviour, whether due to updates or change in usual physical location? Another Thinkpad on the same network with the same install and kernel, an old X120e running an AMD cpu and a Realtek RTL8188CE wireless card, does *not* seem to exhibit this problem. i.e., nm-applet shows the correct icon and shows all available wifi APs after multiple suspend resume cycles. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575655 Title: the network indicator shows the wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
Sorry, I forgot to mention above that I selected both "download updates while installing Ubuntu" and "download third party software for graphics and Wi-Fi hardware, Flash, Mp3 and other media." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418706 Title: UEFI: blank drive incorrectly detected as existing BIOS-mode install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1418706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418706] Re: UEFI: blank drive incorrectly detected as existing BIOS-mode install
This is an infuriating bug, but I've found a workaround, more or less described in a comment in a duplicate bug here: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1547286/comments/11 I'm installing Xubuntu 16.04 amd64 on a completely blank SSD on a brand new UEFI-enabled HP system. If I immediately create an EFI partition (say 200 MB) before the main partition, that doesn't fix the bug. I still get the broken "Force UEFI installation" dialog in the next step. This is because, for some strange reason, the installer decides to set the EFI partition to ext4 instead of FAT32. You can see this in the space allocation graphic at the top of the manual partitioning dialog. So, instead of directly creating an EFI partition (during which you can't specify the file system type), I created a 200 MB FAT32 partition, then changed it to EFI with the "change..." button, and voila, I now have a FAT32 EFI partition. After allocating my root partition and hitting next, I no longer get the broken "Force UEFI installation" dialog, and installation proceeds smoothly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418706 Title: UEFI: blank drive incorrectly detected as existing BIOS-mode install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1418706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1347272] Re: Several XFCE applications appear unresponsive after communicating with a daemon
Just thought I'd mention that this problem does seem to have gone away for me in trusty. Not sure when that happened, but I'm glad it's (apparently) fixed. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear unresponsive after communicating with a daemon To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1347272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365965] Re: [MRE] Please update xfdesktop4 to 4.11.8 in Trusty
I would say release the package as an update, close bug 1307251, and then see if anyone continues to complain about icon positions. My guess is there will be fewer reports, and they'll be trickier to diagnose. It probably deserves a new bug report. I haven't had any other problems with 4.11.8 on trusty - there don't seem to be any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365965 Title: [MRE] Please update xfdesktop4 to 4.11.8 in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1365965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1410548 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1410548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365965] Re: [MRE] Please update xfdesktop4 to 4.11.8 in Trusty
I just had icon positions reset on me on reboot, so it seems bug 1307251 is not fixed after all in xfdesktop 4.11.8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365965 Title: [MRE] Please update xfdesktop4 to 4.11.8 in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1365965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307251] Re: xfdesktop doesn't save the arrangement of desktop icons after a resolution change
I just had icon positions reset on me on reboot, so it seems this bug is not fixed after all in xfdesktop 4.11.8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307251 Title: xfdesktop doesn't save the arrangement of desktop icons after a resolution change To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/1307251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365965] Re: [MRE] Please update xfdesktop4 to 4.11.8 in Trusty
Also, note that I have Save session for future logins disabled in the log out dialog. Not sure if that should matter. I imagine it shouldn't. Icon positions should always be saved between reboots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365965 Title: [MRE] Please update xfdesktop4 to 4.11.8 in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1365965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307251] Re: xfdesktop doesn't save the arrangement of desktop icons after a resolution change
Also, note that I have Save session for future logins disabled in the log out dialog. Not sure if that should matter. I imagine it shouldn't. Icon positions should always be saved between reboots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307251 Title: xfdesktop doesn't save the arrangement of desktop icons after a resolution change To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/1307251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307251] Re: xfdesktop doesn't save the arrangement of desktop icons after a resolution change
I just tried installing the proposed xfdesktop 4.11.8 package from bug 1365965, and so far, it seems to work. I'm not exactly sure what triggered the icon rearrangement on reboot (it wasn't necessarily a screen resolution change), so I'll report back if I have any further problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307251 Title: xfdesktop doesn't save the arrangement of desktop icons after a resolution change To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/1307251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315716] Re: No confirmation prompt when force-deleting (SHIFT+DEL)
This seems to work for me after updating to xfdesktop 4.11.8 in the proposed update in bug 1365965 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315716 Title: No confirmation prompt when force-deleting (SHIFT+DEL) To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/1315716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365965] Re: [MRE] Please update xfdesktop4 to 4.11.8 in Trusty
I'm trying out this 4.11.8 proposed release because I was affected by bug 1307251 and bug 1315716. So far, both seem to have been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365965 Title: [MRE] Please update xfdesktop4 to 4.11.8 in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1365965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369651] Re: libmtp error: Could not send object info when copying content to root MTP folder
I get this Could not send object info error from libmtp on seemingly random files while copying a large number of files to a subfolder of Internal storage on my Moto X running CyanogenMod 11 2014-11-28 (ghost), using Thunar in Xubuntu 14.04. On second glance, I think this is due to the full pathnames of some of the files on the destination exceeding 255 characters in length. Could use a more informative message. Does MTP provide more descriptive error codes? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369651 Title: libmtp error: Could not send object info when copying content to root MTP folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1369651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244629] Re: SRU xfce4-weather-plugin, currently showing 'No Data'
@luca, not still, this is a new issue, started showing No data around last weekend, maybe October 11, 2014 . This is on Xubuntu 14.04 amd64. This bug report refers to an old old version of this issue. xfce4 -weather-plugin has been using met.no for its data for a while now. I suppose something's changed with the met.no API? I even tried compiling and installing the latest xfce4-weather-plugin from git: http://git.xfce.org/panel-plugins/xfce4-weather-plugin/ ...but that doesn't help. I have this problem on 3 different machines running Xubuntu 14.04. Not sure where to alert the devs, though if they use it on a regular basis, they've probably noticed the problem as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244629 Title: SRU xfce4-weather-plugin, currently showing 'No Data' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-weather-plugin/+bug/1244629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244629] Re: SRU xfce4-weather-plugin, currently showing 'No Data'
Actually, from the timestamps of the cache files in $HOME/.cache/xfce4/weather, it looks like the last successful data retrieval was Oct 12. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244629 Title: SRU xfce4-weather-plugin, currently showing 'No Data' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-weather-plugin/+bug/1244629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244629] Re: SRU xfce4-weather-plugin, currently showing 'No Data'
Never mind. The latest version in git does indeed work. met.no changed their API from 1.1 to 1.2: http://api.yr.no/weatherapi/locationforecastlts/1.2/documentation 1.2 was implemented in git in xfce4-weather-plugin this summer, and met.no deprecated 1.1 about a week ago. My problem was that I wasn't installing the git version properly. The panel in xubuntu uses /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/ as the plugin path, but autogen.sh only allows you to set the first part of the prefix: autogen.sh --prefix=/usr But that installs to /usr/lib/xfce4/panel/plugins/, which is missing the x86_64-linux-gnu part of the path. So, I manually copied the libweather.so and libweather.la files to /usr/lib/x86_64-linux- gnu/xfce4/panel/plugins, restarted the panel with xfce4-panel -r, and that did it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244629 Title: SRU xfce4-weather-plugin, currently showing 'No Data' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-weather-plugin/+bug/1244629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318218] Re: SATA problems on MacBook Pro 11,1?
Just to clarify, it seems the hard resetting link and SError: {
CommWake DevExch } errors I was seeing had to do with me
connecting/disconnecting an external bus-powered portable eSATA drive
(ata6) that sometimes isn't correctly detected for some reason. The
sudden, random remounting of my main drive (ata1) in read-only mode may
well be a different problem, and one that leaves no trace in the logs
because, of course, the drive is in read-only mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318218
Title:
SATA problems on MacBook Pro 11,1?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318218/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318218] Re: SATA problems on MacBook Pro 11,1?
I'm getting these errors in Xubuntu 14.04 amd64 with nvidia binaries on a Lenovo Thinkpad W510. I only noticed them because several times over the past couple of months since installing Xubuntu 14.04, the machine has suddenly, and quite randomly, remounted the filesystem to read only. When that happens, I can't even shut down normally. I can't even log in via a TTY to issue a shutdown command. When I installed Xubuntu 14.04, I also upgraded from a hard drive to a Crucial MX100 SSD, but it seems likelier the problem is software, not hardware. I don't have any buffer I/O errors or anything like that in kern.log or syslog. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318218 Title: SATA problems on MacBook Pro 11,1? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390959] Re: 045e:00b0 Microsoft keyboard and 045e:0745 nano transceiver recognised as joystick - interferes with some games
I seem to be having the same problem with a Microsoft Sculpt Mobile Mouse I just bought. http://www.microsoft.com/hardware/en-ca/p/sculpt-mobile-mouse This is in Xubuntu 14.04 amd64 on a Thinkpad W510. In the xfce Mouse and Touchpad settings I get two entries for Microsoft Microsoft (R) Nano Transceiver v1.0. Some more details: $ udevadm info /dev/input/js0 https://gist.github.com/mspacek/c805f36a7129a30a0bcf $ udevadm info --attribute-walk /dev/input/js0 https://gist.github.com/mspacek/96673b195fa0b16f9e20 $ uname -a Linux Escher 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/390959 Title: 045e:00b0 Microsoft keyboard and 045e:0745 nano transceiver recognised as joystick - interferes with some games To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/390959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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-qt:i386
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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sni-qt/+bug/1068940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303736] Re: [SRU] Black screen after wakeup from suspending by closing the laptop lid
** This bug is no longer a duplicate of bug 1357090 Black screen on resume Xubuntu 14.04.1 #1303736 NOT fixed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303736 Title: [SRU] Black screen after wakeup from suspending by closing the laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-power-manager/+bug/1303736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357090] Re: Black screen on resume Xubuntu 14.04.1 #1303736 NOT fixed
Damian, you probably shouldn't go marking the original bug #1303736 (marked resolved) as a duplicate of this one. The whole point of starting this bug was to differentiate it from the previous one, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357090 Title: Black screen on resume Xubuntu 14.04.1 #1303736 NOT fixed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1357090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303736] Re: [SRU] Black screen after wakeup from suspending by closing the laptop lid
As Elfy said, this may be becoming a catch-all bug for similar problems. But, since I don't know where else to report this, and since it seems similar enough: I was having the original black screen problem with the default light- locker installed. After the updates rolled out and after toggling the settings as instructed, the original problem as described went away. Still I was so disappointed with light-locker's TTY switching and all the problems that come with it... bug # 1336647 - light-locker switches virtual terminals on lock and unlock ...that I uninstalled it and installed gnome-screensaver instead. All is good, but once in a while, when I resume from suspend by opening the lid of my Thinkpad W510 (running Xubuntu 14.04 amd64), it turns on, but the screen does not. If I close the lid and let it suspend, and then open it again to resume, the screen has (so far) always turned on on the second try. Seems there's some low probability (maybe 10%) of the screen not turning on during resume. Again, smells like a race condition. Perhaps it has something to do with bug # 1347272. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303736 Title: [SRU] Black screen after wakeup from suspending by closing the laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-power-manager/+bug/1303736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear unresponsive after communicating with a daemon To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1347272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222356] Re: ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message
Is this perhaps a duplicate of bug #1347272 (Several XFCE applications appear unresponsive after communicating with a daemon)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222356 Title: ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1222356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965953 Title: Indicator menus are too short and scroll when opened from screen bottom To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/965953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear unresponsive after communicating with a daemon To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254881] Re: xfce session starts multiple instances of xfce4-power-manager and xfce4-volumed
*** This bug is a duplicate of bug 1347272 *** https://bugs.launchpad.net/bugs/1347272 ** This bug has been marked a duplicate of bug 1347272 Several XFCE applications appear irresponsible after communicating with a daemon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254881 Title: xfce session starts multiple instances of xfce4-power-manager and xfce4-volumed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1254881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: Several XFCE applications appear irresponsible after communicating with a daemon To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1347272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39
@Jeffrey, I don't know for sure, but I'd say it's likely that two drives from the same manufacturer using the same controller will at the very least be both derived from the same firmware code base, and their firmware will therefore likely have a lot of bugs (and features) in common. Since your drive is from another manufacturer (or is it just a relabelled Crucial drive?), it's maybe more likely to have significantly different firmware, and maybe less likely to have the corruption bug. My bet would be the corruption problem is a firmware problem, one that could be fixed. If it is indeed a silicon problem, it could be worked around in the firmware, or features could be disabled to ensure data integrity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39
@Jeffrey AFAIK, the Crucial M500 uses the Marvell 88SS9187 controller, while the M550 and MX100 both use the Marvell 88SS9189 controller, and therefore probably share the same firmware (or maybe the MX100 firmware was forked off of the M550 firmware): These new Crucial MX100 SSD series features the Marvell 88SS9189 controller, a minor upgrade from the 88SS9187 that was found in the M500 drive. http://www.legitreviews.com/crucial-mx100-256gb-512gb-ssd-review_143984 The short summary is that the MX100 builds on the same architecture as the M500 and M550. The only fundamental difference is the NAND inside as the controller is the same Marvell 88SS9189 silicon as found inside the M550. The 9189 is a minor upgrade over the 9187 and what it does is provide better support for DevSLP along with some bandwidth optimizations. http://www.anandtech.com/show/8066/crucial-mx100-256gb-512gb-review -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/976638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1347272] [NEW] DBus communication problems affecting multiple packages
Public bug reported: I seem to be hitting transient DBus communication problems after a fresh install of Xubuntu 14.04 amd64 on my Thinkpad W510 with the latest nvidia binaries from the Ubuntu repos. Here are the related bugs. Sometimes rebooting fixes things for a while. If I understand correctly, at least one of the bug reports (Bug #1314782) suggests a race condition is to blame: Bug #976638 (pkexec does not find any authentication agent) Bug #1193236 (Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*) Bug #1239014 (xfsettingsd unable to daemonize properly when overlay scrollbars are activated) Bug #1048805 (xfce4-appfinder launches very slowly) Bug #1314782 (multimedia keys don't work when xfce4-volumed is run in daemon mode) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: dbus 1.6.18-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jul 22 16:26:36 2014 InstallationDate: Installed on 2014-06-25 (27 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347272 Title: DBus communication problems affecting multiple packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1347272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/976638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314782] Re: multimedia keys don't work when xfce4-volumed is run in daemon mode
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314782 Title: multimedia keys don't work when xfce4-volumed is run in daemon mode To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-volumed/+bug/1314782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239014] Re: xfsettingsd unable to daemonize properly when overlay scrollbars are activated
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239014 Title: xfsettingsd unable to daemonize properly when overlay scrollbars are activated To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/1239014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048805] Re: xfce4-appfinder launches very slowly
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048805 Title: xfce4-appfinder launches very slowly To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-appfinder/+bug/1048805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1193236 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1193236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1068988] Re: Synaptic runs without administrative privileges when run from the launcher
In Xubuntu 14.04, I found I had to replace the exec line in my synaptic.desktop file from synaptic-pkexec to gksu synaptic. Not sure if it's related, but I seem to be having lots of DBus-related issues in Xubuntu 14.04. Argh. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068988 Title: Synaptic runs without administrative privileges when run from the launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1068988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254895] Re: synaptic won't start from unity dash
*** This bug is a duplicate of bug 1068988 *** https://bugs.launchpad.net/bugs/1068988 ** This bug has been marked a duplicate of bug 1068988 Synaptic runs without administrative privileges when run from the launcher -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254895 Title: synaptic won't start from unity dash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1254895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/976638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1068988] Re: Synaptic runs without administrative privileges when run from the launcher
*** This bug is a duplicate of bug 976638 *** https://bugs.launchpad.net/bugs/976638 ** This bug has been marked a duplicate of bug 976638 pkexec does not find any authentication agent -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068988 Title: Synaptic runs without administrative privileges when run from the launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1068988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254895] Re: synaptic won't start from unity dash
*** This bug is a duplicate of bug 976638 *** https://bugs.launchpad.net/bugs/976638 ** This bug is no longer a duplicate of bug 1068988 Synaptic runs without administrative privileges when run from the launcher ** This bug has been marked a duplicate of bug 976638 pkexec does not find any authentication agent -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254895 Title: synaptic won't start from unity dash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1254895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314782] Re: multimedia keys don't work when xfce4-volumed is run in daemon mode
The slowness in that bug may simply be some kind of timeout being hit due to a dbus connection problem. After the timeout, maybe it retries and succeeds, or tries some other method. I also have an unsubstantiated hunch that Bug #976638 (pkexec does not find any authentication agent) is also affected by this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314782 Title: multimedia keys don't work when xfce4-volumed is run in daemon mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1314782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/976638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1193236 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1193236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314782] Re: multimedia keys don't work when xfce4-volumed is run in daemon mode
The slowness in that bug may simply be some kind of timeout being hit due to a dbus connection problem. After the timeout, maybe it retries and succeeds, or tries some other method. I also have unsubstantiated hunches that: Bug #976638 (pkexec does not find any authentication agent) and Bug #1193236 (Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*) are also affected by this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314782 Title: multimedia keys don't work when xfce4-volumed is run in daemon mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1314782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314782] Re: multimedia keys don't work when xfce4-volumed is run in daemon mode
The slowness in that bug may simply be some kind of timeout being hit due to a dbus connection problem. After the timeout, maybe it retries and succeeds, or tries some other method. I also have unsubstantiated hunches that: Bug #976638 (pkexec does not find any authentication agent) and Bug #1193236 (Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*) are also affected by this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314782 Title: multimedia keys don't work when xfce4-volumed is run in daemon mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1314782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 912857] Re: Authenticate window doesn't appear anymore
*** This bug is a duplicate of bug 976638 *** https://bugs.launchpad.net/bugs/976638 ** This bug has been marked a duplicate of bug 976638 pkexec does not find any authentication agent -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/912857 Title: Authenticate window doesn't appear anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/912857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom default keyboard shortcuts don't work To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302244] Re: xfce4-power-manager-settings can not be launched after the session comes back from a suspension
I've seen the same thing regarding the power manager is not running, do you wish to run it now message in Xubuntu 14.04 on my Thinkpad W510. Clicking run does nothing. Trying to run xfce4-power-manager in terminal didn't help either. If I recally correctly, the process wouldn't show up in gnome-system-monitor. Not entirely sure how to reproduce the message. Rebooting probably fixed it. I've got other possibly more pressing issues with xfce4-power-manager and light-locker at the moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302244 Title: xfce4-power-manager-settings can not be launched after the session comes back from a suspension To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1302244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336647] [NEW] light-locker switches virtual terminals on lock and unlock
Public bug reported: I know this is, strangely, by design (http://xubuntu.org/news/screen- locking-in-xubuntu-14-04/), but compared to gnome-screensaver or xscreensaver, it's a regression as far as I'm concerned. I couldn't find any placeholder bug for this. If there is one already, then please mark this as duplicate, and sorry for the noise. A summary of what's wrong with switching VTs: 1. Locking takes ~4 seconds in Xubuntu 14.04 on my Thinkpad W510 with nvidia binaries installed. Unlocking takes another ~4 seconds. That's a total of 8 seconds for a lock/unlock cycle, not including password entry. That's simply terrible terrible usability. Locking and unlocking were basically instant in both gnome-screensaver and xscreensaver. 2. Locking and unlocking both result in some serious screen flashing, plus in my case, the brief display of the nvidia logo. This gives the very strong impression that X has just crashed and restarted. That was my conclusion the first few times it happened. All this VT switching can't be great for the hardware either, especially the backlight. 3. Audio playback stops on VT switch. A lot of us leave our laptops playing music on external speakers while we're in the next room doing something else for who knows how long. Having it stop just because the screensaver has been triggered is another usability fail. I suppose VT switching is being used for some kind of security guarantee (is there a reference for that somewhere?). However, IMO, using VT switching for locking and unlocking is a major fundamental design flaw, resulting in serious usability issues. As a result, light-locker is far from ready for prime time. Rolling it out for an LTS was a big mistake. ** Affects: light-locker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336647 Title: light-locker switches virtual terminals on lock and unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1336647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336065] Re: Does not fail gracefully when lightdm isn't running
** Summary changed: - Does not fail gracefully when lighdm isn't running + Does not fail gracefully when lightdm isn't running -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336065 Title: Does not fail gracefully when lightdm isn't running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1336065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325228] Re: light-locker mutes audio on lock, does not un-mute
@ochosi: it's actually not due to something that light-locker is doing. It's due to the VT switch that happens when locking. Um, isn't it light-locker that's executing the VT switch? Doesn't that make light-locker responsible for all the downsides that come with VT switching, including audio interruption? (see #1336647, ie https://bugs.launchpad.net/bugs/1336647). FWIW, audio does seem to resume playback after unlock for me in Xubuntu 14.04 on my Thinkpad W510 with light-locker installed. But the interruption on locking is completely unacceptable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325228 Title: light-locker mutes audio on lock, does not un-mute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1325228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314782] Re: multimedia keys don't work when xfce4-volumed is run in daemon mode
Hallelujah! Thanks for the workaround Alistair. I was going somewhat crazy, finding that rather randomly, volume keys and notifications and screen brightness notifications would work, sometimes only one would work, and sometimes neither would work. That smells like some kind of a race condition. This is in Xubuntu 14.04 amd64 on a Thinkpad W510 with nvidia binaries. At first I thought Bug #1254881 was the problem (xfce session starts multiple instances of xfce4-power-manager and xfce4-volumed), since I had multiple instances of both processes. After going through the procedure in that bug description, I got rid of my multiple instances (and my efforts seem to have stuck after logout and/or reboot), but I still had random functionality of volume keys and brightness notifications. Adding --no-daemon to the Exec line in both xfce4-volumed.desktop and xfce4-power-manager.desktop in /etc/xdg/autostart nailed it. Thanks for the tip! It seems xfsettingsd also suffers from some kind of DBus communication problem (Bug #1239014, xfsettingsd unable to daemonize properly when overlay scrollbars are activated). I notice that if I try logging out immediately after logging in, the system just sits there for about 10 seconds. I've also been noticing weird behaviour of my workspace applet (wrong workspace labels for the first 10 or 20 sec, which then magically correct themselves to the labels set in the settings), which I suspect might also be related to xfsettingsd. Unfortunately, adding --no-daemon to xfsettingsd.desktop in /etc/xdg/autostart doesn't seem to actually launch xfsettingsd with the --no-daemon flag in the session. Anyways, any news on merging the fix in the branch so these workarounds aren't required? Has it been tested? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314782 Title: multimedia keys don't work when xfce4-volumed is run in daemon mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1314782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254881] Re: xfce session starts multiple instances of xfce4-power-manager and xfce4-volumed
I was suffering from multiple processes of both xfce4-power-manager and xfce4-volumed as well. Thanks Darko for the workaround in the bug description. However, that wasn't enough to make my volume controls work reliably. Note that Bug #1314782 is very related. The workaround posted there (add --no-daemon to the xfce4-volumed processe as well) worked for me. See https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1314782/comments/7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254881 Title: xfce session starts multiple instances of xfce4-power-manager and xfce4-volumed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1254881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239014] Re: xfsettingsd unable to daemonize properly when overlay scrollbars are activated
I think I've noticed the same in Xubuntu 14.04 amd64. Immediately after login, hitting Ctrl+Alt+Del to lock the screen, and attempting to log back out again, doesn't do anything until after about a 10 sec delay. I think killing xfsettingsd and running xfsettingsd --no-daemon instead might fix it on the next login, but I might be wrong. I also notice weird behaviour of my workspace applet. It shows wrong workspace labels for the first 10 or 20 sec, which then magically correct themselves to the correct labels set in the settings. I suspect that's related. Bug #1314782 ( multimedia keys don't work when xfce4-volumed is run in daemon mode) has a promising explanation and a patch for xfce4-volumed that might work, but it apparently hasn't been merged. Not sure if a similar patch could be put together for xfsettingsd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239014 Title: xfsettingsd unable to daemonize properly when overlay scrollbars are activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1239014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239014] Re: xfsettingsd unable to daemonize properly when overlay scrollbars are activated
Oops. That should've been hitting Ctrl+Alt+Del to lock the screen, *OR* attempting to log back out again. By the way, the workspace applet labels are incorrectly displayed only once in a while on login, maybe a 50% probability. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239014 Title: xfsettingsd unable to daemonize properly when overlay scrollbars are activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1239014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973778] Re: Unable to connect to Xfce Power Manager
Note that Darko's Bug #1254881 (xfce session starts multiple instances of xfce4-power-manager and xfce4-volumed) is useful, while Bug #1314782 (multimedia keys don't work when xfce4-volumed is run in daemon mode) might be the ultimate fix for all of this, assuming that patch can be applied to more than just xfce4-volumed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973778 Title: Unable to connect to Xfce Power Manager To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/973778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39
@Allard, OK, that's good to know that a message shows up in dmseg saying the queued trim is disabled. I don't have that message for my MX100, so it seems trim isn't disabled in the kernel for the MX100: $ dmesg | grep ata1 [1.995490] ata1: SATA max UDMA/133 abar m2048@0xf2627000 port 0xf2627100 irq 54 [2.313452] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.314803] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [2.314811] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [2.314976] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04) [2.314978] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [2.315360] ata1.00: supports DRM functions and may not be fully accessible [2.319343] ata1.00: ATA-9: Crucial_CT512MX100SSD1, MU01, max UDMA/133 [2.319349] ata1.00: 1000215216 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [2.325081] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [2.325089] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [2.325152] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04) [2.325157] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [2.325524] ata1.00: supports DRM functions and may not be fully accessible [2.333873] ata1.00: configured for UDMA/133 [ 35.495513] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 35.496830] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 35.496832] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 35.496875] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04) [ 35.496876] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 35.497154] ata1.00: supports DRM functions and may not be fully accessible [ 35.506398] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 35.506399] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 35.506439] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04) [ 35.506441] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 35.506712] ata1.00: supports DRM functions and may not be fully accessible [ 35.514807] ata1.00: configured for UDMA/133 [ 72.563250] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 72.564536] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 72.564538] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 72.564596] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04) [ 72.564597] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 72.564868] ata1.00: supports DRM functions and may not be fully accessible [ 72.574059] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 72.574061] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 72.574108] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04) [ 72.574110] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 72.574367] ata1.00: supports DRM functions and may not be fully accessible [ 72.582480] ata1.00: configured for UDMA/133 [ 88.186608] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 88.187916] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 88.187918] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 88.187977] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04) [ 88.187978] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 88.188274] ata1.00: supports DRM functions and may not be fully accessible [ 88.197508] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 88.197509] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 88.197570] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04) [ 88.197572] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 88.197847] ata1.00: supports DRM functions and may not be fully accessible [ 88.205956] ata1.00: configured for UDMA/133 [ 873.063550] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 873.064874] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [ 873.064876] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [ 873.064924] ata1.00: ACPI cmd ef/5f:00:00:00:00:a0 (SET FEATURES) rejected by device (Stat=0x51 Err=0x04) [ 873.064925] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [ 873.065288] ata1.00: supports DRM functions and may not be fully accessible [
[Bug 1314782] Re: multimedia keys don't work when xfce4-volumed is run in daemon mode
Bug #1048805 is also related (xfce4-appfinder launches very slowly). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314782 Title: multimedia keys don't work when xfce4-volumed is run in daemon mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-volumed/+bug/1314782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048805] Re: xfce4-appfinder launches very slowly
I have this issue for both xfce4-appfinder and xfrun4 on a fresh install of Xubuntu 14.04 amd64 on a Thinkpad W510 with nvidia binaries. Running them with --disable-server makes start times instantaneous. Otherwise, there's an unbearable 10-20 sec delay, and sometimes multiple zombie instances running simultaneously. Bug #1314782 (multimedia keys don't work when xfce4-volumed is run in daemon mode) might be the ultimate fix for all of this, assuming that patch can be applied to more than just xfce4-volumed. Seems like it's some kind of race condition, or forking of processes in the wrong order. Something like that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048805 Title: xfce4-appfinder launches very slowly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-appfinder/+bug/1048805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39
Note that there are reports on the Crucial forum that the Crucial M550 has the same problem, and therefore because it uses the same controller (and firmware?), the MX100 does too: http://forum.crucial.com/t5/Solid-State-Drives-SSD/M500-M5x0-QUEUED- TRIM-data-corruption-alert-mostly-for-Linux/m-p/154146#M43579 I'm not so brave any more, so I've removed the --no-model-check to the exec fstrim-all line in the cron fstrim file for my MX100. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39
@njj: I'm not so sure. According to a post from hmh just a few minutes ago on the above posted Crucial forum thread, the MX100 is not blacklisted in the kernel. Also, when I run fstrim -v /, I get a response that bytes were trimmed. When I run it again, I get 0 bytes trimmed (see #53). Is this expected behaviour for a trim-disabled SSD? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259829] Re: fstrim corrpution on some SSDs
** Summary changed: - htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 + fstrim corrpution on some SSDs ** Summary changed: - fstrim corrpution on some SSDs + fstrim corrupution on some SSDs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: fstrim corrupution on some SSDs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259829] Re: fstrim corrupution on some SSDs
I've installed Xubuntu 14.04 on a brand new Crucial MX100 SSD
(CT512MX100SSD1, original MU01 firmware, no newer firmware available) on
a Thinkpad W510, and saw the note in the cron.weekly/fstrim file. After
running fstrim manually the first two times, I got this:
$ sudo fstrim -v /
/: 498557419520 bytes were trimmed
$ sudo fstrim -v /
/: 0 bytes were trimmed
I also ran some of Martin Pitt's load tests for a few minutes while
calling fstrim -v repeatedly. No problems.
Since Crucial updated the firmware to MU05 on 2014-03-25 for the
affected M500, and since the MX100 drive apparently has a slightly newer
controller...
These new Crucial MX100 SSD series features the Marvell 88SS9189 controller, a
minor upgrade from the 88SS9187 that was found in the M500 drive.
http://www.legitreviews.com/crucial-mx100-256gb-512gb-ssd-review_143984
...I'll be brave and add --no-model-check to the exec fstrim-all line
in the cron fstrim file. If I have any problems, I'll report back.
from hdparm -I:
ATA device, with non-removable media
Model Number: Crucial_CT512MX100SSD1
Serial Number: xxx
Firmware Revision: MU01
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions,
SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x0028)
Supported: 9 8 7 6 5
Likely used: 9
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBAuser addressable sectors: 268435455
LBA48 user addressable sectors: 1000215216
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 488386 MBytes
device size with M = 1000*1000: 512110 MBytes (512 GB)
cache/buffer size = unknown
Form Factor: 2.5 inch
Nominal Media Rotation Rate: Solid State Device
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
*SMART feature set
Security Mode feature set
*Write cache
*Look-ahead
*Host Protected Area feature set
*WRITE_BUFFER command
*READ_BUFFER command
*NOP cmd
*DOWNLOAD_MICROCODE
*Advanced Power Management feature set
SET_MAX security extension
*48-bit Address feature set
*Device Configuration Overlay feature set
*Mandatory FLUSH_CACHE
*FLUSH_CACHE_EXT
*SMART error logging
*SMART self-test
*General Purpose Logging feature set
*WRITE_{DMA|MULTIPLE}_FUA_EXT
*64-bit World wide name
*IDLE_IMMEDIATE with UNLOAD
Write-Read-Verify feature set
*WRITE_UNCORRECTABLE_EXT command
*{READ,WRITE}_DMA_EXT_GPL commands
*Segmented DOWNLOAD_MICROCODE
*Gen1 signaling speed (1.5Gb/s)
*Gen2 signaling speed (3.0Gb/s)
*Gen3 signaling speed (6.0Gb/s)
*READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
DMA Setup Auto-Activate optimization
Asynchronous notification (eg. media change)
Software settings preservation
Device Sleep (DEVSLP)
*SMART Command Transport (SCT) feature set
*SCT Write Same (AC2)
*SCT Features Control (AC4)
*SCT Data Tables (AC5)
*reserved 69[4]
*reserved 69[7]
*Data Set Management TRIM supported (limit 8 blocks)
*Deterministic read ZEROs after TRIM
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
supported: enhanced erase
2min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 500a07510c251af4
NAA : 5
IEEE OUI: 00a075
Unique ID : 10c251af4
Integrity word not set (found 0x, expected 0x1ba5)
Device Sleep:
[Bug 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39
@penalvch, Huh? I'm not currently having this problem. Just reporting that my Crucial CT512MX100SSD1 currently doesn't seem to exhibit the problem, and therefore should maybe be added to the whitelist. If you still want me to file a separate bug report (to get more hardware details?), please let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1281019 Title: 10de:0dda [HP EliteBook 8560w] Brightness controls are not working nvidia-319 and nvidia-331 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1281019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211035] Re: nvidia-settings crashes on exit
*** This bug is a duplicate of bug 1214508 *** https://bugs.launchpad.net/bugs/1214508 Still seeing this in nvidia-settings version 331.20 from the xorg-edgers PPA on Xubuntu 12.10. I updated the title to make it less version specific. ** Summary changed: - nvidia-settings-325 crashes on exit + nvidia-settings crashes on exit ** This bug has been marked a duplicate of bug 1214508 nvidia-settings segfaults on close after official update of drivers from 310 to 319 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211035 Title: nvidia-settings crashes on exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1211035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214508 Title: nvidia-settings =319 segfaults on close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings-319-updates/+bug/1214508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211034] Re: nvidia-settings-325 crash with pressing exit button
*** This bug is a duplicate of bug 1214508 *** https://bugs.launchpad.net/bugs/1214508 ** This bug is no longer a duplicate of bug 1211035 nvidia-settings crashes on exit ** This bug has been marked a duplicate of bug 1214508 nvidia-settings segfaults on close after official update of drivers from 310 to 319 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211034 Title: nvidia-settings-325 crash with pressing exit button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1211034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268027] Re: nvidia-settings crashes on exit
*** This bug is a duplicate of bug 1214508 *** https://bugs.launchpad.net/bugs/1214508 I just marked this as a duplicate of Bug #1214508. Alberto Milone, could you assign yourself to that bug? ** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268027 Title: nvidia-settings crashes on exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1268027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214508 Title: nvidia-settings =319 segfaults on close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings-319-updates/+bug/1214508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1218408 Title: nvidia-settings 319.32 Crash on exit (segmentation fault) (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings-319/+bug/1218408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214508 Title: nvidia-settings =319 segfaults on close To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1214508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1281019 Title: 10de:0dda [HP EliteBook 8560w] Brightness controls are not working nvidia-319 and nvidia-331 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1281019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930563 Title: NM Applet menu entries not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/930563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211035] Re: nvidia-settings-325 crash with pressing exit button
I have the same 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 installed nvidia-325 via synaptic. I get this in /var/log/syslog after two crashes: Sep 3 18:30:57 Escher kernel: [ 990.669702] traps: nvidia-settings[3826] trap invalid opcode ip:7f7cc8123909 sp:7fff8db23558 error:0 in libpixbufloader-xpm.so[7f7cc811f000+6000] Sep 3 18:36:18 Escher kernel: [ 1312.143971] traps: nvidia-settings[4682] trap invalid opcode ip:7ffdaae74909 sp:7fff775145b8 error:0 in libpixbufloader-xpm.so[7ffdaae7+6000] Does xpm suggest it's some sort of image or icon loading problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211035 Title: nvidia-settings-325 crashes on Quit button press To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1211035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211035] Re: nvidia-settings-325 crash with pressing exit button
Note that hitting the close button doesn't cause a crash, just hitting the Quit button. Other than the crash, both do the same thing. ** Summary changed: - nvidia-settings-325 crash with pressing exit button + nvidia-settings-325 crashes on Quit button press -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211035 Title: nvidia-settings-325 crashes on Quit button press To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1211035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211035] Re: nvidia-settings-325 crashes on Quit button press
Oops, never mind. I get the same crash whether I hit Quit or simply close the window. Seems apport stopped bothering to report the crashes after the first few times. Running nvidia-setttings from the command line gives this on exit: Illegal instruction (core dumped)Illegal instruction (core dumped) ** Summary changed: - nvidia-settings-325 crashes on Quit button press + nvidia-settings-325 crashes on exit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211035 Title: nvidia-settings-325 crashes on exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1211035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011073] Re: NetworkManager submenus sometimes unpopulated
@mdeslaur, will Quantal get fixed too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011073 Title: NetworkManager submenus sometimes unpopulated To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/1011073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933300 Title: nm-applet needs restart after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/933300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1117730 Title: nm-applet becomes unresponsive to interactions and submenus such as 'VPN Connections' show completely empty To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1117730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930563 Title: NM Applet menu entries not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/930563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780602 Title: nm-applet leaks memory and stops functioning after a while To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/780602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
