Bug 491797 - KWin Wayland crashed randomly
Summary: KWin Wayland crashed randomly
Status: RESOLVED DUPLICATE of bug 488713
Alias: None
Product: kwin
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 6.1.4
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-16 17:54 UTC by me
Modified: 2024-09-20 12:44 UTC (History)
1 user (show)

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


Attachments
Systemd journal with the stacktrace and everything. (699.26 KB, text/plain)
2024-08-16 17:54 UTC, me
Details
Better stacktrace. (63.23 KB, text/plain)
2024-08-20 17:21 UTC, me
Details
Stacktrace #3 (63.86 KB, text/plain)
2024-08-20 17:26 UTC, me
Details

Note You need to log in before you can comment on or make changes to this bug.
Description me 2024-08-16 17:54:57 UTC
Created attachment 172676 [details]
Systemd journal with the stacktrace and everything.

SUMMARY
I was watching a video on the FreeTube app, then at some point everything went black and got a bunch of windows from different applications telling me that they had crashed (meaning the compositor had crashed).

STEPS TO REPRODUCE
1. Open a series of videos on the FreeTube app
2. Wait for the crash 

OBSERVED RESULT
KWin crashed.

EXPECTED RESULT
KWin should not crash.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
Fedora KDE 40, kernel 6.10.3-200, a bunch of other apps open like LibreWolf, Firefox, Telegram Desktop, Nheko, QOwnNotes, slow connection (if any of these other details even matter).
Comment 1 Nate Graham 2024-08-20 17:06:05 UTC
Thanks for the bug report, but unfortunately the un-symbolicated stack trace buries in a giant syslog is not very useful. Can you follow the steps at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl to refine it, and then paste the output here?
Comment 2 me 2024-08-20 17:21:51 UTC
Created attachment 172780 [details]
Better stacktrace.

Uploaded the better stacktrace.
Comment 3 Nate Graham 2024-08-20 17:23:25 UTC
Hmm, I'm afraid that isn't any better. You don't need to use sudo, just do `coredumpctl gdb 2583`. Then when prompted, type `bt`.
Comment 4 me 2024-08-20 17:26:45 UTC
Created attachment 172781 [details]
Stacktrace #3
Comment 5 Nate Graham 2024-08-20 17:31:40 UTC
Thanks. Unfortunately it's still not very useful, though it's not your fault.


[Current thread is 1 (Thread 0x7f0e6eed4b40 (LWP 2583))]
(gdb) bt
#0  0x00007f0e75796cc1 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt6Core.so.6
#1  0x00007f0e75952a47 in QTimerInfoList::activateTimers() () from /lib64/libQt6Core.so.6
#2  0x00007f0e7595701b in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt6Core.so.6
#3  0x00007f0e76563392 in QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt6Gui.so.6
#4  0x00007f0e757a3b03 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt6Core.so.6
#5  0x00007f0e7579f9bc in QCoreApplication::exec() () from /lib64/libQt6Core.so.6
#6  0x000055721ee6b3a1 in main ()

Not sure what else to do; will let the KWin devs proceed from here.
Comment 6 Vlad Zahorodnii 2024-09-20 12:44:36 UTC

*** This bug has been marked as a duplicate of bug 488713 ***