https://bugs.kde.org/show_bug.cgi?id=524155
Bug ID: 524155
Summary: Kwin randomly crashes on boot
Classification: Plasma
Product: kwin
Version First 6.7.4
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Application: kwin_wayland (6.7.4)
ApplicationNotResponding [ANR]: false
Qt Version: 6.11.1
Frameworks Version: 6.28.0
Operating System: Linux 7.1.7-200.fc44.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 44 (KDE Plasma Desktop Edition)"
DrKonqi: 6.7.4 [CoredumpBackend]
-- Information about the crash:
I simply started the system, logged in, and kwin reported that it had crashed.
The only thing I noticed is that the login-manager took about 1/2 s longer load
time than normal when this happens.
The crash can be reproduced sometimes.
-- Backtrace (Reduced):
#5 0x00007f5b119e50a1 in std::vector<std::unique_ptr<KWin::DrmCommit,
std::default_delete<KWin::DrmCommit> >,
std::allocator<std::unique_ptr<KWin::DrmCommit,
std::default_delete<KWin::DrmCommit> > > >::size (this=<optimized out>) at
/usr/include/c++/16/bits/stl_vector.h:1109
#8 KWin::DrmGpu::pageFlipHandler (fd=39, sequence=3053, sec=55, usec=991179,
crtc_id=151, user_data=0x7f5abc001370) at
/usr/src/debug/kwin-6.7.4-1.fc44.x86_64/src/backends/drm/drm_gpu.cpp:559
#9 0x00007f5b0ed64795 in drmHandleEvent (fd=39, evctx=0x7fff97dd7660) at
../xf86drmMode.c:1070
#10 0x00007f5b119e45ac in KWin::DrmGpu::dispatchEvents (this=<optimized out>)
at /usr/src/debug/kwin-6.7.4-1.fc44.x86_64/src/backends/drm/drm_gpu.cpp:594
#11 0x00007f5b0e784eb7 in QtPrivate::QSlotObjectBase::call (this=<optimized
out>, r=0x5565e9bba870, a=<optimized out>) at
/usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qobjectdefs_impl.h:462
#12 doActivate<false> (sender=<optimized out>, signal_index=<optimized out>,
argv=argv@entry=0x7fff97dd7790) at
/usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qobject.cpp:4372
[...]
#15 QSocketNotifier::activated (this=this@entry=0x5565e9b3fbd0, _t1=...,
_t2=<optimized out>, _t3=...) at
/usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/redhat-linux-build/src/corelib/Core_autogen/include/moc_qsocketnotifier.cpp:161
#16 0x00007f5b0e7943ef in QSocketNotifier::event (this=0x5565e9b3fbd0,
e=<optimized out>) at
/usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qsocketnotifier.cpp:325
#17 0x00007f5b0fa3f92e in QApplicationPrivate::notify_helper (this=<optimized
out>, receiver=0x5565e9b3fbd0, e=0x7fff97dd78e0) at
/usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/widgets/kernel/qapplication.cpp:3276
#18 0x00007f5b0e70f7b8 in QCoreApplication::notifyInternal2
(receiver=0x5565e9b3fbd0, event=0x7fff97dd78e0) at
/usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qcoreapplication.cpp:1114
#19 0x00007f5b0e70f7fd in QCoreApplication::sendEvent (receiver=<optimized
out>, event=<optimized out>) at
/usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qcoreapplication.cpp:1559
#20 0x00007f5b0e90f315 in QEventDispatcherUNIXPrivate::activateSocketNotifiers
(this=this@entry=0x5565e9949cb0) at
/usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qeventdispatcher_unix.cpp:277
#21 0x00007f5b0e90fc83 in QEventDispatcherUNIX::processEvents (this=<optimized
out>, flags=...) at
/usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qeventdispatcher_unix.cpp:499
#22 0x00007f5b0f561f22 in QUnixEventDispatcherQPA::processEvents
(this=<optimized out>, flags=...) at
/usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/gui/platform/unix/qunixeventdispatcher.cpp:28
#23 0x00007f5b0e71d57b in QEventLoop::exec (this=this@entry=0x7fff97dd7ab0,
flags=..., flags@entry=...) at
/usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/global/qflags.h:78
#24 0x00007f5b0e718992 in QCoreApplication::exec () at
/usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qcoreapplication.cpp:1457
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
