The default theme is "ubuntu-logo"; that's what happens when I try to switch theme
r...@jarvis:~# plymouth-set-default-theme solar r...@jarvis:~# plymouth-set-default-theme --rebuild-initrd /lib/plymouth/themes//.plymouth does not exist r...@jarvis:~# plymouth-set-default-theme --reset r...@jarvis:~# plymouth-set-default-theme --rebuild-initrd /lib/plymouth/themes//.plymouth does not exist That's weird... On Fri, Jan 22, 2010 at 17:44, PeterPall <[email protected]> wrote: > Only to make sure that nothing obvious is left out: > Have you ever tried to change the plymouth theme? > > Background: I own 2 Ubuntu installations that I have upgraded from > karmic to lucid, one minimalistic installation that fits on the 8GB SDD > of my computer - and a second quite complete installation on an external > USB HDD. My system is an Acer Aspire One and uses Intel's 945GME > graphics chipset. On both installs plymouth didn't work no matter what I > was doing. > > The error message was the same as stated above ("unexpectedly > disconnected from boot status daeome") - until I switched plymouth's > theme with plymouth-set-default-theme. > > Since then I have not found a theme that doesn't work for me. But if you > tell me which one is installed by default I will give it a try. > > What I haven't tried, too, is, if plymouth does still work if I remove > the "splash" parameter from the kernal command line. But I think you > would know the result in advance, anyway. > > Another thing I noticed is that currently on my system the fact if > plymouth is working on powerdown, too, depends on the graphics mode my > grub2 uses. 640x400 is bad, 1280x600 works fine. > > -- > [lucid] No plymouth at boot time and mountall error > https://bugs.launchpad.net/bugs/504052 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “plymouth” package in Ubuntu: Fix Released > > Bug description: > Binary package hint: plymouth > > When trying to reproduce a /home encryption issue I have (not being > prompted for the key at boot time), I noticed that I currently don't get > plymouth to start at all ! > > In order to test in a clean environment, I did a VM install using the > mini.iso (amd64 install) with the same partitioning as my laptop and > installed a command line Ubuntu + the plymouth package (to keep the image > small so I can upload it if needed). > > At boot time I get: > ----- > mountall: Could not connect to Plymouth > fsck from util-linux-ng 2.16 > /dev/sda1: clean, 43560/122160 files, 193804/487966 blocks > * Starting init crypto disks... * sda2_crypt (starting).. > > Unlocking the disk /dev/disk/by-uuid/91c20a8a-ea4d-4352-aa89-21470dad5a5d > (sda2_crypt) > * sda2_crypt (starting).. > Skipping /home at user request > init: plymouth-log main process (941) terminated with status 111 > ----- > > I don't get prompted for the key to unlock /dev/sda2 and it even gets > discarded by mountall after that. > > Also, when trying to login, vt1 seems broken as after typing two > characters, the terminal freeze and I have to switch to vt2 to get a working > console. > > I'm not sure if that's a Plymouth issue triggering a mountall one or the > other way around, so I may very well be reporting it against the wrong > package, feel free to reassign. > > As I said, I have the same issue on my laptop as in the VM (no Plymouth, > broken VT and no cryptsetup prompt) and I'm keeping the VM around in case > you would like a copy of it. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/504052/+subscribe > -- [lucid] No plymouth at boot time and mountall error https://bugs.launchpad.net/bugs/504052 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
