Bug 209598 - dbus daemon running but kpowersave can not connect
Summary: dbus daemon running but kpowersave can not connect
Status: RESOLVED DUPLICATE of bug 206352
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Hotplug (show other bugs)
Version: Final
Hardware: i686 SuSE Linux 10.1
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Danny Al-Gaaf
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-03 08:13 UTC by Elmar Stellnberger
Modified: 2006-10-09 15:08 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elmar Stellnberger 2006-10-03 08:13:42 UTC
Newly kpowersave reports the error message "DBUS daemon not running" more and more often. Likewise the Yast2 power management module says it can not connect to DBUS daemon though it is running in root mode. Nevertheless DBUS is running. Even restarting does not help.

>/etc/init.d/dbus status
Checking for service D-BUS daemon                                     running

boot:/home/elm/.mozilla/firefox> /etc/init.d/dbus restart
Shutting down D-BUS daemon                                            done
Starting D-BUS daemon                                                 done

> /etc/init.d/dbus stop
Shutting down D-BUS daemon                                            done
> /etc/init.d/dbus start
Starting D-BUS daemon                                                 done

> hal-device
error: libhal_ctx_init: (null): (null)

> hal-resmgr
ERROR! 10:11:50 hal-resmgr.c:411 main_dbus() - libhal_ctx_init: (null): (null)

As a consequence of this I can not use kpowersave to suspend or to query for the processor speed.
Comment 1 Danny Al-Gaaf 2006-10-09 15:08:01 UTC

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