Mailinglist Archive: opensuse-bugs (3547 mails)

< Previous Next >
[Bug 720486] New: init=/sbin/init on cmdline results in kbd service startup failure
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 26 Sep 2011 23:47:32 +0000
  • Message-id: <bug-720486-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=720486

https://bugzilla.novell.com/show_bug.cgi?id=720486#c0


Summary: init=/sbin/init on cmdline results in kbd service
startup failure
Classification: openSUSE
Product: openSUSE 12.1
Version: Factory
Platform: PC
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: mrmazda@xxxxxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---


Created an attachment (id=453116)
--> (http://bugzilla.novell.com/attachment.cgi?id=453116)
/var/log/boot.msg

To reproduce:
1-install M2 or prior with systemd not installed
2-zypper al systemd
3-do zypper dup on daily or weekly basis until approximately M5 is on mirrors
4-zypper rl systemd
5-include init=/sbin/init on cmdlines of Grub stanza(s)
6-upgrade with zypper dup
7-boot

Actual results:
1-Loading console font...failed
2-Loading compose table...failed
3-Failed services in runlevel 3: kbd

Expected results:
1-no failed services reports
2-keyboard configured as specified in /etc/sysconfig/keyboard

I had all my several systems setup to exclude systemd until about a week ago.
Since, I've removed systemd locks and set init=/sbin/init on two of them, one a
week ago, another today, and this has happened to both.

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >