Seems documented
r...@jarvis:~# plymouth-set-default-theme --help
* usage: plymouth-set-default-theme* { --list | --reset | *<theme-name> [
--rebuild-initrd ]* | --help }
--help show this help message
--list show available themes
--reset reset to default theme
--rebuild-initrd rebuild initrd (necessary after changing theme)
<theme-name> name of new theme to use (see --list for available
themes)
But it worked:
r...@jarvis:~# plymouth-set-default-theme --rebuild-initrd solar
update-initramfs: Generating /boot/initrd.img-2.6.32-11-generic
No way to make it work for all initrd images?
But plymouth *doesn't* work yet.
On Fri, Jan 22, 2010 at 20:06, Steve Langasek
<steve.langa...@canonical.com>wrote:
> On Fri, Jan 22, 2010 at 05:51:24PM -0000, Durand D'souza wrote:
> > Same error here!
>
> > On Fri, 22 Jan 2010 17:25:07 -0000, Claudio Moretti
> > <flyingsta...@gmail.com> wrote:
>
> > > 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
>
> You need to run this as 'plymouth-set-default-theme --rebuild-initrd
> solar'.
> I don't know if this is a documentation or implementation bug.
>
> --
> [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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
