[Bug 693913] New: System with systemd installed does not boot without it(normal init)
https://bugzilla.novell.com/show_bug.cgi?id=693913 https://bugzilla.novell.com/show_bug.cgi?id=693913#c0 Summary: System with systemd installed does not boot without it(normal init) Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: cobexer@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Booting current factory fails for me on two different systems. a) when booting with normal init and systemd is installed (did not try without since i do not know if it will boot at all without systemd) basically nothing is able to start because some connect on a socket with systemd in its name is not possible. the boot process halts in runlevel 1? and asks for the root password, entering "reboot" there does not even succeed then... b) booting with systemd (adding init=/bin/systemd in grub interactive) allows me to boot both systems, however both still do not boot correctly. one system does not start at least dbus. login -> rcdbus start starts dbus correctly(rcdbus restart does NOT!) that system seems to work properly otherwise. (the system starts in about 12 seconds which is ok and with the exception of dbus i do not seem to miss anything!) the other however has a more complicated setup: encrypted /home. systemd asks for the password and successfully unlocks the encrypted volume. however it does not mount /home after that. extremely bad about it is that not a single vt starts a login terminal... so on that machine i have to wait for the auto login to fail, fallback to using / as home? (WTF), wait for the second fail, login as root, enter mount /home in a terminal, logout, and login as the correct user... very annoying. Reproducible: Always Steps to Reproduce: 1. current factory 2. instyll systemd, use normal init as default 3. reboot -> complete failure of all? services 4. reboot with init=/bin/systemd, some failed services but at least boots package versions before the gcc switch, some packages were newer already, but not systemd and the kernel or init -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=693913
https://bugzilla.novell.com/show_bug.cgi?id=693913#c1
--- Comment #1 from Christoph Obexer
https://bugzilla.novell.com/show_bug.cgi?id=693913
https://bugzilla.novell.com/show_bug.cgi?id=693913#c2
--- Comment #2 from Christoph Obexer
https://bugzilla.novell.com/show_bug.cgi?id=693913
https://bugzilla.novell.com/show_bug.cgi?id=693913#c
zj jia
https://bugzilla.novell.com/show_bug.cgi?id=693913
https://bugzilla.novell.com/show_bug.cgi?id=693913#c3
--- Comment #3 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=693913
https://bugzilla.novell.com/show_bug.cgi?id=693913#c4
--- Comment #4 from Christoph Obexer
https://bugzilla.novell.com/show_bug.cgi?id=693913
https://bugzilla.novell.com/show_bug.cgi?id=693913#c5
Kay Sievers
https://bugzilla.novell.com/show_bug.cgi?id=693913
https://bugzilla.novell.com/show_bug.cgi?id=693913#c6
--- Comment #6 from Christoph Obexer
https://bugzilla.novell.com/show_bug.cgi?id=693913
https://bugzilla.novell.com/show_bug.cgi?id=693913#c7
Frederic Crozat
participants (1)
-
bugzilla_noreply@novell.com