hald-runner dies in 0.5.10

Bug #163886 reported by Jerome Haltom on 2007-11-19
2
Affects Status Importance Assigned to Milestone
HAL
Fix Released
High
hal (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: hal

Upon upgading hal in latest hoary, hal fails to start, which breaks it's upgrade:

Setting up hal (0.5.10-2ubuntu1) ...
 * Reloading system message bus config... [ OK ]
 * Starting Hardware abstraction layer hald invoke-rc.d: initscript hal, action "start" failed.
dpkg: error processing hal (--configure):
 subprocess post-installation script returned error exit status 1

If I run hald manually with --verbose=yes --daemon=no, it seems to initalize, print out tons of stuff, and then end with:

3:12:37.944 [I] hald_runner.c:110: runner_server_message_handler: destination=(null) obj_path=/org/freedesktop/DBus/Local interface=org.freedesktop.DBus.Local method=Disconnected
13:12:37.944 [I] hald_runner.c:149: runner process disconnected
*** [DIE] hald_runner.c:runner_died():202 : Runner died
13:12:37.946 [D] addon-cpufreq.c:1099: Received DBus message with member Disconnected
13:12:37.946 [D] addon-cpufreq.c:1100: Received DBus message with path /org/freedesktop/DBus/Local
root@station-1:~# libhal.c 4456 : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
libhal.c 4456 : Connection is closed
libhal.c 4456 : Connection is closed

So the runner is dying?

https://bugs.launchpad.net/ubuntu/+source/hal/+bug/163886

I filed this bug. It appears as if 0.5.10 will not properly start on my machine. hald-runner "dies". I do not know how to identify why, since it is started as one of a huge number of sub processes.

3:12:37.944 [I] hald_runner.c:110: runner_server_message_handler: destination=(null) obj_path=/org/freedesktop/DBus/Local interface=org.freedesktop.DBus.Local method=Disconnected
13:12:37.944 [I] hald_runner.c:149: runner process disconnected
*** [DIE] hald_runner.c:runner_died():202 : Runner died
13:12:37.946 [D] addon-cpufreq.c:1099: Received DBus message with member Disconnected
13:12:37.946 [D] addon-cpufreq.c:1100: Received DBus message with path /org/freedesktop/DBus/Local
root@station-1:~# libhal.c 4456 : Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
libhal.c 4456 : Connection is closed
libhal.c 4456 : Connection is closed

Same issue here with 0.5.10 and git master on one system. Works fine on many other systems with the same software versions. This is on Linux 2.6.23.9 on x86.

This happening causes a large number of addin processes to remain alive... and results in multiple runs and failures of hald leaving behind more and more addin processes.

Would it not make sense, as well, for addin processes to die when they lose contact with hald? Perhaps a seperate bug.

Changed in hal:
status: Unknown → Confirmed
Kjell Braden (afflux) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Is this still a problem for you? If so, please follow the "How to file" procedure described at [WWW] https://wiki.ubuntu.com/DebuggingHal and attach the requested files here.

Changed in hal:
assignee: nobody → afflux
status: New → Incomplete

Could you please check if the HAL v0.5.11RC2 and the latest hal-info works for you (from http://hal.freedesktop.org/releases/) or if the problem is present?

I can't speak for the original reporter, however, my system that had similar problems seems to work fine with git 2008-03-01, can't test with 0.5.11RC2 right now.

okay, then I close the bug now. If the problem is for the original reporter present, please reopen.

Changed in hal:
status: Confirmed → Fix Released
Kjell Braden (afflux) wrote :

Closing as upstream marked it as released.

Changed in hal:
assignee: afflux → nobody
status: Incomplete → Fix Released
Changed in hal:
importance: Unknown → High
Changed in hal:
importance: High → Unknown
Changed in hal:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.