That version has died long ago; no more supported
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/579906
Title:
Plymouth does not
Ok, mine was
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/571678 sorry for
the noise.
--
Plymouth does not display bootsplash
https://bugs.launchpad.net/bugs/579906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
I have the same issue, also Kubuntu, also Intel, but GMA 950
--
Plymouth does not display bootsplash
https://bugs.launchpad.net/bugs/579906
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.ub
** Changed in: plymouth (Ubuntu)
Status: New => Confirmed
--
Plymouth does not display bootsplash
https://bugs.launchpad.net/bugs/579906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Unfortunately, the splash does not show up after exiting the initramfs
shell (although /dev/fb0 was present at that time):
http://www.youtube.com/watch?v=E4Oky8d-flQ
On the other hand, when an fsck happens during boot, the bootsplash
becomes visible as soon as the fsck starts:
http://www.youtube.c
After booting with break=modules and finding /dev/fb0 is there, does
continuing the boot with Ctrl-D bring up the splash screen, or not?
The contents of the initramfs all look sensible, so a race condition
still seems the most likely problem here.
--
Plymouth does not display bootsplash
https://
When booting with break=modules, /dev/fb0 is present (29, 0). However, I
just noticed that when booting I noticed a message that may be related
and shows up after grub, but before any plymouth message shows up:
mknod: /dev/fb0: File exists
Probably just cosmetic, but I thought I'd mention it.
--
** Attachment added: "zcat /boot/initrd.img-$(uname -r) | cpio -t"
http://launchpadlibrarian.net/48853918/initrd.txt
--
Plymouth does not display bootsplash
https://bugs.launchpad.net/bugs/579906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Oh, very interesting. I would expect a 1 second delay to be sufficient,
if this is a race condition.
Can you post the output of 'zcat /boot/initrd.img-$(uname -r) | cpio
-t'? Also, please try booting with 'break=modules' and when you get a
shell prompt, check whether /dev/fb0 is present - and if
Added sleep, regenerated the initrd, re-enabled plymouth:debug, updated
grub. Unfortunately, the issue is still unchanged. Even the plymouth-
debug.log file is 100% identical to the one I attached to this bug
(except for the timestamp).
--
Plymouth does not display bootsplash
https://bugs.launchp
The x11.so message is irrelevant; we never want to be using the x11
renderer in the initramfs anyway.
The key section of the log is this:
[./plugin.c]create_backend:creating renderer
backend for device /dev/dri/card0
[./plugin.c]
Sure. I noticed that the log points out a missing
/lib/plymouth/renderers/x11.so, which is indeed not present in the
initrd image although it is present in /lib/plymouth/renderers/ on the
rootfs.
** Attachment added: "/var/log/plymouth-debug.log"
http://launchpadlibrarian.net/48519057/plymouth-
ah - could you also attach /var/log/plymouth-debug.log, please?
--
Plymouth does not display bootsplash
https://bugs.launchpad.net/bugs/579906
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
Please find attached the requested boot.log file.
In the meantime I also figured out a workaround: Adding the following
Kernel boot parameters enables Plymouth to correctly display the
graphical splash:
nomodeset video=uvesafb:mode_option=1024x600-24,mtrr=3,scroll=ywrap
This workaround was *not*
Please boot with plymouth debugging turned on and forward the resulting
/var/log/boot.log.
** Changed in: plymouth (Ubuntu)
Status: New => Incomplete
--
Plymouth does not display bootsplash
https://bugs.launchpad.net/bugs/579906
You received this bug notification because you are a member
Just spotted the "Error: command ['readlink',
'/etc/alternatives/text.plymouth'] failed with exit code 1" error in the
above output. Is having a text theme installed mandatory?
--
Plymouth does not display bootsplash
https://bugs.launchpad.net/bugs/579906
You received this bug notification becaus
** Attachment added: "Broken password entry"
http://launchpadlibrarian.net/48383683/IMAG0027.jpg
--
Plymouth does not display bootsplash
https://bugs.launchpad.net/bugs/579906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
** Attachment added: "Debug messages"
http://launchpadlibrarian.net/48383653/IMAG0025.jpg
--
Plymouth does not display bootsplash
https://bugs.launchpad.net/bugs/579906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/48382695/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/48382696/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/48382697/Dependencies.txt
** A
19 matches
Mail list logo
