I updated the following packages and now it works again:
acpi-support (0.107) to 0.108
grub (0.97-29ubuntu18) to 0.97-29ubuntu19
hal (0.5.11~rc2-1ubuntu1) to 0.5.11~rc2-1ubuntu2
libhal-storage1 (0.5.11~rc2-1ubuntu1) to 0.5.11~rc2-1ubuntu2
libhal1 (0.5.11~rc2-1ubuntu1) to 0.5.11~rc2-1ubuntu2
libx86-1 (0.99-1.2ubuntu2) to 0.99-1.2ubuntu3
xubuntu-docs (8.04.1) to 8.04.2
This is what is in the changelog:
hal (0.5.11~rc2-1ubuntu2) hardy; urgency=low
* debian/rules: build using --with-deprecated-keys, since we don't want to
break packages that were assuming this worked right up through beta.
LP: #204768.
-- Steve Langasek <email address hidden> Fri, 21 Mar 2008 20:24:33 +0000
Looks like this made NetworkManager break.
It would be interesting to look into this bug anyway, to make NetworkManager more robust. I had to kill NetworkManager with -9, as it wouldn't terminate otherwise.
I updated the following packages and now it works again:
acpi-support (0.107) to 0.108 rc2-1ubuntu1) to 0.5.11~rc2-1ubuntu2 rc2-1ubuntu1) to 0.5.11~rc2-1ubuntu2 rc2-1ubuntu1) to 0.5.11~rc2-1ubuntu2
grub (0.97-29ubuntu18) to 0.97-29ubuntu19
hal (0.5.11~
libhal-storage1 (0.5.11~
libhal1 (0.5.11~
libx86-1 (0.99-1.2ubuntu2) to 0.99-1.2ubuntu3
xubuntu-docs (8.04.1) to 8.04.2
This is what is in the changelog:
hal (0.5.11~ rc2-1ubuntu2) hardy; urgency=low
* debian/rules: build using --with- deprecated- keys, since we don't want to
break packages that were assuming this worked right up through beta.
LP: #204768.
-- Steve Langasek <email address hidden> Fri, 21 Mar 2008 20:24:33 +0000
Looks like this made NetworkManager break.
It would be interesting to look into this bug anyway, to make NetworkManager more robust. I had to kill NetworkManager with -9, as it wouldn't terminate otherwise.
Regards,
Lee