Univention Bugzilla – Bug 43656
univention-welcome-screen does not work
Last modified: 2017-04-04 18:28:48 CEST
univention-welcome-screen is not shown: # systemctl start univention-welcome-screen # systemctl status univention-welcome-screen.service [...] Feb 27 17:10:25 master systemd[1]: Starting LSB: Univention Welcome Screen... Feb 27 17:10:25 master univention-welcome-screen[2055]: plymouth bootsplash daemon ist not running ... (warning). Feb 27 17:10:25 master systemd[1]: Started LSB: Univention Welcome Screen.
plymouth: added 080-do-not-ignore-fb-if-drm-is-not-in-use.quilt (backport of upstream changes) added 085-switch-to-welcome-and-snapshot-before-quit.quilt adds a ExecStartPre to the plymouth-quit service to call univention-welcome-screen to switch to the welcome screen and take a snapshot to /tmp/.univention-welcome-screen.png univention-bootsplash (univention-welcome-screen): new systemd service to start univention-welcome-screen to show the welcome screen univention-system-setup: startxwithfirefox start univention-welcome-screen after setup in a mode, where plymouth is restarted, a snapshot is taken and shown
Created attachment 8557 [details] debug logfile Runs very well on KVM, only one slight hickup when displaying the file from /tmp, i guess that is ok. Unfortunately nothing is displayed in a Virtualbox VM. A quick debug produced the attached logfile
I've disabled the welcome-screen installation for the 4.2 RC: r78016: * Don't install univention-welcome-screen until Bug #43656 has been fixed First, the welcome-screen is shown. After 10 seconds, a black screen is shown, if I press ESC the message: A start job is running for Wait for Plymouth Boot Screen to Quit (2min 34s / no limit).
re enabled, i updated the systemd service to ignore the return code of the welcome screen (i think this is what blocked the startup)
It works with the latest changes.
UCS 4.2 has been released: https://docs.software-univention.de/release-notes-4.2-0-en.html https://docs.software-univention.de/release-notes-4.2-0-de.html If this error occurs again, please use "Clone This Bug".