gnome-keyring-daemon refuses to start

Bug #818018 reported by Pete Goodall
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-keyring (Ubuntu)
Incomplete
Low
Unassigned

Bug Description

I have just done a fresh install of Ubuntu 11.10 from the daily live CD from 29th July 2011. After installation, I could not connect to any wireless network or even my mobile broadband connection. I restored my home directory to see if maybe it was just the lack of a keyring and that still didn't help. Checking the wireless connections I noticed that a) none of my previously saved networks were listed and b) the one I had been trying to connect to was listed, but had no password filled in. I filled in the password for the WPA2 network and connected just fine. I checked seahorse to see if the password was saved and was informed seahorse couldn't connect to gnome-keyring-daemon. When I try to start the gnome-keyring-daemon from the command line, here is what I get:

$ gnome-keyring-daemon
gnome-keyring-daemon: error getting process capabilities, aborting

I'm not sure how to debug this, so please let me know what other information I can give you.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-keyring 3.1.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
Date: Fri Jul 29 13:21:10 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110728)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Pete Goodall (pgoodall) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Hey Pete, that seems similar to bug #813755, could you try if the workaround on
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/813755/comments/5
is working for you?

Changed in gnome-keyring (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pete Goodall (pgoodall) wrote :

Hi Seb,

Yes, the workaround (using setcap) seems to fix the issue.

Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

The fix from comment 5 on #813755 works for me as well. Marking as a dupe

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.