Bug 476709 - kwin_wayland randomly segfaults. Screen goes black then restarts but all open applications are lost.
Summary: kwin_wayland randomly segfaults. Screen goes black then restarts but all open...
Status: RESOLVED DUPLICATE of bug 475629
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.27.9
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-08 10:55 UTC by james
Modified: 2023-11-21 13:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Journal logs (including stack trace) (35.86 KB, text/plain)
2023-11-08 10:55 UTC, james
Details
Backtrace with symbols (1.21 KB, text/plain)
2023-11-10 10:45 UTC, james
Details
All threads stacktrace (12.14 KB, text/x-log)
2023-11-17 11:11 UTC, james
Details

Note You need to log in before you can comment on or make changes to this bug.
Description james 2023-11-08 10:55:24 UTC
Created attachment 162946 [details]
Journal logs (including stack trace)

SUMMARY
I've had this happen twice now, a couple of weeks apart. All of a sudden my displays go black, and a few seconds later the desktop reappear but all my applications have been terminated. Stack trace is attached.

Looking in the logs I can see that kwin_wayland has segfaulted.

STEPS TO REPRODUCE
- No idea, it seems to occur randomly.

OBSERVED RESULT
Crashes

EXPECTED RESULT
Should not crash

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION
Kernel 6.5.9
Platform: Wayland

I am using bismuth to add tiling functionality to plasma, not sure if this is related.
Comment 1 fanzhuyifan 2023-11-09 03:50:14 UTC
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols.

Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this.

Thanks again!
Comment 2 james 2023-11-10 10:45:09 UTC
Created attachment 163016 [details]
Backtrace with symbols

Hopefully the attached helps?
Comment 3 fanzhuyifan 2023-11-10 16:44:29 UTC
(In reply to james from comment #2)
> Created attachment 163016 [details]
> Backtrace with symbols
> 
> Hopefully the attached helps?

Humm the attachment doesn't show any KDE code.. Did you follow all the instructions on the wiki? Make sure to include all threads.
Comment 4 james 2023-11-15 15:14:00 UTC
(In reply to fanzhuyifan from comment #3)
> (In reply to james from comment #2)
> > Created attachment 163016 [details]
> > Backtrace with symbols
> > 
> > Hopefully the attached helps?
> 
> Humm the attachment doesn't show any KDE code.. Did you follow all the
> instructions on the wiki? Make sure to include all threads.

As I have no way to reproduce this issue I followed the instructions for using coredumpctl - this is all it gave me. It seems like the dump has now been erased from my machine so I'll have to wait until the problem reoccurs.
Comment 5 james 2023-11-17 11:11:53 UTC
Created attachment 163232 [details]
All threads stacktrace
Comment 6 james 2023-11-17 11:12:49 UTC
Ok the issue has reoccured. I tried to use coredumpctl to take a stacktrace of all threads but I'm still not seeing anything kwin related?
Comment 7 fanzhuyifan 2023-11-17 16:37:02 UTC
(In reply to james from comment #6)
> Ok the issue has reoccured. I tried to use coredumpctl to take a stacktrace
> of all threads but I'm still not seeing anything kwin related?

Yeah there doesn't seem to be anything kwin related. But your first stacktrace without the debug symbols does have kwin_related stuff..
Comment 8 james 2023-11-17 18:22:03 UTC
I'm not really sure what to do at this point. Would uploading the core dump help?
Comment 9 james 2023-11-21 13:56:27 UTC
*** This bug has been marked as a duplicate of bug 475629 ***