Hi Marcus,
Marcus Lundblad wrote:
> Actually, after a reboot it worked to run "dpkg --configure -a"
>
> But I suppose it would be good if it hadn't hanged there anyway. Maybe
> it should have timed-out and print some error message, so that the
> updgrade would still have been carried out.
Unfortunately the stuff that happens after the messages that you got is
basically everything -- there is no more output, and it runs a hell of a
lot of scripts. It may even be a customized script. So we need to dig a
bit to find out what happened here.
Some questions that I would like you to answer, if possible:
1. If you downgrade to 0.109-3 and then upgrade to 0.109-5 again, do you
get the same problem? (If not, then it's not reproducible and I can't do
a thing about this.)
2. If it's reproducible: do you have customizations in the /etc/acpi
directory? If you purge and reinstall, does the problem still occur?
(Back up your customizations!)
3. If it's reproducible: could you edit /etc/init.d/acpi-support as follows:
start)
log_begin_msg "Checking battery state..."
if [ x"`echo /proc/acpi/ac_adapter/*`" != x"/proc/acpi/ac_adapter/*"
]; then
echo CALLING power.sh
/etc/acpi/power.sh
echo RETURNED FROM power.sh
fi
# Source everything in /etc/acpi/start.d/
for SCRIPT in /etc/acpi/start.d/*.sh; do
if [ -f "$SCRIPT" ] ; then
echo CALLING $SCRIPT"
. $SCRIPT
echo RETURNED FROM $SCRIPT"
fi
done
log_end_msg 0
;;
and then do the upgrade again (not overwriting changes to this file)?
I'd like to see where it hangs.
Thanks in advance for helping to find out what's going on here!
Cheers,
Bart
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
