http://bugzilla.opensuse.org/show_bug.cgi?id=1083939 http://bugzilla.opensuse.org/show_bug.cgi?id=1083939#c1 --- Comment #1 from Thomas Schmid --- Created attachment 762680 --> http://bugzilla.opensuse.org/attachment.cgi?id=762680&action=edit Syslog during problem 2018-05-03T09:12 and T09:13 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1083939 http://bugzilla.opensuse.org/show_bug.cgi?id=1083939#c3 --- Comment #3 from Thomas Schmid --- Unfortunately this is not possible: I have a Xorg.0.log.old which is from the right period. But for unknown reasons, it starts with log entries having kernel time stamps pointing at a system time 3h *after* the event. As I wrote, 3+h after the incident, I did a openSuSE update and restarted the X260 labtop. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1083939 http://bugzilla.opensuse.org/show_bug.cgi?id=1083939#c5 --- Comment #5 from Stefan Dirsch --- (In reply to Thomas Schmid from comment #4)

I guess at the restart of the X.org, it copied the Xorg.0.log to Xorg.0.log.old. Then when I restarted the labtop, Xorg log got rotated again, overwriting Xorg.0.log.old.

Yes. That's correct. If you can't access the system any longer after the issue has happened and need to reboot, you can reboot in runlevel 3, so X isn't started. Just add 3 to the kernel command line in grub. Then save Xorg.0.log.old somehow. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1083939 http://bugzilla.opensuse.org/show_bug.cgi?id=1083939#c9 Max Staudt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |mstaudt@suse.com Resolution|--- |INVALID Flags|needinfo?(thomi.schmid@swis | |sonline.ch) | --- Comment #9 from Max Staudt --- Okay, it's been two weeks, and no further complaints. It may just as well have been a glitch in Plasma. Let's close this for now, and if it becomes reproducible, please feel free to REOPEN the ticket, so we can have a look. For lack of a better label, I'll close this as RESOLVED INVALID for now. -- You are receiving this mail because: You are on the CC list for the bug.