If the segfault isn't reproducible with current plymouth, then we should
close this report. For any other crashes, you should probably file a
new bug report as they are unlikely to be related.
Please also open a bug against the grub2 package about update-grub not
picking up the 'quiet splash' opt
Ok, with the new installation, I have the graphic and wonderfull purpul
boot, but I have install a new version of grub, and my previous version
was like alexander.
--
plymouthd crashed with SIGSEGV
https://bugs.launchpad.net/bugs/543344
You received this bug notification because you are a member
I have the version 0.92bubuntu71 because I have all updates.
But with the live system it runs really good, so, in parrallell I will install
lucid on an other partition.
--
plymouthd crashed with SIGSEGV
https://bugs.launchpad.net/bugs/543344
You received this bug notification because you are a m
Mmm, I didn't suggest reinstalling, at all. I asked what version of
initramfs-tools you have installed. If you reinstall the system, we may
lose any information needed in order to debug this.
--
plymouthd crashed with SIGSEGV
https://bugs.launchpad.net/bugs/543344
You received this bug notifica
Ok, I may have make a mistake during the installation, I will reinstall
correctly now, and I will tell you what happen.
I have made "update grub" from karmic too, but I have not install grub the sda6.
Thank you.
--
plymouthd crashed with SIGSEGV
https://bugs.launchpad.net/bugs/543344
You receiv
I can confirm that my grub.cfg doesn't contain the "splash" statement
either. I have never messed with the grub settings. What I am doing
though is using Karmic's bootloader because I'm dual booting. So it's in
fact Karmic's "update-grub" which detects Lucid and writes those lines
to grub.cfg
--
Please make sure you have version 0.92bubuntu71 or later of initramfs-
tools installed. If you didn't, and you upgrade to this version, is the
problem resolved?
Originally, you reported:
> When I boot, I can't see the purple boot, but just text lines.
But your report shows:
> ProcCmdLine: BOOT
Now, plymouth have status 69, and on the screen "mountall: could not
connect to plymouth" is printed.
--
plymouthd crashed with SIGSEGV
https://bugs.launchpad.net/bugs/543344
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
I experience this on a Thinkpad T60 with an ATI Radeon Mobile X1400
--
plymouthd crashed with SIGSEGV
https://bugs.launchpad.net/bugs/543344
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.u
update, safe-upgrade as of 26 March and then this happened a bit later.
Linux version 2.6.32-17-generic-pae (bui...@vernadsky) (gcc version
4.4.3 (Ubuntu 4.4.3-3ubuntu3) ) #26-Ubuntu SMP Sat Mar 20 01:28:23 UTC
2010
VGA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress
200]
Jerry
** Visibility changed to: Public
--
plymouthd crashed with SIGSEGV
https://bugs.launchpad.net/bugs/543344
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/
11 matches
Mail list logo
