Univention Bugzilla – Bug 44061
univention-welcome-screen does not work on virtualbox and vmware
Last modified: 2020-06-02 16:21:47 CEST
Plymouth and subsequently the welcome screen do not work on virtualbox. The same logfile is produced as on the original bug, when plymouthd is started with --debug --no-daemon
+++ This bug was initially created as a clone of Bug #43656 +++
Created attachment 8732 [details]
system without welcome screen after system-setup
On vmware and virtualbox the welcome screen is not displayed after system setup, see screenshot
Created attachment 8767 [details]
It worked in VMware when i tested it with an interim version, but the UCS 4.2 release version does not show a welcome screen in any VMware version. The welcome screen is shown briefly, but then switches to a blank screen. I found, that our script renders a blank screen as the image in /tmp/.univention-welcome-screen.png, which is then displayed. May be pointless, but attached is the image found in /tmp/.univention-welcome-screen.png
Doesn't work either on Hyper-V (Windows Server 2012 R2). Bootsplash is not shown. Welcome screen is not shown, but instead of a blank screen, I see the login console.
UCS users are confused by the warning messages: https://help.univention.com/t/boot-und-shutdown-error/5584
Created attachment 8945 [details]
0.9.2~23: seat: be a little more forgiving in the case there's no open terminal
# gdb --args plymouthd --attach-to-session --no-daemon --tty=/dev/tty8
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff79b71d0 in ply_terminal_is_open () from /lib/x86_64-linux-gnu/libply-splash-core.so.2
(gdb) bt: /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed aus base/grub-efi-amd64-signed/gcdx64.efi.signed
#0 0x00007ffff79b71d0 in ply_terminal_is_open () from /lib/x86_64-linux-gnu/libply-splash-core.so.2
#1 0x00007ffff79bab8f in ply_seat_open () from /lib/x86_64-linux-gnu/libply-splash-core.so.2
#2 0x00007ffff79b1d36 in ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.2
#3 0x00007ffff79b21e4 in ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.2
#4 0x00007ffff79b2b1f in ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.2
#5 0x00007ffff79b2e44 in ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.2
#6 0x0000000000404d7b in main ()
Maybe <https://bugs.freedesktop.org/show_bug.cgi?id=80553> AKA <http://cgit.freedesktop.org/plymouth/commit/?id=84eb4381db85877a9a56b35994e6c10d43e46ebe>?
Created attachment 8946 [details]
welcome screen with patch from comment 5
@Comment5: Great, plymouth does not crash anymore. We at least have a bootsplash and welcome screen. However, there still seem to be some redraw issues, see screenshot.
* The crash was fixed with the patch from comment 5.
* The graphic errors were fixed by making sure /dev/fb0 is considered an active console.
* The blank welcome screen (with vmware and at least intel hardware) was fixed by deactivating the drm renderer. It's not really possible to grab an image from plymouth if the drm renderer is used. It would be possible to just let plymouth running but it uses a noticeable amount of system resources. I did a quick research if disabling the drm renderer might become a problem, but it doesn't seem so. See for example: https://www.phoronix.com/scan.php?page=news_item&px=DRM-Text-Mode-Proposal
* I removed the dependency on fbgrab and fbi by using "plymouth quit --retain-splash".
* The switch over to the welcome screen is now flicker free.
* Improved systemd integration.
I noticed that the console screen saver now seems to be ignored. Is that behaviour ok? See also Bug 40750. (Can be reproduced by adding consoleblank=10 to the kernel options)
r80962: fix welcome screen start in appliance mode
As discussed, with the current version there are black tiles leaking and showing up in system, setup; reopening
(In reply to Erik Damrose from comment #10)
> As discussed, with the current version there are black tiles leaking and
> showing up in system, setup; reopening
This happened due to a typo I made in bug 44952...
OK: bootsplash and welcome-screen
OK: Transition after system-setup
OK: KVM, VMWare, Virtualbox, hardware(xen5)
OK: plymouth, univention-bootsplash, univention-system-setup