Red Hat Bugzilla – Bug 188972
GNOME Power Manager won't start
Last modified: 2013-03-13 00:50:16 EDT
Description of problem: The GNOME power manager complains that it cannot start
until the dbus session service is started, but I have it started and listed in
the GNOME session.
Version-Release number of selected component (if applicable): 2.14.1-1
How reproducible: Everytime I log in.
Steps to Reproduce:
1.Turn on power manager.
Actual results: Power manager error dialog pops up with the message that states
that the power manager cannot start until the dbus session service is started.
It goes on to say that you can start the dbus session service manually with the
eval 'dbus-launch --auto-syntax'
Expected results: Power manager should start, because the dbus session service
is started, and is listed in the GNOME session.
Created attachment 127736 [details]
Screen shot that shows the error dialog, and the contents of the GNOME session side-by-side.
I'm lost to why whis would happen. J5, got any ideas?
Just got back from vacation. Is dbus running?
The attached screen shot says it all! DBUS is running.
Arggg, error message is wrong - Richard take that out. You can't just start a
session bus and expect it to work. Plus dbus-launch is not the same as dbus.
dbus-launch just launches dbus and manages its lifecycle. The dbus session
should be started by your xsession. Please reboot, login fresh and attach the
output of ps -aux | grep dbus to this bug. Thanks.
Error messages should never give instructions, just diagnostics because they
always end up confusing the user.
Created attachment 127921 [details]
ps aux | grep dbus output
Here is the ps output
(In reply to comment #5)
> Error messages should never give instructions, just diagnostics because they
> always end up confusing the user.
2006-04-18 Richard Hughes <email@example.com>
* src/gpm-main.c (main): Don't tell the user to use dbus-launch as it's the
wrong way to do this. rh:188972
I'll commit this to 2-14 and 2-15 now.
Andrig, did you reboot? You have 13 dbus instances running. Another thing to
do is check to see if /usr/bin/dbus-daemon exists. It shouldn't and if it is
still there then you had an upgrade error and I would bet rpm -q dbus would show
more than one version installed.
I hadn't rebooted at that time, but I had switched runlevels a number of times.
I do have the /usr/bin/dbus-daemon, and rpm -q shows two dbus, but I believe
they are the 32-bit version and the 64-bit version, not two different ones.
Here is what it looks like:
[root@localhost bin]# ls -laF dbus-daemon
-rwxr-xr-x 1 root root 596744 Aug 29 2005 dbus-daemon*
[root@localhost bin]# rpm -q dbus
I have a lot of 32-bit and 64-bit applications mixed on my machine, and that is
probably why I have two. Can I just remove the dbus-daemon from /usr/bin?
Have you ever installed dbus from source? Do a rpm -qf /usr/bin/dbus-daemon and
post the results. Thanks.
Interestingly, that file is not owned by any package, as you can see here:
[root@localhost ~]# rpm -qf /usr/bin/dbus-daemon
file /usr/bin/dbus-daemon is not owned by any package
But, I have never installed dbus from source before.
For some reason it never got removed on upgrade. Remove it and reboot to see if
that fixes things.
I removed it and rebooted, and now everything is working. Thanks for the help.
I really appreciate it.