https://bugs.kde.org/show_bug.cgi?id=460798
--- Comment #4 from tho...@zell-mbc.com --- (In reply to Nate Graham from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports. > > Can you please attach one? Thanks! I had two more crashes over the weekend, but unfortunately none led to a coredump. What I can find this time is lots of processes which die because something is missing. Going up the log the below is the first crash entry and all the others may fail because of sddm to go away: Okt 23 21:39:55 hermes sddm[746]: Authentication error: "Process crashed" Okt 23 21:39:55 hermes sddm[746]: Auth: sddm-helper crashed (exit code 15) Okt 23 21:39:55 hermes sddm[746]: Authentication error: "Process crashed" Okt 23 21:39:55 hermes sddm[746]: Auth: sddm-helper exited with 15 Okt 23 21:39:55 hermes sddm[746]: Display server stopping... Okt 23 21:39:55 hermes systemd[1]: Stopped target Graphical Interface. Okt 23 21:39:55 hermes kglobalaccel5[1136]: The X11 connection broke (error 1). Did the X11 server die? Next to die is akonadi: Okt 23 21:39:55 hermes akonadiserver[1516]: org.kde.pim.akonadiserver: Control process died, committing suicide! Plasma is next: Okt 23 21:39:55 hermes systemd[871]: plasma-gmenudbusmenuproxy.service: Main process exited, code=exited, status=1/FAILURE Okt 23 21:39:55 hermes systemd[871]: plasma-gmenudbusmenuproxy.service: Failed with result 'exit-code'. Okt 23 21:39:55 hermes systemd-coredump[37353]: Failed to connect to coredump service: Connection refused And lots more… -- You are receiving this mail because: You are watching all bug changes.
