Comment 5 for bug 211343

Hi Martin,

I decided to run your instructions before updating, after updating but not
restarting and after restarting the computer. There was no change to the
output and I did not lose connectivity; all appears fine.

this is the output I got every time:
lrwxrwxrwx 1 root root 13 2008-04-17 18:28 /etc/rc1.d/K16hal ->
../init.d/hal
lrwxrwxrwx 1 root root 13 2008-04-17 18:28 /etc/rc2.d/S24hal ->
../init.d/hal
lrwxrwxrwx 1 root root 13 2008-04-17 18:28 /etc/rc3.d/S24hal ->
../init.d/hal
lrwxrwxrwx 1 root root 13 2008-04-17 18:28 /etc/rc4.d/S24hal ->
../init.d/hal
lrwxrwxrwx 1 root root 13 2008-04-17 18:28 /etc/rc5.d/S24hal ->
../init.d/hal

All I can think of is doing the update alongside others triggers the problem
so I am going to try that. Ill send you this email for now and will let you
know later what happens. It may take a while as I will reinstall all and may
need to change to my regular HD if I get the problem again.

Cheers

Jose

Martin Pitt writes:

> Jose, can you please give the output of
>
> ls -l /etc/rc*.d/*hal
>
> ?
>
> --
> gutsy->hardy upgrade has wrong init script priority
> https://bugs.launchpad.net/bugs/211343
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Source Package "hal" in Ubuntu: Fix Released
>
> Bug description:
> Binary package hint: hal
>
> /etc-upgrade.tar/etc/rc2.d/S12hal
> /etc-fresh.tar/etc/rc2.d/S24hal