[Bug 943312] New: new systemd do not work properly in systemd-vconsole-setup.service
http://bugzilla.suse.com/show_bug.cgi?id=943312 Bug ID: 943312 Summary: new systemd do not work properly in systemd-vconsole-setup.service Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: mlin@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- new systemd[1] now is stuck in openSUSE Staging[2], packages looks all build succeeded, however it can not pass openQA, due to gnome[3], kde[4] and cryptlvm[5] test were failed. It seems systemd-vconsole-setup.service is totally broken, according to the logs I can see the error below, a) [ 666.199424] reboot: Restarting system [ 2.752818] systemd[1]: [/usr/lib/systemd/system/systemd-ask-password-plymouth.service:12] Executable path is not absolute, ignoring: --watch --plymouth [ 2.756170] systemd[1]: systemd-ask-password-plymouth.service: Service lacks both ExecStart= and ExecStop= setting. Refusing. [ 2.813551] systemd[1]: Failed to start Setup Virtual Console. b) Aug 25 07:07:44 linux-urr2 systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE Aug 25 07:07:44 linux-urr2 systemd[1]: Failed to start Setup Virtual Console. Aug 25 07:07:44 linux-urr2 systemd[1]: systemd-vconsole-setup.service: Unit entered failed state. you can found the complete log in logs.tar.bz2 on openQA.. [1] https://build.opensuse.org/request/show/323880 [2] https://build.opensuse.org/project/show/openSUSE:Factory:Staging:F [3] https://openqa.opensuse.org/tests/79948 [4] https://openqa.opensuse.org/tests/79946 [5] https://openqa.opensuse.org/tests/79620 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=943312
Max Lin
http://bugzilla.suse.com/show_bug.cgi?id=943312
Max Lin
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c1
--- Comment #1 from Stephan Kulow
http://bugzilla.suse.com/show_bug.cgi?id=943312
Max Lin
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c2
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c3
Ismail Donmez
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c5
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c6
Max Lin
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c7
--- Comment #7 from Max Lin
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c10
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c11
Thomas Blume
(In reply to Max Lin from comment #9)
The onyl thing I see is
Sep 09 02:07:51 linux-kmyi systemd-vconsole-setup[368]: /usr/bin/setfont failed with error code 1. Sep 09 02:07:51 linux-kmyi systemd-vconsole-setup[367]: /usr/bin/setfont failed with error code 1.
Sep 09 02:09:20 linux-kmyi systemd-vconsole-setup[1698]: mapscrn: cannot open map file _trivial_ Sep 09 02:09:20 linux-kmyi systemd-vconsole-setup[1698]: /usr/bin/setfont failed with error code 1.
clearly this results in an failure of systemd-vconsole-setup. The question rises on *what* does /usr/bin/setfont stumble across?
Make sure that kbd gets installed as well is available in the the initrf. Also please disable plymouth and retry.
This should have been fixed by a dracut patch. See bug 926742 comment#8. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c12
--- Comment #12 from Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c13
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c14
--- Comment #14 from Thomas Blume
(In reply to Dr. Werner Fink from comment #12)
Ahh .. this fix is for SLES-12. Thomas?
I'm sorry, seems I somehow failed to submit it. This is done now: https://build.suse.de/request/show/67408 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c15
Max Lin
(In reply to Dr. Werner Fink from comment #13)
(In reply to Dr. Werner Fink from comment #12)
Ahh .. this fix is for SLES-12. Thomas?
I'm sorry, seems I somehow failed to submit it. This is done now:
will also submit the same change for openSUSE? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c17
Thomas Blume
will also submit the same change for openSUSE?
Patches submitted to openSUSE 13.2 and OpenSUSE Development repo. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c22
Fabian Vogt
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c24
--- Comment #24 from Thomas Blume
Proper fix is in Base:System, both plymouth and dracut fixes are being submitted to factory right now. There's also bug 904214 in systemd-vconsole-setup itself, which is closely related to this issue.
Fabian, it seems openSUSE 13.2 is also affected (see bug 744108). Can you please also submit to openSUSE:13.2:Update? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=943312
http://bugzilla.suse.com/show_bug.cgi?id=943312#c25
--- Comment #25 from Fabian Vogt
participants (1)
-
bugzilla_noreply@novell.com