Robert Millan wrote: > Package: hal > Version: 0.5.10-5 > Severity: serious > > postinst fails when upgrading from etch: > > [...] > S'est configurant hal (0.5.10-5) ... > Reloading system message bus config...Failed to open connection to system > message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: > Connection refused > invoke-rc.d: initscript dbus, action "force-reload" failed. > Starting Hardware abstraction layer: haldinvoke-rc.d: initscript hal, action > "start" failed. > dpkg: s'ha produt un error en processar hal (--configure): > el subprocs post-installation script retorn el codi d'eixida d'error 1 > > I didn't stop dbus previous to the upgrade, or do anything special. Maybe it > should just tollerate this error and proceed?
hal.postinst contains: if [ -x /etc/init.d/dbus ]; then invoke-rc.d dbus force-reload || true fi So it should ignore errors, when dbus is not running. /etc/init.d/hal contains: start) if [ ! -d /proc/sys/fs/inotify ]; then log_failure_msg "Can't start $DESC - enable inotify support in your kernel" exit 0 fi if [ ! -e /var/run/dbus/system_bus_socket ]; then log_failure_msg "Can't start $DESC - please ensure dbus is running" exit 0 fi [..] So we also check for a running dbus there. Could you check your hal init script, if you have those checks there? Could you also check, if dbus is *not* running but /var/run/dbus/system_bus_socket is existent (which should never happen though). Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature