Bug 432278 - Kwin crashes when attempting drag-and-drop from Dolphin to Discord for the second time
Summary: Kwin crashes when attempting drag-and-drop from Dolphin to Discord for the se...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 5.20.90
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-29 15:14 UTC by Alex
Modified: 2021-02-18 05:41 UTC (History)
1 user (show)

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


Attachments
xdg-desktop-portal-kde backtrace (1.87 KB, text/vnd.kde.kcrash-report)
2021-01-29 15:14 UTC, Alex
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2021-01-29 15:14:42 UTC
Created attachment 135281 [details]
xdg-desktop-portal-kde backtrace

It also happens when dragging something from Telegram into Discord. I'm not sure which other apps besides Discord could be used to replicate this crash. When the crash occurs, the screen locks up for a second, before apparently causing every open app to crash, because a separate crash handler will appear for each one, in addition to xdg-desktop-portal-kde. Attached is a backtrace for that, but I don't know how useful it is. I'm not sure if that kind of behaviour is normal for kwin crashes in wayland sessions also.
Comment 1 Nate Graham 2021-02-01 19:25:25 UTC
Application: xdg-desktop-portal-kde (xdg-desktop-portal-kde), signal: Aborted

[KCrash Handler]
#4  0x00007f3aefc5c9d5 in raise () from /lib64/libc.so.6
#5  0x00007f3aefc458a4 in abort () from /lib64/libc.so.6
#6  0x00007f3af008348f in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5
#7  0x00007f3aec248eb3 in QtWaylandClient::QWaylandDisplay::checkError() const [clone .cold] () from /lib64/libQt5WaylandClient.so.5
#8  0x00007f3aec2580ea in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5
#9  0x00007f3af02833c0 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#10 0x00007f3af028677a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5
#11 0x00007f3af0286f21 in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5
#12 0x00007f3af1a2aec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#13 0x00007f3af0253bd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#14 0x00007f3af02a1157 in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#15 0x00007f3aee96096f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#16 0x00007f3aee9b2758 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0
#17 0x00007f3aee95dd43 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#18 0x00007f3af02a06f3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#19 0x00007f3af025257b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#20 0x00007f3af025a1b4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#21 0x0000556a8f40be37 in main ()
[Inferior 1 (process 2345) detached]
Comment 2 Alex 2021-02-18 05:41:50 UTC
I can't reproduce this on Plasma 5.21, I'm guessing it was fixed.