Hello
I a using the final release of lucid and I did not got this error using
the default plymouth, but when I change the default for the plymouth-
theme-solar (I did not try any other) it gaves me the same error making
impossible to start the system stucking it in an eternal loop (the
plymouth
I experienced this _once_ today, but could not reproduce it (tested 3
reboots). I was able to switch to text console (ctrl-alt-f2) and login,
but never got a prompt. CTRL-ALT-DEL didn't work either, sysrq-boot did.
--
Default Plymouth theme is sometimes stuck in the loading animation
I see that there is a bind mount listed in /etc/fstab, which may be
related. Reassigning to mountall, since as I said the symptoms don't
indicate a plymouth problem - but if you haven't seen the bug again
since the initial report, this may already be fixed in mountall.
** Package changed:
I haven't experienced this bug for a while now, but before a mountall
update I did experience this issue several times, with or without
Plymouth.
--
Default Plymouth theme is sometimes stuck in the loading animation
https://bugs.launchpad.net/bugs/542575
You received this bug notification
It sounds like you experienced the problem where mountall would block
waiting for Plymouth, without noticing that (a) plymouth wasn't running
or (b) what it was waiting for actually showed up
This was fixed in 2.10, and you say you've not experienced the bug for a
while which fits
If you have a
Now I remember that changelog entry for mountall again and I recall
thinking back then: lets see if this solves the bug. I've paid
attention and haven't noticed this bug since then. So Fix Released it
probably is.
--
Default Plymouth theme is sometimes stuck in the loading animation
Apart from the mountall crash and the two error messages about
ureadahead I didn't see any other error message.
By the way, I haven't experienced this bug since I've reported it.
** Attachment added: fstab
http://launchpadlibrarian.net/41869173/fstab
--
Default Plymouth theme is sometimes
Sorry, the mountall assertion failure is a bug introduced when adding
support for listening for the enter key.
I don't think that's the root cause of your problem, that only applies
when pressing enter at the screen. Can you post the fstab for this
system?
--
Default Plymouth theme is
And do you really not see any other messages on the screen when this
happens? The boredom_timeout assertion failure happens when waiting for
a filesystem, and mountall is supposed to ask plymouth to print a
message to the screen at this point. Perhaps there's a bug in the text
plugin here that
Today I had this issue a few times after each other for the first time.
When Plymouth was going on endlessly for the Xth time I pressed Enter,
which -- to my surprise -- killed Plymouth and presented me with a
recovery shell, preceded by the following message:
mountall:mountall.c:2726: Not
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/41399483/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/41399485/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41399487/Dependencies.txt
**
Thank you for taking the time to report this issue and help to improve
Ubuntu.
The spinning animation doesn't indicate a plymouth bug; plymouth itself
is running, it just hasn't been instructed to stop. Nor is the
ureadahead failure typically a bug (though it's a bug that the message
is
12 matches
Mail list logo
