[Desktop-packages] [Bug 1388922] Re: xdg-open doesn't properly detect Xfce/Xubuntu
The patch referenced in post #17 won't correct this issue. It's adding the following condition: x"$DESKTOP_SESSION" = x"xfce" However, that's not the value of DESKTOP_SESSION: $ env | grep DESKTOP DESKTOP_SESSION=xubuntu XDG_SESSION_DESKTOP=xubuntu XDG_CURRENT_DESKTOP=XFCE A more correct check would be against XDG_CURRENT_DESKTOP -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1388922 Title: xdg-open doesn't properly detect Xfce/Xubuntu Status in Xdg-utils: Fix Released Status in xdg-utils package in Ubuntu: Confirmed Bug description: xdg-open doesn't detect the XFCE desktop environment on its fresh install on Ubuntu (not Xubuntu). I was able to fix that by adding 'elif [ x"$DESKTOP_SESSION" = x"xubuntu" ]; then DE=xfce;' line in 'detectDE()' function. To manage notifications about this bug go to: https://bugs.launchpad.net/xdg-utils/+bug/1388922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1406825] Re: xscreensaver complains "This version of xscreensaver is VERY OLD!"
Downloading the latest Debian build will only push this issue out. The problem is that upstream (Jamie Zawinski) has added code that checks to see if the current time is more than 12 months from when xscreensaver was compiled. I can't seem to find the current revision control repository for the Ubuntu package of xscreensaver or I'd provide links to the code in question within the repository, but here are links to the code on a github repository: https://github.com/danfuzz/xscreensaver/blob/f9983b7c0795eacde86415ca6362af0873b1cf07/driver/prefs.c#L1654 https://github.com/danfuzz/xscreensaver/blob/f9983b7c0795eacde86415ca6362af0873b1cf07/driver/splash.c#L170 https://github.com/danfuzz/xscreensaver/blob/f9983b7c0795eacde86415ca6362af0873b1cf07/driver/splash.c#L223 Seems the current 14.10 package was compiled back on December 9th, 2013. That's what's showing up in the about dialog anyway. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1406825 Title: xscreensaver complains "This version of xscreensaver is VERY OLD!" Status in One Hundred Papercuts: Confirmed Status in xscreensaver package in Ubuntu: Confirmed Bug description: Early minutes of year 2015 and the xscreensaver complains that "This version of xscreensaver is VERY OLD!" in this dialog: http://i.imgur.com/VUCQfun.png?1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xscreensaver 5.26-1ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-28.38-lowlatency 3.16.7-ckt1 Uname: Linux 3.16.0-28-lowlatency x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jan 1 00:44:38 2015 InstallationDate: Installed on 2011-11-13 (1144 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: xscreensaver UpgradeStatus: Upgraded to utopic on 2014-10-25 (67 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1406825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1374222] Re: path for policy files changed
Are the debian/rules changes from upstream? Near as I can tell, upstream does not have a debian directory in its source tree: https://chromium.googlesource.com/chromium/src.git/+/37.0.2062.120 Or are you referring to a different upstream? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1374222 Title: path for policy files changed Status in “apparmor” package in Ubuntu: New Status in “chromium-browser” package in Ubuntu: New Bug description: Between package version: 37.0.2062.94-0ubuntu0.12.04.1~pkg909 and package version: 37.0.2062.120-0ubuntu0.12.04.1~pkg917 The path checked by Ubuntu's chromium-browser package for policy files has changed. This results in administrator mandated settings not being applied, which should be considered a security vulnerability. In previous versions of the package, policy files were read from: /etc/chromium-browser/policies In the new version of the package, it is reading policy files from: /etc/chromium/policies The new package version has dropped the following line from its debian/rules file: sed -i 's,/etc/chromium/policies,/etc/chromium-browser/policies,' \ $(DEB_TAR_SRCDIR)/chrome/common/chrome_paths.cc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1374222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1374222] Re: path for policy files changed
It's not called out specifically in the change log. The existing entries in the change log are very concerning for the 12.04 LTS update: chromium-browser (37.0.2062.120-0ubuntu0.12.04.1~pkg917) precise- security; urgency=medium * Release to stage chromium-browser (37.0.2062.120-0ubuntu1) UNRELEASED; urgency=low * Upstream release 37.0.2062.120: - CVE-2014-3178: Use-after-free in rendering. Credit to miaubiz. - CVE-2014-3179: Various fixes from internal audits, fuzzing and other initiatives. * debian/rules: Simplify and rearrange. * debian/rules, debian/known_gyp_flags: Keep better track of known GYP flags, so we can fail when something changes unexpectedly. * debian/rules: Fix up patch-translations rule. Why are changes being made to debian/rules to "Simplify and rearrange" in an LTS update? That's just inviting problems like this. In looking at a side-by-side diff (via meld), it appears that the removal of this line may have been of victim of the referenced rearranging. I attempted to find the packaging source repository, but the one referenced in LP appears to be out dated and did not see a reference to the current one (if there is a public one). ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3178 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3179 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1374222 Title: path for policy files changed Status in “apparmor” package in Ubuntu: New Status in “chromium-browser” package in Ubuntu: New Bug description: Between package version: 37.0.2062.94-0ubuntu0.12.04.1~pkg909 and package version: 37.0.2062.120-0ubuntu0.12.04.1~pkg917 The path checked by Ubuntu's chromium-browser package for policy files has changed. This results in administrator mandated settings not being applied, which should be considered a security vulnerability. In previous versions of the package, policy files were read from: /etc/chromium-browser/policies In the new version of the package, it is reading policy files from: /etc/chromium/policies The new package version has dropped the following line from its debian/rules file: sed -i 's,/etc/chromium/policies,/etc/chromium-browser/policies,' \ $(DEB_TAR_SRCDIR)/chrome/common/chrome_paths.cc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1374222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1248763] Re: incorporate patches for sliding window support
Yes, that is the same issue, this report would be the solution to that issue. The updated patches appear to correct the hanging issue. I've updated my PPA builds with the latest patches. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1248763 Title: incorporate patches for sliding window support Status in “gvfs” package in Ubuntu: Incomplete Bug description: Please pull the upstream patches for sliding window support from these bug reports: https://bugzilla.gnome.org/show_bug.cgi?id=523015 https://bugzilla.gnome.org/show_bug.cgi?id=532951 https://bugzilla.gnome.org/show_bug.cgi?id=711247 I've built packages with them already. They are available in my PPA: https://launchpad.net/~jcollins/+archive/gvfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1248763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 250517] Re: gvfs performs slowly on bulk sftp transfers
PPA builds with Ross Lagerwall's patches can be found here: https://launchpad.net/~jcollins/+archive/gvfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/250517 Title: gvfs performs slowly on bulk sftp transfers Status in The "G" Library - GLib: Confirmed Status in GVFS: In Progress Status in “gvfs” package in Ubuntu: Triaged Bug description: Tested on a low-latency 100Mb fibre link. scp/sftp console clients are able to hit the line speed of around 10MB/s. Copying via Nautilus is almost 10 times slower, at about 1.6MB/s. This seems to be because it does not batch up writes, but waits for a reply for each. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/250517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1248763] Re: incorporate patches for sliding window support
The addition of sliding window support makes gvfs sftp transfers behave more like openssh sftp file transfers, resulting a significant throughput increase for connections with moderate to high latency (see below). The hang is being handled within one of the original bug reports, specifically: https://bugzilla.gnome.org/show_bug.cgi?id=532951. I'm testing updated patches to see if they resolve the hang. >From the referenced bug reports: == PULL == Some benchmark figures: Old behavior: Copying from local server = 6.1MB/s Copying from local server with 250ms of RTT latency = 0.251MB/s Copying many small files with 250ms of RTT latency = 0.64 files per second New behavior: Copying from local server = 13MB/s Copying from local server with 250ms of RTT latency = 6.6MB/s Copying many small files with 250ms of RTT latency = 1.24 files per second OpenSSH sftp client: Copying from local server = 14.2MB/s Copying from local server with 250ms of RTT latency = 6.4MB/s Copying many small files with 250ms of RTT latency = 1.34 files per second == PUSH == Some benchmark figures: Old behavior: Copying from local server = 6.1MB/s Copying from local server with 250ms of RTT latency = 0.249MB/s Copying many small files with 250ms of RTT latency = 0.93 files per second New behavior: Copying from local server = 12.2MB/s Copying from local server with 250ms of RTT latency = 6.2MB/s Copying many small files with 250ms of RTT latency = 1.24 files per second OpenSSH sftp client: Copying from local server = 12.8MB/s Copying from local server with 250ms of RTT latency = 6.7MB/s Copying many small files with 250ms of RTT latency = 1.33 files per second ** Bug watch added: GNOME Bug Tracker #532951 https://bugzilla.gnome.org/show_bug.cgi?id=532951 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1248763 Title: incorporate patches for sliding window support Status in “gvfs” package in Ubuntu: Incomplete Bug description: Please pull the upstream patches for sliding window support from these bug reports: https://bugzilla.gnome.org/show_bug.cgi?id=523015 https://bugzilla.gnome.org/show_bug.cgi?id=532951 https://bugzilla.gnome.org/show_bug.cgi?id=711247 I've built packages with them already. They are available in my PPA: https://launchpad.net/~jcollins/+archive/gvfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1248763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1248763] Re: incorporate patches for sliding window support
Looks like there may be some issue with the patches as I have been able to create reproducible hangs copying large (750M) files with the patched GVFS packages. This has been reported upstream. Will update this report when it's been resolved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1248763 Title: incorporate patches for sliding window support Status in “gvfs” package in Ubuntu: New Bug description: Please pull the upstream patches for sliding window support from these bug reports: https://bugzilla.gnome.org/show_bug.cgi?id=523015 https://bugzilla.gnome.org/show_bug.cgi?id=532951 https://bugzilla.gnome.org/show_bug.cgi?id=711247 I've built packages with them already. They are available in my PPA: https://launchpad.net/~jcollins/+archive/gvfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1248763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1248763] [NEW] incorporate patches for sliding window support
Public bug reported: Please pull the upstream patches for sliding window support from these bug reports: https://bugzilla.gnome.org/show_bug.cgi?id=523015 https://bugzilla.gnome.org/show_bug.cgi?id=532951 https://bugzilla.gnome.org/show_bug.cgi?id=711247 I've built packages with them already. They are available in my PPA: https://launchpad.net/~jcollins/+archive/gvfs ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1248763 Title: incorporate patches for sliding window support Status in “gvfs” package in Ubuntu: New Bug description: Please pull the upstream patches for sliding window support from these bug reports: https://bugzilla.gnome.org/show_bug.cgi?id=523015 https://bugzilla.gnome.org/show_bug.cgi?id=532951 https://bugzilla.gnome.org/show_bug.cgi?id=711247 I've built packages with them already. They are available in my PPA: https://launchpad.net/~jcollins/+archive/gvfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1248763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1248249] Re: regression: local admin not authorized for many tasks
For some reason this is working now, after a reboot. Not entirely sure what's changed, or why it wasn't working before. Resolving. ** Changed in: policykit-desktop-privileges (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/1248249 Title: regression: local admin not authorized for many tasks Status in “policykit-desktop-privileges” package in Ubuntu: Invalid Bug description: Similar reports to this were filed previously: #1005643 & #1069234 While 1069234 was marked as a duplicate of 1005643, and 1005643 was marked as resolved, this problem still exists with 13.10. When attempting to mount any of my local volumes through a graphical file manager (such as Thunar or Nautilus), I'm greeted with a dialog like the following: Failed to mount "keys". Not authorized to perform operation. When attempting to mount them from a command line I get the following: $ udisksctl mount -b /dev/mmcblk0p1 AUTHENTICATING FOR org.freedesktop.udisks2.filesystem-mount === Authentication is required to mount MS (/dev/mmcblk0p1) Multiple identities can be used for authentication: 1. Jamin Collins,,, (jcollins) 2. Jamin Collins,,, (jcollins) Choose identity to authenticate as (1-2): This is presumably because my user is in both the admin and sudo groups. If I remove the user from the sudo group the prompt changes: $ sudo deluser jcollins sudo [sudo] password for jcollins: Removing user `jcollins' from group `sudo' ... Done. $ udisksctl mount -b /dev/mmcblk0p1 AUTHENTICATING FOR org.freedesktop.udisks2.filesystem-mount === Authentication is required to mount MS (/dev/mmcblk0p1) Authenticating as: Jamin Collins,,, (jcollins) Password: So, there are a couple of problems here. First is the fact that a local admin is being prompted for authentication to mount local or removable file systems. Second, that the authentication system can't determine that accounts are, in fact, identical. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 07:35:31 2013 InstallationDate: Installed on 2009-12-21 (1414 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True PackageArchitecture: all SourcePackage: policykit-desktop-privileges UpgradeStatus: Upgraded to saucy on 2013-11-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1248249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1248249] Re: regression: local admin not authorized for many tasks
When prompted, the following appears in /var/log/auth.log: Nov 5 08:43:23 odin polkitd(authority=local): Registered Authentication Agent for unix-process:9487:464692 (system bus name :1.100 [udisksctl mount -b /dev/mmcblk0p1], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) When attempting to mount the volume through a graphical file manager (such as Thunar or Nautilus) there are no entries in /var/log/auth.log. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/1248249 Title: regression: local admin not authorized for many tasks Status in “policykit-desktop-privileges” package in Ubuntu: New Bug description: Similar reports to this were filed previously: #1005643 & #1069234 While 1069234 was marked as a duplicate of 1005643, and 1005643 was marked as resolved, this problem still exists with 13.10. When attempting to mount any of my local volumes through a graphical file manager (such as Thunar or Nautilus), I'm greeted with a dialog like the following: Failed to mount "keys". Not authorized to perform operation. When attempting to mount them from a command line I get the following: $ udisksctl mount -b /dev/mmcblk0p1 AUTHENTICATING FOR org.freedesktop.udisks2.filesystem-mount === Authentication is required to mount MS (/dev/mmcblk0p1) Multiple identities can be used for authentication: 1. Jamin Collins,,, (jcollins) 2. Jamin Collins,,, (jcollins) Choose identity to authenticate as (1-2): This is presumably because my user is in both the admin and sudo groups. If I remove the user from the sudo group the prompt changes: $ sudo deluser jcollins sudo [sudo] password for jcollins: Removing user `jcollins' from group `sudo' ... Done. $ udisksctl mount -b /dev/mmcblk0p1 AUTHENTICATING FOR org.freedesktop.udisks2.filesystem-mount === Authentication is required to mount MS (/dev/mmcblk0p1) Authenticating as: Jamin Collins,,, (jcollins) Password: So, there are a couple of problems here. First is the fact that a local admin is being prompted for authentication to mount local or removable file systems. Second, that the authentication system can't determine that accounts are, in fact, identical. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 07:35:31 2013 InstallationDate: Installed on 2009-12-21 (1414 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True PackageArchitecture: all SourcePackage: policykit-desktop-privileges UpgradeStatus: Upgraded to saucy on 2013-11-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1248249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1248249] [NEW] regression: local admin not authorized for many tasks
Public bug reported: Similar reports to this were filed previously: #1005643 & #1069234 While 1069234 was marked as a duplicate of 1005643, and 1005643 was marked as resolved, this problem still exists with 13.10. When attempting to mount any of my local volumes through a graphical file manager (such as Thunar or Nautilus), I'm greeted with a dialog like the following: Failed to mount "keys". Not authorized to perform operation. When attempting to mount them from a command line I get the following: $ udisksctl mount -b /dev/mmcblk0p1 AUTHENTICATING FOR org.freedesktop.udisks2.filesystem-mount === Authentication is required to mount MS (/dev/mmcblk0p1) Multiple identities can be used for authentication: 1. Jamin Collins,,, (jcollins) 2. Jamin Collins,,, (jcollins) Choose identity to authenticate as (1-2): This is presumably because my user is in both the admin and sudo groups. If I remove the user from the sudo group the prompt changes: $ sudo deluser jcollins sudo [sudo] password for jcollins: Removing user `jcollins' from group `sudo' ... Done. $ udisksctl mount -b /dev/mmcblk0p1 AUTHENTICATING FOR org.freedesktop.udisks2.filesystem-mount === Authentication is required to mount MS (/dev/mmcblk0p1) Authenticating as: Jamin Collins,,, (jcollins) Password: So, there are a couple of problems here. First is the fact that a local admin is being prompted for authentication to mount local or removable file systems. Second, that the authentication system can't determine that accounts are, in fact, identical. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 07:35:31 2013 InstallationDate: Installed on 2009-12-21 (1414 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True PackageArchitecture: all SourcePackage: policykit-desktop-privileges UpgradeStatus: Upgraded to saucy on 2013-11-04 (0 days ago) ** Affects: policykit-desktop-privileges (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/1248249 Title: regression: local admin not authorized for many tasks Status in “policykit-desktop-privileges” package in Ubuntu: New Bug description: Similar reports to this were filed previously: #1005643 & #1069234 While 1069234 was marked as a duplicate of 1005643, and 1005643 was marked as resolved, this problem still exists with 13.10. When attempting to mount any of my local volumes through a graphical file manager (such as Thunar or Nautilus), I'm greeted with a dialog like the following: Failed to mount "keys". Not authorized to perform operation. When attempting to mount them from a command line I get the following: $ udisksctl mount -b /dev/mmcblk0p1 AUTHENTICATING FOR org.freedesktop.udisks2.filesystem-mount === Authentication is required to mount MS (/dev/mmcblk0p1) Multiple identities can be used for authentication: 1. Jamin Collins,,, (jcollins) 2. Jamin Collins,,, (jcollins) Choose identity to authenticate as (1-2): This is presumably because my user is in both the admin and sudo groups. If I remove the user from the sudo group the prompt changes: $ sudo deluser jcollins sudo [sudo] password for jcollins: Removing user `jcollins' from group `sudo' ... Done. $ udisksctl mount -b /dev/mmcblk0p1 AUTHENTICATING FOR org.freedesktop.udisks2.filesystem-mount === Authentication is required to mount MS (/dev/mmcblk0p1) Authenticating as: Jamin Collins,,, (jcollins) Password: So, there are a couple of problems here. First is the fact that a local admin is being prompted for authentication to mount local or removable file systems. Second, that the authentication system can't determine that accounts are, in fact, identical. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 07:35:31 2013 InstallationDate: Installed on 2009-12-21 (1414 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True PackageArchitecture: all SourcePackage: policykit-desktop-privileges UpgradeStatus: Upgraded to saucy on 2013-11-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1248249/+subscriptions -- Mailing list: https://launchpad.net/~deskt
[Desktop-packages] [Bug 1075478] Re: bluetooth keyboards and mice not working after suspend/resume
The attached script disconnects all currently attached bluetooth devices on suspend, thus completely avoiding this bug. Place the script in /etc/pm/sleep.d/10_bluetooth-input, and ensure that its executable. ** Attachment added: "/etc/pm/sleep.d/10_bluetooth-input" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1075478/+attachment/3500463/+files/10_bluetooth-input -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1075478 Title: bluetooth keyboards and mice not working after suspend/resume Status in xserver-xorg-input-evdev: Unknown Status in “xserver-xorg-input-evdev” package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 12.10 I encountered the following problem: I have my apple wireless bluetooth keyboard paired up to Ubuntu, and it works fine when I boot up my laptop (HP EliteBook 8530w) as soon as I hit the login screen. However, if I then suspend and resume my laptop again, the bluetooth keyboard does not respond anymore. According to the bluetooth GUI applet it is still succesfully paired up and connected, and I see the green light on my keyboard blinking a few times when I hit a key for the first time after resume which is also the case when it _does_ work, but I get no response whatsoever from Ubuntu when typing on my keyboard. "sudo service bluetooth restart" does not work. Please let me know what additional information to provide. To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/1075478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1075478] Re: Apple wireless bluetooth keyboard not working after suspend/resume
To be clear, this issue is present with any bluetooth connected evdev input (keyboard or mouse) that is not disconnected prior to a suspend resume cycle. ** Summary changed: - Apple wireless bluetooth keyboard not working after suspend/resume + bluetooth keyboards and mice not working after suspend/resume -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1075478 Title: bluetooth keyboards and mice not working after suspend/resume Status in xserver-xorg-input-evdev: Unknown Status in “xserver-xorg-input-evdev” package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 12.10 I encountered the following problem: I have my apple wireless bluetooth keyboard paired up to Ubuntu, and it works fine when I boot up my laptop (HP EliteBook 8530w) as soon as I hit the login screen. However, if I then suspend and resume my laptop again, the bluetooth keyboard does not respond anymore. According to the bluetooth GUI applet it is still succesfully paired up and connected, and I see the green light on my keyboard blinking a few times when I hit a key for the first time after resume which is also the case when it _does_ work, but I get no response whatsoever from Ubuntu when typing on my keyboard. "sudo service bluetooth restart" does not work. Please let me know what additional information to provide. To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/1075478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1075478] Re: Apple wireless bluetooth keyboard not working after suspend/resume
This is a seriously annoying bug. I'm not sure this is reported against the correct subsystem. This strikes me as more an evdev or udev issue than a bluez issue. To work around this for now, I've got a script that will disables any xinput device with "mouse" in it's name. ** Attachment added: "disable any xinput with mouse in its name" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1075478/+attachment/3497864/+files/kick-mice ** Package changed: bluez (Ubuntu) => xserver-xorg-input-evdev (Ubuntu) ** Also affects: evdev via https://bugzilla.redhat.com/show_bug.cgi?id=811534 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1075478 Title: Apple wireless bluetooth keyboard not working after suspend/resume Status in xserver-xorg-input-evdev: Unknown Status in “xserver-xorg-input-evdev” package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 12.10 I encountered the following problem: I have my apple wireless bluetooth keyboard paired up to Ubuntu, and it works fine when I boot up my laptop (HP EliteBook 8530w) as soon as I hit the login screen. However, if I then suspend and resume my laptop again, the bluetooth keyboard does not respond anymore. According to the bluetooth GUI applet it is still succesfully paired up and connected, and I see the green light on my keyboard blinking a few times when I hit a key for the first time after resume which is also the case when it _does_ work, but I get no response whatsoever from Ubuntu when typing on my keyboard. "sudo service bluetooth restart" does not work. Please let me know what additional information to provide. To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/1075478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 825897] Re: nm-applet becomes unresponsive, requiring a restart
** Summary changed: - network-manager becomes unresponsive, requiring a service restart + nm-applet becomes unresponsive, requiring a restart ** Description changed: - After network-manager has been running for a while (overnight) it becomes unresponsive: + After nm-applet has been running for a while (overnight) it becomes unresponsive: - unable to uncheck "Enable Wireless" - doesn't list the numerous additional networks under "More Networks" - doesn't find new networks - This behavior persists until the network-manager service is restarted - via: sudo service network-manager restart + This behavior persists until the applet is restarted via something like: + killall nm-applet; sleep 1; nohup nm-applet & - ProblemType: Bug - DistroRelease: Ubuntu 11.04 - Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 - ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 - Uname: Linux 2.6.38-10-generic x86_64 - NonfreeKernelModules: nvidia - Architecture: amd64 - Date: Sat Aug 13 09:25:50 2011 - IfupdownConfig: - auto lo - iface lo inet loopback - InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) - NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - ProcEnviron: - LANGUAGE=en_US:en - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: network-manager - UpgradeStatus: Upgraded to natty on 2011-07-25 (19 days ago) + This problem has been consistently present since 11.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/825897 Title: nm-applet becomes unresponsive, requiring a restart Status in Network Manager GNOME Applet: New Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: After nm-applet has been running for a while (overnight) it becomes unresponsive: - unable to uncheck "Enable Wireless" - doesn't list the numerous additional networks under "More Networks" - doesn't find new networks This behavior persists until the applet is restarted via something like: killall nm-applet; sleep 1; nohup nm-applet & This problem has been consistently present since 11.04 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/825897/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 825897] Re: network-manager becomes unresponsive, requiring a service restart
Should also be noted that simply killing nm-applet and restarting it are sufficient to restore functionality: killall nm-applet; sleep 1; nohup nm-applet & ** Bug watch added: GNOME Bug Tracker #691516 https://bugzilla.gnome.org/show_bug.cgi?id=691516 ** Also affects: network-manager-applet via https://bugzilla.gnome.org/show_bug.cgi?id=691516 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/825897 Title: network-manager becomes unresponsive, requiring a service restart Status in Network Manager GNOME Applet: Unknown Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: After network-manager has been running for a while (overnight) it becomes unresponsive: - unable to uncheck "Enable Wireless" - doesn't list the numerous additional networks under "More Networks" - doesn't find new networks This behavior persists until the network-manager service is restarted via: sudo service network-manager restart ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Aug 13 09:25:50 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to natty on 2011-07-25 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/825897/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 825897] Re: network-manager becomes unresponsive, requiring a service restart
All that is necessary to reproduce this bug is lots of changes in the wireless networks seen by the system. Nothing more. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/825897 Title: network-manager becomes unresponsive, requiring a service restart Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: After network-manager has been running for a while (overnight) it becomes unresponsive: - unable to uncheck "Enable Wireless" - doesn't list the numerous additional networks under "More Networks" - doesn't find new networks This behavior persists until the network-manager service is restarted via: sudo service network-manager restart ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Aug 13 09:25:50 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to natty on 2011-07-25 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/825897/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1055238] Re: PCI/internal sound card not detected on Toshiba P855-S5200 Laptop
I'm also finding that alsa-hda-dkms won't install under 12.10 and need it to solve #1064621. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1055238 Title: PCI/internal sound card not detected on Toshiba P855-S5200 Laptop Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: It used to work, but now with the 3.5.0 kernel, alsa-hda-dkms won't install Ubuntu Quantal 12.10 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: Date: Sun Sep 23 21:08:44 2012 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.70 dmi.board.asset.tag: * dmi.board.name: QFKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr1.70:bd06/22/2012:svnTOSHIBA:pnSatelliteP855:pvrPSPKAU-00F009:rvnTOSHIBA:rnQFKAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.name: Satellite P855 dmi.product.version: PSPKAU-00F009 dmi.sys.vendor: TOSHIBA modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-09-23T20:51:29.873787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1055238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1069234] Re: regression: local admin not authorized for many tasks
The attached file is a very permissive work around for the issue, it will allow local admins to do any of the potential udisk2 actions. Simply place it in /var/lib/polkit-1/localauthority/50-local.d. ** Attachment added: "udisk2.pkla" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1069234/+attachment/3407659/+files/udisk2.pkla -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1069234 Title: regression: local admin not authorized for many tasks Status in “gnome-disk-utility” package in Ubuntu: Confirmed Bug description: With 12.10 it looks like gnome-disk-utility has moved to using udisks2 behind the scenes. However, it appears that polkit entries were not created for most of the potential actions that can be taken within gnome-disks. Many of the actions result in an error like the following: An error occured Not authorized to perform operation (udisks-error-quark, 4) I've received the above error when trying to use gnome-disks start a benchmark of a volume. This worked fine under 12.04 (via the gnome- disks precursor palimpsest and udisks). Digging into this, it appears that there are a total of 38 possible polkit actions and local admins are only authorized by default for a total of three of them (via 10-vendor.d/com.ubuntu.desktop.pkla): org.freedesktop.udisks2.filesystem-mount-system org.freedesktop.udisks2.encrypted-unlock-system org.freedesktop.udisks2.filesystem-fstab Contrast this with the authorization for the previous udisk activities: org.freedesktop.udisks.filesystem-* org.freedesktop.udisks.drive-ata-smart* Which covers 10 actions from what I can see. For parity with previous releases I believe the following actions also need to be authorized for local admins: org.freedesktop.udisks2.filesystem-mount [1] org.freedesktop.udisks2.filesystem-unmount-others [1] org.freedesktop.udisks2.ata-smart-* [2] I'm sure there are others as there doesn't appear to be a direct 1:1 translation for some of the permissions. This is a regression with regard to the previous 12.04 release and what local admin users were authorized to do. [1] - covered previously by org.freedesktop.udisks.filesystem-* [2]- covered previously by org.freedesktop.udisks.drive-ata-smart* ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-disk-utility 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Sat Oct 20 14:45:17 2012 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to quantal on 2012-10-12 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1069234/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1069234] [NEW] regression: local admin not authorized for many tasks
Public bug reported: With 12.10 it looks like gnome-disk-utility has moved to using udisks2 behind the scenes. However, it appears that polkit entries were not created for most of the potential actions that can be taken within gnome-disks. Many of the actions result in an error like the following: An error occured Not authorized to perform operation (udisks-error-quark, 4) I've received the above error when trying to use gnome-disks start a benchmark of a volume. This worked fine under 12.04 (via the gnome-disks precursor palimpsest and udisks). Digging into this, it appears that there are a total of 38 possible polkit actions and local admins are only authorized by default for a total of three of them (via 10-vendor.d/com.ubuntu.desktop.pkla): org.freedesktop.udisks2.filesystem-mount-system org.freedesktop.udisks2.encrypted-unlock-system org.freedesktop.udisks2.filesystem-fstab Contrast this with the authorization for the previous udisk activities: org.freedesktop.udisks.filesystem-* org.freedesktop.udisks.drive-ata-smart* Which covers 10 actions from what I can see. For parity with previous releases I believe the following actions also need to be authorized for local admins: org.freedesktop.udisks2.filesystem-mount [1] org.freedesktop.udisks2.filesystem-unmount-others [1] org.freedesktop.udisks2.ata-smart-* [2] I'm sure there are others as there doesn't appear to be a direct 1:1 translation for some of the permissions. This is a regression with regard to the previous 12.04 release and what local admin users were authorized to do. [1] - covered previously by org.freedesktop.udisks.filesystem-* [2]- covered previously by org.freedesktop.udisks.drive-ata-smart* ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-disk-utility 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Sat Oct 20 14:45:17 2012 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to quantal on 2012-10-12 (8 days ago) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal regression-release ** Description changed: With 12.10 it looks like gnome-disk-utility has moved to using udisks2 behind the scenes. However, it appears that polkit entries were not created for most of the potential actions that can be taken within gnome-disks. Many of the actions result in an error like the following: An error occured Not authorized to perform operation (udisks-error-quark, 4) - I've received the above error when trying to use gnome-disks to do things such as: - - starting a benchmark of a volume - - All of these actions worked fine under 12.04 (via the gnome-disks + I've received the above error when trying to use gnome-disks start a + benchmark of a volume. This worked fine under 12.04 (via the gnome-disks precursor palimpsest and udisks). Digging into this, it appears that there are a total of 38 possible polkit actions and local admins are only authorized by default for a total of three of them (via 10-vendor.d/com.ubuntu.desktop.pkla): org.freedesktop.udisks2.filesystem-mount-system org.freedesktop.udisks2.encrypted-unlock-system org.freedesktop.udisks2.filesystem-fstab Contrast this with the authorization for the previous udisk activities: org.freedesktop.udisks.filesystem-* org.freedesktop.udisks.drive-ata-smart* Which covers 10 actions from what I can see. For parity with previous releases I believe the following actions also need to be authorized for local admins: org.freedesktop.udisks2.filesystem-mount [1] org.freedesktop.udisks2.filesystem-unmount-others [1] org.freedesktop.udisks2.ata-smart-* [2] I'm sure there are others as there doesn't appear to be a direct 1:1 translation for some of the permissions. This is a regression with regard to the previous 12.04 release and what local admin users were authorized to do. [1] - covered previously by org.freedesktop.udisks.filesystem-* [2]- covered previously by org.freedesktop.udisks.drive-ata-smart* ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-disk-utility 3.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Sat Oct 20 14:45:17 2012 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to qua
[Desktop-packages] [Bug 29263] Re: No nfs:// support
Per the referenced site, nfs-lan does not appear to have support for Nautilus 3.x -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-vfs2 in Ubuntu. https://bugs.launchpad.net/bugs/29263 Title: No nfs:// support Status in Gnome VFS Filesystem Abstraction library: Won't Fix Status in GVFS: New Status in “gnome-vfs2” package in Ubuntu: Won't Fix Status in “gvfs” package in Ubuntu: Triaged Status in “gnome-vfs2” package in Baltix: New Bug description: Once, some time ago, gnome-vfs had support for nfs:// URLs. At some point there wasn't anyone maintaining it and it got broken so it just configured out. I tried out KDE for a few days and found that it had nfs:// support in it's kio stuff and it worked famously. It would be nice to see nfs:// support in gnome-vfs again. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-vfs/+bug/29263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 839444] Re: Gnome uses two different ssh agents depending on how program is launched
For xbindkeys users, this bug is reported against Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628654 The work around is to simply create a ~/.xbindkeys.noauto file (note the leading period on the file name). This will prevent the Xsession startup script from launching xbindkeys too early. Then start xbindkeys via your normal mechanism. ** Bug watch added: Debian Bug tracker #628654 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628654 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/839444 Title: Gnome uses two different ssh agents depending on how program is launched Status in The GNOME 2 Session Manager: Confirmed Status in “gnome-session” package in Ubuntu: Triaged Status in “gnome-session” package in Debian: New Bug description: If a shell is launched through the menu SSH_AUTH_SOCK will have a value of the form /tmp/keyring-xx/ssh. If a keyboard shortcut is created through System > Preferences > Keyboard Shortcuts and that shortcut is used to launch a shell, then SSH_AUTH_SOCK will have a value of the form /tmp/ssh-x#/agent.#. All shells in the session should by default be using the same ssh- agent. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-session-bin 2.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-33.72-generic 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-generic i686 Architecture: i386 Date: Fri Sep 2 12:06:28 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) ProcEnviron: PATH=(custom, user) LANG=en_DK.utf8 SHELL=/bin/bash SourcePackage: gnome-session To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/839444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 151365] Re: Autosave doesn't work for Unsaved Documents
Great logic. So, since cars and planes shouldn't crash perhaps we don't need safety features developed for them? Seriously, this is faulty logic. Software will from time to time crash. Sure, it shouldn't. But if reasonable steps can be taken to prevent data loss, they should. This doesn't really seem like an unreasonable step. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/151365 Title: Autosave doesn't work for Unsaved Documents Status in Light-Weight Text Editor for Gnome: New Status in “gedit” package in Ubuntu: Triaged Bug description: Autosave doesn't happen if the document has *never* been saved. It should, since data can be lost if there is a crash while an unsaved document is in the editor. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/151365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
