Public bug reported:
Binary package hint: hal
After hard reboot, the system reboots and comes to the
text-mode screen on tty1. It never reaches the GUI. And
this is not a temporary problem -- it persists through all
subsequent reboots of the system.
If I log in at the text-mode prompt, become root, and then
do the following:
service hal start
service gdm start
then the GUI screen comes back up, and the system is
healthy. If I reboot the system again, any number of times,
I always face the same need to start hal manually, followed
by gdm.
The only non-standard things I can think of, in my Ubuntu
installation, are (i) my /var/log is on a separate file system,
not on the root file system, and (ii) my home dir too is on
that separate file system, not on root.
Other than these, I do not know of anything else which is
non-standard in my case, and I do not know whether these
are relevant for this problem or not.
This is repeatable. It has happened to myself and a
colleague, both using Thinkpad X-series laptops and the
exact same Ubuntu version, installed from the same copy
of live CD. Both of us have the same separate file system
for homedir, logs, etc, with softlinks from the root-fs.
Both of us had laptop hangs on different occasions, and
had to do a hard reboot. We got this problem after that,
and then in my laptop's case, it went away only after I
re-formatted the HDD and re-installed Ubuntu again from
the CD.
ProblemType: Bug
Architecture: i386
Date: Wed Feb 10 15:38:18 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: vmnet vmci vmmon
Package: hal 0.5.13-1ubuntu8
ProcEnviron:
PATH=(custom, user)
LANG=en_IN
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: hal
Uname: Linux 2.6.31-14-generic i686
** Affects: hal (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386
--
After hard reboot, hal doesn't restart on reboot, ever
https://bugs.launchpad.net/bugs/519768
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
