Bug 483415 - gnome-keyring-daemon claims inablity to connect to dbus session
gnome-keyring-daemon claims inablity to connect to dbus session
Product: Fedora
Classification: Fedora
Component: gnome-keyring (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Tomáš Bžatek
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-01-31 18:44 EST by Michal Jaegermann
Modified: 2015-03-03 17:34 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 07:10:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2009-01-31 18:44:26 EST
Description of problem:

After graphics session starts I have in /var/log/messages:

gnome-keyring-daemon[3425]: couldn't connect to dbus session bus: dbus-launch failed to autolaunch D-Bus session: No protocol specified#012Autolaunch error: X11 initialization failed.
gnome-keyring-daemon[3430]: The daemon was already initialized.

There is usually a three seconds gap in timestamps between such two entries although on occasions it can be as small as one second.

The above despite that 'pgrep -f -l dbus' shows things like those:

3464 dbus-launch --sh-syntax --exit-with-session
3467 /bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session

OTOH 'pgrep -f -l gnome-keyring-daemon' shows that process as running
but with a pid from the second message (3430 in this case and only with it).

Version-Release number of selected component (if applicable):

How reproducible:
on every sesssion start
Comment 1 Colin Walters 2009-02-02 20:56:15 EST
Hmm, probably gnome-keyring is getting executed from the PAM context, and is trying to connect to the session bus.  But because there is no session bus at that point, one gets autolaunched.

This was supposed to be fixed from this bug:

Comment 2 Bug Zapper 2009-06-09 07:00:49 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 3 Bug Zapper 2010-04-27 08:50:14 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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: 
Comment 4 Bug Zapper 2010-06-28 07:10:34 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.