Description of problem: I've got the below message in my daily logwatch email (from /var/log/messages): **Unmatched Entries** gdm-session-worker: gnome-keyring-daemon: couldn't lookup keyring component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session)gnome-keyring-daemon: couldn't lookup ssh component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session)gnome-keyring-daemon: couldn't lookup pkcs11 component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session): 2 Time(s) Version-Release number of selected component (if applicable): gnome-keyring-2.24.1-1.fc10.i386 How reproducible: happened once
This is: http://bugzilla.gnome.org/show_bug.cgi?id=558181
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is happening on a daily basis for me. I also notice a similar message when using gedit after 'su' to root in a console: (gedit:8291): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: 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.)
*** Bug 474993 has been marked as a duplicate of this bug. ***
It looks like this bug is fixed upstream: http://svn.gnome.org/viewvc/gnome-keyring?view=revision&revision=1381
Hasn't seen this bug for ages. Anybody else does?
Unfortunately it still persists on my machine.
(In reply to comment #7) > Unfortunately it still persists on my machine. Oh well, what version of gnome-keyring package you have?
gnome-keyring-2.24.1-1.fc10.x86_64 gnome-keyring-2.24.1-1.fc10.i386 -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
(In reply to comment #7) > Unfortunately it still persists on my machine. Me too, with gnome-keyring-2.24.1-1.fc10.i386 . In fact, the package was never updated since Fedora 10 release. Also, the next upstream stable release was in GNOME 2.26, so the patch I mentioned in comment #5 should be backported to fix this bug for Fedora 10. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
With gnome-keyring-2.25.92-1.fc11.x86_64 (and it's dependencies)from rawhide the problem disappears. Can we maybe push that to F10?
Is somebody working on this yet? --------------------- Connections (secure-log) Begin ------------------------ **Unmatched Entries** gdm-session-worker: gnome-keyring-daemon: couldn't lookup keyring component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session)gnome-keyring-daemon: couldn't lookup ssh component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session)gnome-keyring-daemon: couldn't lookup pkcs11 component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session): 1 Time(s) ---------------------- Connections (secure-log) End -------------------------
I'm also seeing it still (since F10 installation) in daily logwatch reports. Now that F11 release is only days ahead, will this be fixed in F10?
Not seeing this anymore since I upgraded to F11.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
In reference to comment #14, after installing (clean installation of) Fedora 11 I don't see this either. WORKSFORME, that is...
Let's kill it then.