Bug 200800 - Unable to determine address of message bus
Summary: Unable to determine address of message bus
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: GConf2
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-31 18:43 UTC by Pete Zaitcev
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-03-06 20:19:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Error dialog (15.77 KB, image/png)
2006-07-31 18:43 UTC, Pete Zaitcev
no flags Details

Description Pete Zaitcev 2006-07-31 18:43:16 UTC
Description of problem:

I ran "yum update" and now at every login I receive an error dialog:
"Unable to determine the address of the message bus".

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

[zaitcev@niphredil ~]$ rpm -q GConf GConf2 dbus
GConf-1.0.9-20
GConf2-2.14.0-2.1
dbus-0.90-8
[zaitcev@niphredil ~]$

How reproducible:

Happens every time, but it's unknown what to do to reproduce on demand.

Steps to Reproduce:

Unknown
  
Actual results:

Error dialog (see attachement)

Expected results:

No error dialog

Additional info:

The dbus processes seem to be operating, but perhaps some /var/run
file is missing or other dbus error. I have no idea how to narrow
the bug down to the right component.

Comment 1 Pete Zaitcev 2006-07-31 18:43:16 UTC
Created attachment 133341 [details]
Error dialog

Comment 2 Ray Strode [halfline] 2007-03-06 19:01:52 UTC
are you still seeing this?

what's the output of echo $DBUS_SESSION_BUS_ADDRESS at a terminal?

do you get to that dialog from a gdm login or text login followed by startx ?

Comment 3 Pete Zaitcev 2007-03-06 20:19:02 UTC
No, this is gone now. Unfortunately, I do not remember exactly what I've done
to get rid of this. It was not related to dbus, but rather to some GNOME thing.
I forgot that I filed the bug, sorry. I should've updated the report.
Now I think that I removed GConf altogether and that fixed it.


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