https://bugzilla.suse.com/show_bug.cgi?id=1175779 https://bugzilla.suse.com/show_bug.cgi?id=1175779#c11 Franck Bui <fbui@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #11 from Franck Bui <fbui@suse.com> --- Unfortunately we introduced a bug when we switched to tmpfs for /tmp by default and we forgot to remove some related code in the specfile. The consequence of that was the creation of a dangling symlink (pointing to /usr/share/systemd/tmp.mount which has been removed since the use of tmpfs) for users who switched to tmpfs for /tmp. Please note that the dangling symlink was created during the _second_ update of systemd, which followed a former update that already contained the switch to tmpfs for /tmp by default. For affected users, the problem arose during a reboot after this second update. Either the system failed to boot completely because / was left RO or /tmp wasn't mounted at all. Fortunately, a fix is already available in the Update channel, kudos to Fabian Vogt ! Conclusion ---------- 1. only users that switched to tmpfs by default should be affected 2. make sure /tmp entry in fstab is commented out (as it was recommended in [1]) 3. make sure to update systemd ASAP, so the dangling symlink is automatically fixed and points to /usr/lib/systemd/system/tmp.mount 4. ensure that the symlink is correct after the update and if so feel free to erase it as there's no point to override a unit by itself. We don't do that automatically because it highly depends on 2. to be done. 5. reboot to make sure that /tmp is correctly mounted. [1] https://en.opensuse.org/openSUSE:Tmp_on_tmpfs -- You are receiving this mail because: You are on the CC list for the bug.