Your message dated Mon, 6 Sep 2010 12:33:17 +0200
with message-id <aanlktikq-3nodf8n9=m+zubtxrnuqz3uguhbxmk-b...@mail.gmail.com>
and subject line Re: Is the bug you reported still affecting bootchart?
has caused the Debian Bug report #521437,
regarding Reinstalled Hal, now can't boot.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
521437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hal, bootchart
Version: unknown.
Severity: critical
I ran "sudo aptitude reinstall hal", and as per the command, hal
reinstalled. Followed by some weird messages, which made absolutely no sense
to me, and unfortunately I forgot to copy them...
Anyway, the next couple of reboots worked fine, until I tried to run a
bootchart. I added init=/sbin/bootchartd to the appropiate place in menu.lst
in /boot/grub/ and rebooted (a note, bootchart was running fine before the
hal reinstall) - I can't get past booting now, X, gdm, hal and pretty much
every other package fail to initialize in a massive string of errors most of
which say 'rm: cannot remove ....." (I can't ever see the ...... it scrolls
away too quickly). After everything fails I'm still given a console login,
but the entire system is still in read-only mode (probably why all the rm's
failed).
I can't find any of these messages in any of the log files in /var/log/ and
have no idea what I can to try and fix this - nor do I have any idea which
log I should submit to assist with investigating this. I've run a live USB
install which has allowed me to remove the init=/sbin/bootchartd from grub,
but this makes no difference...
I'm running the debian EEEpc distribution, on an EEE 701 with 4gb SSD.
help?
--- End Message ---
--- Begin Message ---
This was probably a problem in splashy, which has been updated several
times since then so there's probably little sense in reassigning.
I'm closing this bug, if you have problems again with this error
message try submitting a bug report against splashy.
Thanks,
Luca
--- End Message ---
