Hi,
I’ve installed 13.2 RC2 from the DVD image as well as from the live Gnome media, and I also installed Gnome live Factory, but I can’t get it to show Plymouth. This is on a fairly standard Acer laptop with Intel graphics, Plymouth normally works perfectly on it. But with 13.2 RC2 and Factory, it just shows a silent black boot screen until GDM loads. Any tips to fix it?
Thanks!
I haven’t really investigated that yet, but it seemed to me that plymouth works just fine. It’s just that the theme is completely black apparently.
So try to install some other theme or maybe the openSUSE theme from 13.1 (plymouth-branding-openSUSE).
The theme files are located in /usr/share/plymouth/themes/.
You have to recreate the initrd afterwards for the change to have effect, or call “plymouth-set-default-theme -R themename”.
Ah, you’re right, the “spinner” theme does work during bootup. Thanks for the tip!
However, it goes to text mode during shutdown. Is there any way to make Plymouth appear during shutdown as well? Thanks again!
… I kinda like watching the text mode scroll up the screen during boot and shutdown. 
On 2014-10-13 07:26, Fraser Bell wrote:
>
> rahim123;2669122 Wrote:
>> Ah, you’re right, the “spinner” theme does work during bootup. Thanks
>> for the tip!
>> However, it goes to text mode during shutdown. Is there any way to make
>> Plymouth appear during shutdown as well? Thanks again!
>
> … I kinda like watching the text mode scroll up the screen during boot
> and shutdown.
Same here. I can’t help with plymouth problems because I remove it at
system install time. I consider the raw text messages beautiful. Others
are bewildered when they see my machines booting and think me crazy 
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Me, too. But I’m stuck with plymouth for 3.2 and factory. That’s because I use encryption, and plymouth allows me to only provide the key once instead of for each encrypted partition.
I used to be able to do this with the “initrd” option on the entry in “/etc/crypttab”. But, with the switch to “dracut”, that does not seem to work.
And yes, I know there’s a workaround by putting passphrase for the second encrypted partition in a file on the first encrypted partition. But I’m not sure I like doing it that way.
So, any way to enable Plymouth during shutdown too? Thanks!
I think that depends on the theme as well.
I do see plymouth during shutdown here with the default openSUSE theme (just a black screen of course). I haven’t installed the latest updates yet though.
I agree upon see the the text scroll instead of a black screen. The esc (gives text)button have helped me more then once to track down problems.
regards
On 2014-10-13 15:26, nrickert wrote:
> And yes, I know there’s a workaround by putting passphrase for the
> second encrypted partition in a file on the first encrypted partition.
> But I’m not sure I like doing it that way.
I do it that way, works perfectly and it is safe
The second partition has two password, the original or manual one, and a
random and horribly difficult one, which is stored in a file in the
first encrypted partition; thus to be able to read that file with the
password you need to activate and mount that first partition, thus the
file is safe, protected by encryption.
Only while the machine is running someone could read that file, provided
he is root already, in which case he already has access to all the data.
I certainly will not use plymouth in order activate two partitions. I
rather prefer to type the password twice or more.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I did have a look at this issue yesterday, and the reason for the black bootsplash is quite simple, actually:
The plymouth scripts references the image files background-xxx.png, but the image files are in fact named blank-background-xxx.png.
To fix it you could either rename the image files (in /usr/share/theme/plymouth/openSUSE/), or change the script accordingly (/usr/share/theme/plymouth/openSUSE/openSUSE.script).
But somehow the fading does not work, the picture is always at full intensity. Maybe they “disabled” it on purpose until this is fixed?
I cannot really imagine that this was done by mistake (in Factory nearly two months ago!) and nobody noticed until now…
I noticed that the plymouth graphic was a dull gray (not black). But I didn’t report a bug. I just said to myself “What were they thinking?”
Personally, I don’t like plymouth, which is why I didn’t bother reporting. Previously (12.3 and 13.1), I uninstalled plymouth. But I’m leaving it there for now, because that way I am only prompted once for a LUKS encryption key. Previously I could manage that with the “initrd” option in “/etc/crypttab”, but that seems to not be honored now with the switch to dracut.
Footnote: firefox wants me to change “honored” to “honoured”. And a test shows that it wants me to use “coloured” rather than “colored”. Is this a forum thingy? Or was firefox for factory installed with UK English dictionaries?
With my sentence I primarily meant the developers/artwork designers and people verifying the openQA tests. They must have noticed by now, as the bootsplash is not some obscure, hidden feature, so I suppose that’s done on purpose (until that fade issue is fixed probably).
But the OP created a bug report as well:
http://bugzilla.opensuse.org/show_bug.cgi?id=900804
Footnote: firefox wants me to change “honored” to “honoured”. And a test shows that it wants me to use “coloured” rather than “colored”. Is this a forum thingy? Or was firefox for factory installed with UK English dictionaries?
There’s a recent bug report that Firefox seems to default to “Malawi English” for spell checking:
http://bugzilla.opensuse.org/show_bug.cgi?id=902278
Maybe you’re affected by this, too?
That does seem to be the problem, though it is more amusing than troubling.
A SUSE developer recently stated (see bug #899783), that this option is not honored in dracut, but there is another option for this in dracut.conf (add_device).
Hendrik
Thanks for the reference. I may experiment with that.
Canadian and UK spelling is with “our” for these words, instead of “or”.
Simply because we are not as lazy as them Yankees, so we will write or type the extra letter in order to spell the word correctly … rotfl!rotfl!
I grew up in Australia, and we knew the correct spelling there, too. But by now I have adapted to using the same spelling as the locals.
Sorry for being a bit of a newbie, but I’m trying to understand how to fix this.
The plymouth scripts references the image files background-xxx.png, but the image files are in fact named blank-background-xxx.png.
To fix it you could either rename the image files (in /usr/share/theme/plymouth/openSUSE/), or change the script accordingly (/usr/share/theme/plymouth/openSUSE/openSUSE.script).
I’m not sure what to change. Where does the “openSUSE.script” come from?
Thanks.
Then better wait until this is fixed in the packages.
13.2 GM is on Thursday, then the final packages will be published.
I’m not sure what to change.
As I wrote already, either rename the image files in /usr/share/plymouth/themes/openSUSE (blank-background-xxx to background-xxx), or open the file openSUSE.script in the same directory in a text editor and change the names of the image files it loads.
Then recreate the initrd, because plymouth is started there already normally.
Where does the “openSUSE.script” come from?
The package plymouth-branding-openSUSE, part of openSUSE’s branding and artwork.