After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 577587 - gnome-keyring-daemon stalls after upgrading to jaunty beta
gnome-keyring-daemon stalls after upgrading to jaunty beta
Status: RESOLVED DUPLICATE of bug 575247
Product: gnome-keyring
Classification: Core
Component: general
2.26.x
Other All
: Normal major
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-04-01 08:23 UTC by bjoern
Modified: 2009-04-10 20:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description bjoern 2009-04-01 08:23:29 UTC
Please describe the problem:
After upgrading to jaunty gnome-keyring-daemon wound not run. Trying to save any passwords (e.g. mail-notification) it would say it could not save any. When I followed the instructions in another forum saying one should remove ~/.gnome2/keyrings folder and restart, it firstly went well letting gnome-keyring-daemon come up again and save passwords. After another update (uptodate version from ubuntu repositories) it, however, started stalling again after I logged into my account. Now, even the solution mentioned above does not work anymore.

Starting gnome-keyring-daemon from console shows the following error message:

** Message: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files
GNOME_KEYRING_SOCKET=/tmp/keyring-2cOEK8/socket
SSH_AUTH_SOCK=/tmp/keyring-2cOEK8/socket.ssh
GNOME_KEYRING_PID=5785

I started this bug report using apport ('ubuntu-bug gnome-keyring'). Hopefully, the report is attached to this entry.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: gnome-keyring 2.26.0-0ubuntu3
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-keyring
Uname: Linux 2.6.28-11-generic i686

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?
No, but every time I reboot after the problem appears for the fist time after deleting '~/.gnome2/keyrings' and '~/.seahorse'.

Other information:
GNU gdb 6.8-debian
Copyright (C) 2008 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 "i486-linux-gnu"...
(no debugging symbols found)
(gdb) handle SIG33 pass nostop noprint
Signal        Stop	Print	Pass to program	Description
SIG33         No	No	Yes		Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/gnome-keyring 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb7301a30 (LWP 16254)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
usage: gnome-keyring command [options]
commands: import

Program exited with code 02.
(gdb) backtrace full
No stack.
(gdb) info registers
The program has no registers now.
(gdb) thread apply all backtrace
No registers.
(gdb) quit
Comment 1 Stef Walter 2009-04-02 03:35:39 UTC
This is an odd message:

** Message: couldn't set environment variable in session: The name
org.gnome.SessionManager was not provided by any .service files

Out of interest, are you using GNOME as your desktop environment. If not, which one are you using, as I'll need to test with it and see if we can solve the problem.
Comment 2 Alex Hofbauer 2009-04-03 17:17:03 UTC
Just wanted to confirm that problem, same on Debian/unstable here.

Temp workaround (keyring won't get unlocked though) is to add it so session programs.
Comment 3 Jeremy Nickurak 2009-04-03 19:26:35 UTC
I'm seeing the same problem under jaunty, with the gnome desktop environment.

Potentially related distribution bugs:

https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/352269
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/344014
Comment 4 Stef Walter 2009-04-10 20:06:54 UTC
Thanks for the bug report. I believe this is a duplicate of bug #575247. Please reopen if that's not the case. 

*** This bug has been marked as a duplicate of 575247 ***