Bug 467866 - KDE window manager crashes when using Qt application
Summary: KDE window manager crashes when using Qt application
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.24.7
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-27 23:18 UTC by Laura Dietz
Modified: 2023-05-05 03:46 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Laura Dietz 2023-03-27 23:18:41 UTC
Application: konsole (21.12.3)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.15.2-051502-generic x86_64
Windowing System: Wayland
Distribution: Ubuntu 22.04.2 LTS
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:

I was using Lyx (a Qt application). Nothing special, just writing text, maybe copy & paste.


Since I switched from X11 to kwin/Wayland/Plasma, the KDE window manager crashes randomly multiple times a day, when I use various applications. 

These are random crashes, so I can't reproduce them.

I think this could be a secondary crash, since it crashed while flushing the wayland requests.



-- Backtrace:
Application: Konsole (konsole), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139907280649856) at ./nptl/pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=139907280649856) at ./nptl/pthread_kill.c:78
#6  __GI___pthread_kill (threadid=139907280649856, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#7  0x00007f3eb9056476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x00007f3eb903c7f3 in __GI_abort () at ./stdlib/abort.c:79
#9  0x00007f3eb94f8ba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f3eb7660e45 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#11 0x00007f3eb767111a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#12 0x00007f3eb97597c8 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f3eb975ccb3 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f3eb975d4e3 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f3eba2bc713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f3eb9721e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f3eb977bcc5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f3eb78edd3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f3eb79426c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f3eb78eb3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f3eb977b0b8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f3eb972075b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007f3eb9728cf4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x000055d5fd9f6795 in ?? ()
#25 0x00007f3eb903dd90 in __libc_start_call_main (main=main@entry=0x55d5fd9f4c60, argc=argc@entry=1, argv=argv@entry=0x7ffee66a3da8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x00007f3eb903de40 in __libc_start_main_impl (main=0x55d5fd9f4c60, argc=1, argv=0x7ffee66a3da8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffee66a3d98) at ../csu/libc-start.c:392
#27 0x000055d5fd9f6e15 in ?? ()
[Inferior 1 (process 12524) detached]
Comment 1 Nate Graham 2023-04-05 00:19:10 UTC
Yes, when KWin crashes, apps will crash too. Can you attach a symbolicated backtrace of the kwin_wayland crash? `coredumpctl` may help; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl.
Comment 2 Bug Janitor Service 2023-04-20 03:45:46 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2023-05-05 03:46:12 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!