Bug 771299

Created attachment 498485 [details]
Observed view

Created attachment 498486 [details]
Expected. Like it was before in 12.1 and 12.2-beta2 / factory-0455

This is an artifact of bug #771300. plymouth seems to be kept running until an X server starts - which never happens in text mode.

*** This bug has been marked as a duplicate of bug 771300 ***

As of today's 12.3 Factory Milestone 2, almost everything is broken. plymouth starts but dies or something, leaving the terminal in a horrible state.

Created attachment 520039 [details]
stuck on tty7

Created attachment 520040 [details]
a bunch of services completely screwed up

Created attachment 520041 [details]
systemd logging at its best, telling me nothing

Adding systemd/plymouth maintainers.

Maybe you can tell us a little more about what media you have been using on what system, graphics driver, etc ? 

I don't know what you are trying to do here, but there seems to be something wrong with the SSH stuff. At least that is the only thing that I can read out of the screenshots. 

The fact that plymouth is being shown as fail, is correct as that the plymouth systemd service fails as that plymouth is already running at that moment. 

Did you try the journalctl -b command to see the full logfile ? Just grepping on some works, might give you the wrong impression and/or the wrong information. 

It seems that for SSH you are missing a number of keys, which might be due to a failed installation.

Created attachment 520044 [details]
journalctl -b | grep -i plym

I simply did a fresh install using factory of the day into a VirtualBox machine. Graphics driver is irrelevant, as I am the normal 80x25 VGA (non-FB non-KMS) text mode.


As for sshd(.service), I suspect that ExecStart is started while ExecStartPre has not exited yet.

Jan, 

You are now contradicting yourself. Either you used Milestone 2 to install into a virtualbox or you used factory of the day (which could be completely different). 

In your situation it is indeed that the graphics driver is irrelevant, but a non-KMS text mode also means that Plymouth will not display it's graphical screen. It will most likely just display a fallback test-based screen that shows a running statusbar at the bottom of the screen (three green colors filling the bottom line of the screen from left to right). 

Based on this I somehow lost in what you actually want to report as a bug. Whether you want to report a bug for plymouth (which seems not to be stuck as that the machine starts) or that a bunch of services failed to start or just for the sshd service ?

It's really Factory, though /etc/os-release says Milestone 2.
Yes, plymouth shows, as desired, the 3-color bar - except that it does not complete but dies early on. Because plymouth overrides the default terminal colors while it is active and resets them when orderly stopped, there must be some kind of premature exit bug here.
http://inai.de/files/ply.mkv

Ok. Clear :-) The /etc/os-release file is only changed with every milestone. 

This is what I saw from your little movie:

1) You are booting in non-graphics modes (init 3). This will cause systemd to stop the plymouth bootsplash as that there is no display manager that will do this. With init 3 systemd will not start the graphical.target and therefore the exit-plymouth service will be started and stops plymouth. This is however the normal procedure. 

2) I didn't see the bar moving, but what makes you say that there must be some kind of premature exit bug there ? The fact that the bars do not reach the right side of the screen does not indicate that plymouth exists prematurely. If I look at the movie, then plymouth exists and directly the login prompt is shown. Which for me indicates that systemd stopped plymouth at the desired point. 

Based on this, I am guessing now that the actual bug you want to report is that the console does not have the default terminal colors ? Or better said, it does not have the colors that you are expecting to see. 

Did you ever tried to boot the virtual machine without plymouth active ? And then to see if the terminal colors are different ? You can put 'rd.plymouth=0' in the kernel boot option (in grub)

With rd.plymouth=0, boot proceeds as expected.
http://inai.de/files/ply2.mkv

[ The reason I am not using recordmydesktop is because it produces Ogg files that ffmpeg-mplayer considers broken :( ]

Hi Jan,

Now we are getting somewhere :-)   The rd.plymouth=0 parameters causes that plymouth is not started by the initrd. As that plymouth is not running, systemd will start it and that seems to be going fine. 

So something inside the initrd is causing this effect and I am wondering why the same command issued in the initrd is not correctly falling back on text-mode, while if it is being issued by systemd it does correctly. 

Can you paste the boot options from grub ?

Another thing you could try is to issue the following command : 

(as root)  plymouth-set-default-theme -R text 

This should set the default theme to the text theme and rebuild the initrd. After this a reboot should show the same result as in comment #14

Options:

linux /boot/vmlinuz-3.6.3-1-desktop root=UUID=blabla splash=silent quiet showopts 3 rd.plymouth=0


I was already getting text splash before, so set-default-theme -R text has had no changing effect. After having recreated the initrd and not specifying rd.plymouth=0 at boot, the splash is still stuck.

So far, only rd.plymouth=0 works.

With regards to changing the splash, I wanted to make sure that the text splash would be the default one. Instead of a graphics one. 

What is the output of 'rpm -qa | grep plymouth' ?

plymouth-0.8.8_git201211022126-2.1.x86_64
plymouth-plugin-label-0.8.8_git201211022126-2.1.x86_64
plymouth-plugin-script-0.8.8_git201211022126-2.1.x86_64
plymouth-scripts-0.8.8_git201211022126-2.1.x86_64
plymouth-branding-openSUSE-12.3-1.4.noarch

Ok, The plymouth-branding-openSUSE is the one that would cause the graphical theme to be default, so issuing the command plymouth-set-default-theme -R text should have changed that to the text based theme. 

What software are you using for the virtual machine ?

>so issuing the command plymouth-set-default-theme -R text
>should have changed that to the text based theme.

plymouth automatically falls back to text if there is no active framebuffer/KMS — that part already behaves as desired and is not for debate.

>What software are you using for the virtual machine ?

XFCE default install, and manually doing a text boot with the "3" alias as shown above.

It is still the same in beta1--see http://lists.opensuse.org/opensuse-factory/2013-01/msg00621.html

Looks like a serious issue to me.

Karl,

Can you be a little bit more specific about what you see ? The email doesn't say anything specific.

Can both of you indicate if this was working fine with the 12.2 ?

Can both of you indicate if this was working fine with the 12.2 ?

(In reply to comment #23)

> Can you be a little bit more specific about what you see ? The email doesn't
> say anything specific.

YaST (textmode, ncurses) comes up with a green skin (I'll attach the screen shot).  It's a virtualbox installation.  I think I did not test this with 12.2.

Created attachment 522635 [details]
green yast

Karl,

Which bootsplash do you see ? It is the text based one (with the three colored bars at the bottom of the screen (like Jan) ? Or do you have a full graphical bootsplash ?

First I see the graphical bootsplash.  There I enter textmode=1 as a boot parameter, and then I see the three colored bars at the bottom.  After booting for the second part of the installation, yast is green.

If I install without textmode=1, the first part of the installation is fully graphical, but the second part also falls back to text mode (with the three colored bars at the bottom) and a green yast.  I complains about ~ "there are either packages missing or a problem with the X server".

I hope this somehow helps.

Hi Karl,

Ok. At least I know now that you are also having plymouth in text mode. The complains about problem with the X-server might be due to a missing KMS initialization in the virtualbox. 

Would you be able to try something with an different plymouth package ? As that both issues are with the text mode of the splash, I removed one patch and rebuild the plymouth package. Would be great if you could test this one to see if this helps or that it still has the green yast.

The new package is available in http://download.opensuse.org/repositories/home:/tittiatcoke:/testing/openSUSE_Factory/

(for both i586 and x86_64).

Thanks 

Regards

Raymond

Looks fixed for me with build0370/factory du jour fresh install with "Minimal X server" pattern.

 plymouth-0.8.8_git201211022126-4.2.1
 plymouth-branding-openSUSE-12.3-6.5.1
 plymouth-plugin-label-0.8.8_git201211022126-4.2.1
 plymouth-plugin-script-0.8.8_git201211022126-4.2.1
 plymouth-scripts-0.8.8_git201211022126-4.2.1
 systemd-195-13.6.1

Closing bug due to no response

For the original reporter, it was fixed.