[Bug 939237] New: Update of sddm can cause severe damage to system
http://bugzilla.novell.com/show_bug.cgi?id=939237 Bug ID: 939237 Summary: Update of sddm can cause severe damage to system Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: w.pelser@web.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After a software update including sddm I hibernated the system as usual. After resuming I tried to reboot the system later on , but it fails with: "can't find sysroot". For normal users system is broken and hardly to repair. After another software update including sddm I immediately rebooted the system and found no problems. Please confirm my observation. There must be a warning, that a sddm update requires a reboot of the system. Or a changing in sddm is needed, which makes this impossible. (Repairing of the broken system is possible, but you need a openSUSE-13.2-NET-x86_64.iso on an USB-stick or a CD by hand. I had to do so for several times, until I found the cause.) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=939237
http://bugzilla.novell.com/show_bug.cgi?id=939237#c1
--- Comment #1 from Walther Pelser
http://bugzilla.novell.com/show_bug.cgi?id=939237
http://bugzilla.novell.com/show_bug.cgi?id=939237#c3
--- Comment #3 from Walther Pelser
This bug is completely chaotic. Even with sddm update it can't break your / fs. Updates requiring reboot are already flagged and notify user, when using yast.
If it ever happens again try to collect more logs so we could actually figure out what went wrong. (dmesg/journalctl/...).
As I wrote in my description sddm-update did really break my /fs, when first -after the update- I hibernate the system and then -after resuming- reboot it. Today I updated sddm with yast and there was no notifier or pop-up, that reboot is required. As it wasn't before. Until I found out, what the reason was, it was a lot of work, to repair the system again for several times (I avoid it now, by rebooting immediately.) This is the reason why I asked, if somebody else could confirm this. When booting fails, there are no logs etc, because it is too early. For me this problem is not yet solved, but maybe somebody else have to find it out too. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com