Application: kalarm (3.1.2 (KDE Apps 20.12.2)) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.14-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.3 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: upon KDE start kAlarm crashes same every time I try launching it manually The crash can be reproduced every time. -- Backtrace: Application: KAlarm (kalarm), signal: Segmentation fault [KCrash Handler] #4 0x00007f0566a579fb in xcb_send_request_with_fds64 () from /lib64/libxcb.so.1 #5 0x00007f0566a581dd in xcb_send_request () from /lib64/libxcb.so.1 #6 0x00007f0566a598a8 in xcb_intern_atom () from /lib64/libxcb.so.1 #7 0x00007f0569643c20 in Atoms::init() () from /lib64/libKF5WindowSystem.so.5 #8 0x00007f0569643e01 in atomsForConnection(xcb_connection_t*) () from /lib64/libKF5WindowSystem.so.5 #9 0x00007f056964ac35 in NETRootInfo::NETRootInfo(xcb_connection_t*, QFlags<NET::Property>, QFlags<NET::Property2>, int, bool) () from /lib64/libKF5WindowSystem.so.5 #10 0x000055fc104d64af in (anonymous namespace)::findFullScreenWindows (screenTypes=..., screenRects=...) at /usr/src/debug/kalarm-20.12.2-1.fc34.x86_64/src/messagewindow.cpp:1389 #11 MessageWindow::getWorkAreaAndModal (this=0x55fc1132cea0) at /usr/src/debug/kalarm-20.12.2-1.fc34.x86_64/src/messagewindow.cpp:1279 #12 0x000055fc104c64fb in MessageWindow::MessageWindow (flags=0, alarm=..., event=..., this=0x55fc1132cea0, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /usr/src/debug/kalarm-20.12.2-1.fc34.x86_64/src/messagewindow.cpp:126 #13 MessageDisplay::create (event=..., alarm=..., flags=0) at /usr/src/debug/kalarm-20.12.2-1.fc34.x86_64/src/messagedisplay.cpp:37 #14 0x000055fc104acd90 in KAlarmApp::execAlarm (this=<optimized out>, event=..., alarm=..., flags=...) at /usr/src/debug/kalarm-20.12.2-1.fc34.x86_64/src/kalarmapp.cpp:2285 #15 0x000055fc104a6bb8 in KAlarmApp::handleEvent (findUniqueId=<optimized out>, action=KAlarmApp::QueuedAction::Handle, id=..., this=0x55fc10fe10c0) at /usr/src/debug/kalarm-20.12.2-1.fc34.x86_64/src/kalarmapp.cpp:1971 #16 KAlarmApp::processQueue (this=0x55fc10fe10c0) at /usr/src/debug/kalarm-20.12.2-1.fc34.x86_64/src/kalarmapp.cpp:1083 #17 0x00007f0567ecd809 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #18 0x00007f0568abe423 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x00007f0567ea3098 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #20 0x00007f0567ea6606 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #21 0x00007f0567ef4bf7 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #22 0x00007f0565bb84cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #23 0x00007f0565c0c4e8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #24 0x00007f0565bb5c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #25 0x00007f0567ef4698 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #26 0x00007f0567ea1ab2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #27 0x00007f0567ea9fe4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #28 0x000055fc10410bc5 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kalarm-20.12.2-1.fc34.x86_64/src/main.cpp:70 [Inferior 1 (process 4789) detached] Possible duplicates by query: bug 348572, bug 269759, bug 257262, bug 214384, bug 189352. Reported using DrKonqi
This crash only occurs when using Wayland, when using multiple monitors. The code concerned checks whether an alarm window should be displayed on top of a full screen window: this code is for now disabled on Wayland. It is now fixed by commit a063257b4bb673f3ab7d85a15a1c926f9c768696, and will be in KAlarm version 3.3.0, which will be included in KDE apps release 21.08.