Some more info - I noticed that hald dies after some minutes; tried to start hald manually by running
# /etc/dbus-1/event.d/20hal start the process hangs at Starting Hardware abstraction layer: hald (no dot after this text) output of ps aux | grep hald first: root 5818 0.0 0.0 3216 852 ? Ss 22:42 0:00 /usr/sbin/hald hal 5820 24.5 0.3 5320 3856 ? Ss 22:42 0:00 /usr/sbin/hald root 5822 0.0 0.0 2732 952 ? S 22:42 0:00 hald-runner root 5829 0.0 0.0 1900 644 ? S 22:42 0:00 /usr/lib/hal/hald-addon-acpi root 5846 0.0 0.0 2792 800 ? D 22:42 0:00 /usr/lib/hal/hald-probe-storage then, until it dies: root 5818 0.0 0.0 3216 852 ? Ss 22:42 0:00 /usr/sbin/hald hal 5820 0.6 0.3 5320 3860 ? Ss 22:42 0:00 /usr/sbin/hald root 5822 0.0 0.0 2732 952 ? S 22:42 0:00 hald-runner root 5829 0.0 0.0 1900 644 ? S 22:42 0:00 /usr/lib/hal/hald-addon-acpi CPU usage stays low: is hald waiting for something? After some minutes ps aux | grep hald retrieves no processes with such name: hald died. I also tried to start hald with # /usr/sbin/hald --daemon=no --verbose=yes This way hald doesn't die anymore: I could also check its messages when inserting/connecting/removing media to the PC; no actions are triggered for any media change: hald is obviously not functional as I wrote in the previous message (see bug #350762). Thanks Mau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
