auto smbfs mount in /etc/fstab causes hald hang at boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HAL |
Invalid
|
Undecided
|
Unassigned | ||
Nautilus |
Unknown
|
Critical
|
|||
Baltix |
Invalid
|
Undecided
|
Unassigned | ||
hal (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
My main computer, an Athlon XP, has been an up-to-date Dapper system for weeks now with no problems. Two days ago I updated to the latest packages, and it stopped booting.
The boot process brings up the brown graphical screen with the progress bar, and shows various systems being started up. It prints that dbus started successfully, and prints a message about hald starting, and then pauses. After a while, the brown graphical screen goes away and shows the text screen of systems startup. This screen shows hald with a status of "[ok]". The system is hung there.
I have a second computer, with an Athlon64 chip, running a k8 kernel. It hadn't been updated in many weeks. I booted it up, and decided to update it. Once it was up to date I rebooted it. It hung at boot in the exact same way as the other computer!
Since then I have been running "apt-get update; apt-get dist-upgrade" several times a day, hoping there would be an updated package (hald or whatever) that would fix the problem. So far it's still there.
Possible clues:
* I also see a failure of "mousedev" to start up.
* Both of these computers are set up with a Belkin OmniView USB KVM Switch. The keyboard and mouse are connected to the KVM, and the KVM is plugged in to a USB port on each computer.
* Both computers have nVidia drivers, tainting the kernel with non-GPL. Other than nVidia they have only standard Linux stuff.
* I looked in /var/log/syslog for clues, and found none. I did not see any messages from hald in the log before the system restart message.
* Both motherboards have VIA chipsets.
I really want at least one of these computers running again ASAP. I'm tempted to downgrade one of them to older Ubuntu that will work, but so far I'm limping along using Windows, in case someone wants me to run a specific test or something.
Even if I do reinstall Ubuntu on one of the two computers, I will leave the other one up-to-date to reproduce the problem.
Changed in nautilus: | |
status: | Unknown → Unconfirmed |
Changed in nautilus: | |
status: | New → Invalid |
Changed in hal: | |
assignee: | pitti → nobody |
Changed in nautilus: | |
importance: | Unknown → Critical |
status: | Invalid → Unknown |
I can confirm this bug. My workaround was booting into rescue mode and running: manager and a few other things, but at least my system boots now.
apt-get remove hal
That removed ubuntu-desktop gnome-volume-
I've installed all the latest updates for Dapper Drake.