[Pkg-utopia-maintainers] Bug#469528: hal upgrade problem from etch

[Chris Tracy]

Thanks, I rm'd /var/run/dbus/system_bus_socket and re-ran apt-get dist- 
upgrade.

I had not done any previous apt-get dist-upgrade's before, so I  
imagine this problem could be repeated by doing a clean install of  
etch, then configuring apt to use the 'unstable' release and running  
apt-get dist-upgrade.

This time, the apt-get dist-upgrade proceeeded but I still got a few  
error messages:

# rm  /var/run/dbus/system_bus_socket
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
7 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up hal (0.5.10+git20080301-1) ...
Reloading system message bus config...Failed to open connection to  
system message bus: Failed to connect to socket /var/run/dbus/ 
system_bus_socket: No such file or directory
invoke-rc.d: initscript dbus, action "force-reload" failed.
Can't start Hardware abstraction layer - please ensure dbus is running
Setting up gnome-power-manager (2.20.2-3) ...
Setting up gnome-mount (0.7-2) ...
Setting up gnome-volume-manager (2.22.1-1) ...
Setting up sound-juicer (2.20.1-1) ...
Setting up gnome-desktop-environment (1:2.20.2.2) ...
Setting up gnome (1:2.20.2.2) ...

Neither hald or dbus were running after doing this:

# ps auxwww|grep hal
root     30936  0.0  0.0   3116   700 pts/2    R+   12:53   0:00 grep  
hal
# ps auxwww|grep dbus
root     30938  0.0  0.0   3120   704 pts/2    R+   12:53   0:00 grep  
dbus

I didn't really feel like re-installing dbus so I just re-ran the dbus  
rc script.  As far as I can see, it seems to be ok now:

# /etc/init.d/dbus restart
Stopping System Tools Backends: system-tools-backendsstart-stop- 
daemon: warning: failed to kill 9715: No such process
.
Stopping Hardware abstraction layer: hald.
Stopping system message bus: dbus.
Starting system message bus: dbus.
Starting Hardware abstraction layer: hald.
Starting System Tools Backends: system-tools-backends.

# ps auxwww|grep hal
103      31022  3.0  0.2   5036  3040 ?        Ss   12:53   0:00 /usr/ 
sbin/hald
root     31023  0.4  0.1   3232  1048 ?        S    12:53   0:00 hald- 
runner
103      31039  0.0  0.0   2268   884 ?        S    12:53   0:00 hald- 
addon-acpi: listening on acpid socket /var/run/acpid.socket
root     31049  0.0  0.0   3292  1016 ?        S    12:53   0:00 hald- 
addon-storage: polling /dev/hdc (every 2 sec)
root     31082  0.0  0.0   3120   700 pts/2    R+   12:53   0:00 grep  
hal

# ps auxwww|grep dbus
101      30993  0.0  0.0   2620   924 ?        Ss   12:53   0:00 /usr/ 
bin/dbus-daemon --system
root     31078  0.0  0.1   2624  1236 ?        S    12:53   0:00 dbus- 
daemon --session --print-address --nofork
root     31085  0.0  0.0   3120   700 pts/2    R+   12:53   0:00 grep  
dbus

Thanks,
-Chris


On Mar 8, 2008, at 6:17 AM, Robert Millan wrote:

> On Sat, Mar 08, 2008 at 10:42:11AM +0000, Toby Cadoux wrote:
>> I had the same problem but removed /var/run/dbus/system_bus_socket  
>> and
>> reinstalled dbus.
>> Everything went swimmingly after that.
>>
>> On the other hand I have no idea _why_.
>
> Ok but don't tell _me_.  Tell the BTS (CCed).
>
> -- 
> Robert Millan
>
> <GPLv2> I know my rights; I want my phone call!
> <DRM> What use is a phone call… if you are unable to speak?
> (as seen on /.)
>
>
>
> -- 
> To unsubscribe, send mail to 469528-unsubscribe at bugs.debian.org.