[kde] [Bug 467866] New: KDE window manager crashes when using Qt application

Laura Dietz bugzilla_noreply at kde.org
Tue Mar 28 00:18:41 BST 2023


https://bugs.kde.org/show_bug.cgi?id=467866

            Bug ID: 467866
           Summary: KDE window manager crashes when using Qt application
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: dietz at smart-cactus.org
  Target Milestone: ---

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 at entry=6) at
./nptl/pthread_kill.c:89
#7  0x00007f3eb9056476 in __GI_raise (sig=sig at 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 at entry=0x55d5fd9f4c60, argc=argc at entry=1,
argv=argv at 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]

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list