http://bugzilla.opensuse.org/show_bug.cgi?id=965492 Bug ID: 965492 Summary: oS 13.1: systemd in patch 2016-137 booting directly into maintenance mode Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Maintenance Assignee: bnc-team-screening@forge.provo.novell.com Reporter: pi.ro@web.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 664678 --> http://bugzilla.opensuse.org/attachment.cgi?id=664678&action=edit 'journalctl -xb' Output in Maintenance Mode. openSuse 13.1 on Thinkpad: /home with own encrypted /dev/sda7 (/tmp and /var bound to /home/tmp and /home/var) After applying recommended update 2016-137 for systemd (208-35.1 to 210-40.1) next reboot directly went into maintenance mode without asking for home-password (or any pause). Manual 'cryptsetup luksOpen /dev/sda7 cr_home' was possible, /home then automatically mounted. As dev-mapper-cr_home.device timed out (?), I set a keyfile for /dev/sda7 and changed crypttab accordingly. System booted still into maintenance mode, this time with /home mounted properly. 'journalctl -xb' output attached. 'systemctl isolate graphical.target' was possible, so I changed systemd & systemd-sysvinit from 210-40.1 back to 208-35-1 in yast: booted without any flaw like before the update. libgudev-1_0-0, libudev1 and udev from patch 2016-137 could stay at 210-40.1 without any harm. May be similar to Bug 960258. -- You are receiving this mail because: You are on the CC list for the bug.