I think I have the same bug/issue.
Problem: On boot quite often * it just hangs at the blue kubuntu splash screen
with dots moving.
Just sits there. Has not crashed, because a Ctrl-Alt-Delete does an ordered
shutdown and restart.
No other prompts/etc on screen - just splash screen - cannot swap
OK.
Just did some testing:
Warm-reboots - seems to start OK.
Cold-boot hangs * at splash screen - tried pressing ´m´ and ´S´ - nothing
happens.
Cannot change to other consoles - hitting Ctrl-Alt-Del initiates restart and
suddenly i can access other console again (but not login as no time
Just found this:
´plymouth-log-viewer´ - as any user in terminal
==
fsck from util-linux-ng 2.17.2
udevd[412]: BUS= will be removed in a future udev version, please use
SUBSYSTEM= to match the event device, or SUBSYSTEMS= to match
Elroy,
I think I have the same bug/issue.
This bug has been closed as *invalid*. It is not a productive use of
your time to follow up to this bug report. I recommend you look in one
of the support forums for advice - e.g., ubuntuforums.org or
askubuntu.com.
--
You received this bug
There is a serious error in mountall, I think. The upgrade from hardy to
lucid works fine on the first look. But after editing /etc/fstab my
system hangs without an error message. The only change was a little bit
formatting for a better overview on the mount options. When I found this
thread, I
** Attachment added: /etc/fstab, with boot failure
https://bugs.launchpad.net/ubuntu-release-notes/+bug/510415/+attachment/1873281/+files/fstab.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Indeed. This is not user friendly behaviour. I have had the splash
screen truned off for as long as I can remember, because that is
supposed to give me MORE information if things go wrong. This idiotic
change actually does the opposite. Totally unacceptable.
--
Lucid mountall can cause
Well, guess what, this happened to me, too. After having added my new
phone to fstab (as a user mount), the system just hung in the middle of
the boot process. Fsck found my root, /dev/sda2 to be clean, and
then...nothing. No message about any key shortcuts, no message about
waiting for
I agree with some of the voices raised here. I just edited fstab,
screwing up the device name of an unimportant data partition, and now
I'm left with a non-booting server and no clear indication of what went
wrong (well, until I found this).
I think perhaps other than the root partition, a flag
Florian,
I'm sorry that you had the problems you did recovering your system after
changing a partition UUID, but that doesn't appear to be related to this
bug report. Mountall was fixed well before the lucid release to provide
progress information on the screen about unmountable filesystems; if
i just spent about 1 hour trying to fix my machine because of this SH**
:(
i reinstalled windows and formated the partition - which was listed in
/etc/fstab with the UUID and because of the reformat the UUID changed
the boot process hang - no indication why
i even recovered the whole ubuntu
11 matches
Mail list logo
