That version has died long ago; no more supported
** Changed in: plymouth (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/591825
Title:
plymouth crashes on boot
** Changed in: plymouth (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/591825
Title:
plymouth crashes on boot with kernel NULL pointer dereference
--
ubuntu-b
Happened to me one time today. Here's the relevant part of syslog:
Jan 3 15:58:00 moon init: plymouth main process (290) killed by SEGV signal
Jan 3 15:58:00 moon kernel: [ 69.750059] BUG: unable to handle kernel NULL
pointer dereference at 0130
Jan 3 15:58:00 moon kernel: [ 6
[Expired for plymouth (Ubuntu) because there has been no activity for 60
days.]
** Changed in: plymouth (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/5918
plymouth crashed very early in the boot process, so i presume, apport did
not manage to gather any other information.
I've droppen the vga=791 and splash from the defoptions line in menu.lst,
that completely kills my console (only ssh login possible)
Dropping only the splash from the menu.lst stil
Thank you for taking the time to report this bug and help to improve
Ubuntu.
The report includes no information about the actual crash, so this is
impossible to debug. Did apport not manage to collect a backtrace for
this crash (because plymouth crashed too early, maybe)?
I see you have the rade
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/50023130/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/50023131/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/50023132/Dependencies.txt
** A
