https://bugzilla.novell.com/show_bug.cgi?id=773562 https://bugzilla.novell.com/show_bug.cgi?id=773562#c1 --- Comment #1 from Frederic Crozat 2012-07-30 08:12:27 UTC --- quiet is not supposed to control plymouth startup, but only text output being verbose or not (and kernel output). What is your exact /proc/cmdline ? Plymouth should only show splash if splash or splash=silent . I guess we should add those checks in plymouth-{reboot/kexec/poweroff/halt).service systemd file to prevent splash for appearing. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=773562 https://bugzilla.novell.com/show_bug.cgi?id=773562#c3 --- Comment #3 from Raymond Wooninck 2012-07-30 12:55:25 UTC --- Looking at the /proc/cmdline output, then you have the option there splash=silent. This means that Plymouth will show its splash screen and not the detailed output. Even if systemd service files would check the commandline, then the splash would still be shown. What do you have set for the default plymouth theme ? (execute plymouth-set-default-theme without arguments). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=773562 https://bugzilla.novell.com/show_bug.cgi?id=773562#c5 --- Comment #5 from Raymond Wooninck 2012-07-30 13:22:28 UTC --- Indeed, it looks that way. To me it seems that you do not want the graphical splash, but are more interested to have the boot process as verbose text. Could you try to reset the theme to text mode, with: "plymouth-set-default-theme text" This should give you always the detailed verbose text screen during boot and shutdown. I am not sure if this would resolve the blank tty screen on shutdown. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=773562 https://bugzilla.novell.com/show_bug.cgi?id=773562#c7 --- Comment #7 from Raymond Wooninck 2012-07-31 08:58:37 UTC --- plymouth-set-default-theme is working as expected. If you call it with --help, then you will see that you have to specify the -R option if you want to have the initrd rebuild. So this is not another bug ! (I just forgot to indicate the -R to you, but it is used when installing/removing the openSUSE theme). The blank tty7 screen on reboot is not a bug with plymouth, but comes from the way that plymouth was integrated into openSUSE. With almost all other distro's you see that plymouth defaults to run on the console for the startup and shutdown procedures. openSUSE is one of the few where it was clearly requested by it's users, to have plymouth run on tty7 (as with the previous bootsplash), so that the resulting graphical sessions would start from tty7 and not (as with Fedora, Ubuntu, etc) on the console itself. During shutdown plymouth will use tty7 to show its graphical splash, but actually the whole shutdown process runs on the console. The bug here could be however that during shutdown the output on the console is not captured as during the startup process. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=773562 https://bugzilla.novell.com/show_bug.cgi?id=773562#c9 Raymond Wooninck changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #9 from Raymond Wooninck 2012-11-25 17:57:56 UTC --- Based on the 0.8.8 release of Plymouth, the systemd units were adjusted to be aware of the kernel options. With the kernel option plymouth.enable=0 (disabled) or plymouth.enable=1 (enabled) you can now set whether or not plymouth should be started or not. When plymouth.enable is set to 0, then systemd will not initiate plymouth upon shutdown/reboot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=773562 https://bugzilla.novell.com/show_bug.cgi?id=773562#c11 Jan Engelhardt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Component|Basesystem |Basesystem Resolution|FIXED | AssignedTo|tittiatcoke@gmail.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE 12.2 |openSUSE 12.3 --- Comment #11 from Jan Engelhardt 2013-02-16 12:29:41 CET --- . -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=773562 https://bugzilla.novell.com/show_bug.cgi?id=773562#c13 Jan Engelhardt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|jengelh@inai.de | --- Comment #13 from Jan Engelhardt 2013-02-17 05:55:35 CET --- Heh, of course not :) verbose, to me, implies plymouth.enable=0, if it helps getting to see text. Though I wonder - if one uses a picture background (as in the SUSE versions before plymouth), plymouth.enable=0 would disable that too, would it not? So "verbose" should mean: if there's a verbose.jpg defined for the particular theme, use that, if not, turn it off like plymouth.enable=0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=773562 https://bugzilla.novell.com/show_bug.cgi?id=773562#c14 Raymond Wooninck changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #14 from Raymond Wooninck 2013-02-23 16:27:36 UTC --- Jan, I can't control kernel parameters as that this is done upstream. If you do not want to see the plymouth bootsplash, then you have to use the parameter plymouth.enable=0. This would switch plymouth off during boot and shutdown. If you insist on using the verbose parameter, then I would suggest to report this upstream and see if the upstream developers are willing to implement this. With plymouth there is no verbose.jpg for particular themes. Plymouth starts in a graphical mode and by pressing Esc, you can see the detailed bootsplash. There is no more background picture for the terminal as before with the old bootsplash. I tried to do this and ended up with a corrupted shutdown. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=773562 https://bugzilla.novell.com/show_bug.cgi?id=773562#c16 --- Comment #16 from Raymond Wooninck 2013-02-23 17:09:36 UTC --- I guess you didn't saw my last sentence where I indicated that I tried to get the background picture and that this resulted in a corrupted shutdown with plymouth no longer running. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=773562 https://bugzilla.novell.com/show_bug.cgi?id=773562#c18 --- Comment #18 from Raymond Wooninck 2013-02-24 09:54:06 UTC --- Christian, Yes, I did exactly the same thing, but splash is messing around with the console buffer and this causes that plymouth doesn't even show during shutdown. But I guess that nobody cares and that they want to have this background image on the tty1 and they will file bugreports that the plymouth shutdown splash doesn't work. Maybe the guy didn't care that the shutdown doesn't show plymouth and maybe neither would you, but I hope that you can understand that this would create another flow of bugreports if I would implement this. And for what ? Just to have a textured tty1 ? All other distro's have implemented plymouth and the graphical session on tty1, only openSUSE is doing it on tty7 as that the majority of it's users are used to the fact that the graphical session should be on tty7 and not on tty1. But maybe you can make it work and create an SR to plymouth to implement it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=773562 https://bugzilla.novell.com/show_bug.cgi?id=773562#c20 --- Comment #20 from Jan Engelhardt 2013-02-24 17:42:55 CET ---

All other distro's have implemented plymouth and the graphical session on tty1, only openSUSE is doing it on tty7 as that the majority of it's users are used to the fact that the graphical session should be on tty7 and not on tty1.

What (open)SUSE did was have X on tty7, but console (with or without splash) on tty1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.