|
Bugzilla – Full Text Bug Listing |
| Summary: | plymouth: splash is started nevertheless on reboot | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.3 | Reporter: | Jan Engelhardt <jengelh> |
| Component: | Basesystem | Assignee: | Forgotten User sM9JzehKpy <forgotten_sM9JzehKpy> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | fcrozat, forgotten_sM9JzehKpy, suse-beta |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | compl"i"mentary screenshot | ||
|
Description
Jan Engelhardt
2012-07-28 17:32:42 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.
BOOT_IMAGE=/boot/vmlinuz-3.4.4-1.1-desktop root=UUID=59f0af2f-019c-4a0c-8504-89bd7e0d441a splash=silent showopts vga=0 Whether it's supposed to display messages or splash does not matter; it should just be consistent, and it is not currently when boot is verbose and shutdown isn't :) N.B.: as an added bug, the text splash shown on shutdown is showing an empty tty, rather than the text progress bar. 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). >splash=silent. This means that Plymouth will show its splash screen and not the
>detailed output.
Except it does not do that on boot, where "quiet" seems to control this instead.
The theme is openSUSE.
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. I do not want anything specifically, I am just testing around. With `plymouth-set-default-theme text`, nothing changes (one still gets the graphical splash). That seems logical, given the initrd was not updated—and that is at the same time another bug. Setting the theme however does not change the reboot situation. Whether you use `set-default-theme` or vga=0 to make plymouth use the text-progress-bar splash, a blank tty7 is shown on reboot when "text" is active. 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. It seems that I made a wrong assumption in my previous comment. I have been looking into the text splashscreen and this appears to be nothing else than the fallback whenever a graphical driver is failing. It still hides the verbose boot-/shutdown text. On startup a tri-color progress bar is shown at the bottom of the screen and indeed on shutdown nothing is shown. Checking the theme itself, it seem to be hardcoded into the plymouth binaries. I am checking with the developers if this is "as designed" or a bug. Please beware however that also the openSUSE theming of plymouth never showed a progress bar on shutdown (as that this could lead to a false indication of the progress) and the latest theme has the progress bar also removed from the startup screen. I will let you know what my findings are with regards to the text splash 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. Created attachment 524980 [details]
compl"i"mentary screenshot
The problem is still present in build0370. In particular, splash is now also briefly shown on boot.
plymouth-*-0.8.8_git201211022126-4.2.1
. Jan, what are you kernel command line parameters ? Did you set the plymouth.enable=0 option ? 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. 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. If plymouth can inspect the kernel command line to look for "plymouth.enable=0", then it surely can also look at the command line for "verbose", and if found, deactivate itself, does it not? >There is no more background picture for the terminal as before with the old bootsplash. Was there any progress w.r.t. restoring it? http://lists.opensuse.org/opensuse-factory/2012-11/msg00873.html 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. On 2013-02-07 Malte Gell wrote about the background picture in the opensuse-de mailinglist - http://lists.opensuse.org/opensuse-de/2013-02/msg00151.html The translated text is: ------------------------------------------------------------------------------- I solved it this way: from the bootsplash package (that I can't install because it conflicts with plymouth) I extracted the binary "splash" and copied it to /usr/bin. This way, I can setup a background image in the console. Instead of extending plymouth to make this [the background image] possible, you could just integrate the splash command from the bootsplash package into the plymouth package. That would be the easiest solution. ------------------------------------------------------------------------------- He didn't complain about any problems afterwords (BTW: he's using 12.2), so I assume it works. However, I didn't test it myself. 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. (In reply to comment #18) > 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. Yes, I fully understand it. > But maybe you can make it work and create an SR to plymouth to implement it. Personally, I don't care too much about having a background image on tty1 - I prefer xterms ;-) I just wanted to mention the ML post in case it you didn't test that way. But then, it would have been a too easy solution, which means it had to be buggy ;-) >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.
|