https://bugzilla.novell.com/show_bug.cgi?id=681099 https://bugzilla.novell.com/show_bug.cgi?id=681099#c0 Summary: systemd crashes if home or probably another partition is encrypted Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain@novell.com ReportedBy: timshel@rocketmail.com QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0 I have encrypted my home partition with luks and while the system seems to boot fine at first the screen switches to tty0 after boot. You can switch back to X but it is impossible to shut down or restart the system afterwards. This didn't happen in Factory two month ago or so. Some patch/change seems to have introduced this problem because before that systemd worked fine for me with the encrypted home partition. Since then I have disabled it on my machine with encryption. On the one without it it works fine that's why I thought it was a local issue but I have reproduced it in Virtualbox with a fresh installation. dmesg output: [ 55.945861] systemd[1]: Caught <SEGV>, dumped core as pid 3823. [ 55.945980] systemd[1]: Freezing execution. If you tell me were to fine this dump I can post it. The debug symbols are already installed but nevertheless it should be easy to reproduce. Reproducible: Always Steps to Reproduce: 1. add a encrypted luks partition to crypttab (maybe it must be home) 2. add it to fstab so it gets mounted during boot 3. reboot Actual Results: You see the console after boot instead of X and systemd has crashed so you are unable to shut down the system. Expected Results: You should have no problems. -- 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.