** Tags added: bugpattern-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/813755
Title:
gnome-keyring-daemon fails to start as it can't get capabilities
To manage notifications about this bug
So...the livecd filesystem doesn't seem to support file caps.
We probably need ubiquity to manually set file caps on this binary after
copying it to the hard disk during installation.
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
from irc discussion:
ev so the package in question should carry a script in
/usr/lib/ubiquity/target-config to set things up properly
see jockey for an example
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~mathieu-tl/gnome-keyring/filecaps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/813755
Title:
gnome-keyring-daemon fails to start as it can't get capabilities
To manage
This bug was fixed in the package gnome-keyring - 3.1.1-0ubuntu3
---
gnome-keyring (3.1.1-0ubuntu3) oneiric; urgency=low
* debian/patches/99git_fs_caps_11a5d41.patch: cherry-pick patch from git:
improve checks for FS capabilities.
*
This won't need a change in ubiquity after all, we ship a hook script in
gnome-keyring to take care of the step of fixing permissions at the end
of the install (see gnome-keyring changelog entry about target-config
script above). Marking the ubiquity task Invalid.
** Changed in: ubiquity (Ubuntu)
** Also affects: gnome-keyring (Ubuntu Oneiric)
Importance: Undecided
Status: Fix Released
** Also affects: ubiquity (Ubuntu Oneiric)
Importance: Undecided
Status: Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Actually, I was looking at upstream git...our version is too old. We should
update to 3.1.4 to get these two commits:
http://git.gnome.org/browse/gnome-keyring/commit/daemon/gkd-capability.c?id=ad67edd5fb25fca974f10f568c31a2316d728b79
will those commit fix the issue or just workaround the fact that the
setcap call didn't happen for some reason?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/813755
Title:
gnome-keyring-daemon
oh, also Chrisccoulson is working on the gnome-keyring update, it's just
taking some time because it requires a new depends to be packaged first
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/813755
The commits will let gnome-keyring start anyway, even if setcap didn't
work, by using insecure memory. Ideally, we'd also have setcap working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/813755
Marc Just a fresh install from from tuesday's image had the same issue
and this temp work around fixed it.
I'll try a more current iso and see if it is still the same latter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, I've successfully reproduced this issue by installing a clean i386
VM with the 2011-07-21 live cd.
** Changed in: gnome-keyring (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like gnome-keyring now needs file capabilities. The postinst sets
capabilities, but I suspect the setcap utility isn't installed when
gnome-keyring gets installed on new installations.
Workaround:
sudo setcap CAP_IPC_LOCK=ep /usr/bin/gnome-keyring-daemon
--
You received this bug
Also, it should be able to run even if the filesystem capabilities
aren't set, but for some reason, it's getting CAPNG_FAIL...needs
investigation...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I wouldn't advise using setuid here. This will probably change the
permissions of the files in your home directory, and cause problems when
the actual issue is fixed and there's an update, where gnome-keyring
won't be able to read your keyring files.
--
You received this bug notification because
James, I can't reproduce this. Any ideas on how to reproduce?
Is this after you set up/copy over some keys?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/813755
Title:
gnome-keyring-daemon fails to
17 matches
Mail list logo
