Bugzilla – Bug 149464
current hal-resmgr patch (52696) breaks hal/dbus
Last modified: 2006-02-17 08:58:33 UTC
after installing the hal-resmgr patch automounting stops working and powersaved cannot be started. /etc/init.d/haldaemon status -> unused lshal -> cannot connect to /var/run/dbus/system_socket: Connection refused powersave also writes to systemlog that it cannot connect to dbus
Are there any messages in the syslog? Please attach 500 lines of /var/log/messages here. Note: Product openSUSE is for the Wiki at opensuse.org only, not for the SUSE Linux distribution. Please change that to SUSE Linux X.X wheres X.X is the version you are reporting this bug for.
i cut out two corresponding parts from syslog ----------------------------------- Feb 6 19:04:32 hex [powersave]: ERROR (PM_Interface:241) Haldaemon not available. Most of acpi information for battery or ac adapter will not be available Feb 6 19:04:32 hex [powersave]: ERROR (openSystemConnection:469) dbus_bus_request_name(): Error. (No reply within specified time) Feb 6 19:04:33 hex [powersave]: ERROR (start:315) Could not establish DBus connection -------------cut-------------------------- Feb 7 13:16:39 hex [powersave]: WARNING (ACPI_Interface:47) could not set battery alarm Feb 7 13:16:39 hex [powersave]: WARNING (getCoresAffectedCpus:249) failed to get affected_cpus for cpu 0 Feb 7 13:16:39 hex 2253: arguments to dbus_bus_request_name() were incorrect, assertion "(error) == NULL || !dbus_error_is_set ((error))" failed in file dbus-bus.c line 652. This is normally a bug in some application using the D-BUS library. Feb 7 13:16:39 hex [powersave]: ERROR (openSystemConnection:277) dbus_bus_request_name(): Error. (No reply within specified time) Feb 7 13:16:39 hex [powersave]: ERROR (MainLoop:57) Error setting up connection to DBus system bus. Aborting... -------------cut-------------------------- here the exact output from lshal ------------------------------------------ hex:/var/log # lshal lshal version 0.5.4 error: dbus_bus_get: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
Have you tried booting with ACPI=off, does it work then?
(In reply to comment #3) > Have you tried booting with ACPI=off, does it work then? no, the problem remains the same, same errors however, if i do dbus stop/haldaemon stop/dbus start/haldaemon start the haldaemon seems to work, or at least "lshal" does the excpected. powersaved reports a succesfull start (of course when booted with acpi on), but when i run kpowerd it complains about powersaved not running, producing no output on syslog or in a shell. and automounting does not work, no matter what i do. but i don't know if this is connected to hal? because if i manually mount a dvd and do "ls" in that directory it hangs. i have to kill the ls process from another console (also, no errors on syslog)
What does all of the above have todo with hal-resmgr? To me it sounds like the dbus daemon is not running.
the problem appeared as soon as i installed the above mentiod patch. as i wrote in the summary "... breaks hal/_dbus_". of course all that could be caused by something else, but i do remember that hal-resmgr was the only packet connected to the dbus/hal "thing" that a patch was available for when i did the update tafter which the problems occured (after a reboot). as i wrote in comment #4 the haldaemon seems to work when i do dbus stop / start. i cannot tell wether the problem is caused by dbus or by hal, but the problem is that haldaemon will not start at bootup. powersaved is not working, automounting is not working even if i do dbus stop / start // hal stop / start, but lshal does work when i do that. i installed the -debug packages for dbus, hal and powersave but the information i provided is all i got. i collected all the information i could get but i'm not very experienced in debuging software, i'm just trying to help :) anyways, i reinstalled the whole system and right know i'm writing from a unpatched suse linux 10.0 and everything seems to be fine (kpowersave running, my usb stick got mounted automatically). i'm downloading all available patches right now and see if i can reproduce this.
have you been able to reproduce it?
no, everything seems to be fine now! the difference seems to be that when i had that problem there was a patch for hal-resmgr available but not for hal. i had a look at update/10.0/patches directory of ftp.suse.com and was supprissed to see that the patch for hal is dated 24.11.2005, whereas the hal-resmgr patch is dated 16.01.2006. sorry, i have no idea how that could have happened but it seems to be that somehow this was the source of all problems, because now my system is in the same state as before except the patch for hal.
*shrug* let's blame the moon ;-)