Bug 461605

Summary: Plasma repeatedly crashing
Product: [Plasma] plasmashell Reporter: kde
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: kde, nate
Priority: NOR Keywords: drkonqi
Version: 5.25.5   
Target Milestone: 1.0   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description kde 2022-11-08 18:30:53 UTC
Application: plasmashell (5.25.5)

Qt Version: 5.15.6
Frameworks Version: 5.98.0
Operating System: Linux 5.15.0-52-generic x86_64
Windowing System: X11
Distribution: Feren OS
DrKonqi: 5.25.5 [CoredumpBackend]

-- Information about the crash:
After logging in, Plasma crashed, which happens lots of times on my machine. But this time it did not recover automatically. Instead, a second crash happened, which is this one.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

[New LWP 2531]
[New LWP 2543]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007f19bf5ff00b in raise () from /lib/x86_64-linux-gnu/libc.so.6
[Current thread is 1 (Thread 0x7f19bb7ed2c0 (LWP 2531))]
__preamble__
[Current thread is 1 (Thread 0x7f19bb7ed2c0 (LWP 2531))]

Thread 2 (Thread 0x7f19ba954700 (LWP 2543)):
#0  0x00007f19bf6ce99f in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f19bdde236e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f19bdde24a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f19bfc9fb6b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f19bfc43b0b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f19bfa5d342 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f19c05def4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007f19bfa5e543 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f19bf28f609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#9  0x00007f19bf6db133 in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f19bb7ed2c0 (LWP 2531)):
[KCrash Handler]
#3  0x00007f19bf5ff00b in raise () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x00007f19bf5de859 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x00007f19bfa22bd9 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f19bfa21fe5 in qt_assert(char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00005566981eac55 in ScreenPool::handleScreenRemoved (this=0x556698cc33d0, screen=0x556698c21550) at /tmp/git-sources/plasma-workspace/shell/screenpool.cpp:445
#8  0x00005566981f0e25 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<QScreen*>, void, void (ScreenPool::*)(QScreen*)>::call (f=(void (ScreenPool::*)(ScreenPool * const, QScreen *)) 0x5566981ea89e <ScreenPool::handleScreenRemoved(QScreen*)>, o=0x556698cc33d0, arg=0x7ffd1a648df0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152
#9  0x00005566981f08ff in QtPrivate::FunctionPointer<void (ScreenPool::*)(QScreen*)>::call<QtPrivate::List<QScreen*>, void> (f=(void (ScreenPool::*)(ScreenPool * const, QScreen *)) 0x5566981ea89e <ScreenPool::handleScreenRemoved(QScreen*)>, o=0x556698cc33d0, arg=0x7ffd1a648df0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185
#10 0x00005566981efb9f in QtPrivate::QSlotObject<void (ScreenPool::*)(QScreen*), QtPrivate::List<QScreen*>, void>::impl (which=1, this_=0x556698cb1110, r=0x556698cc33d0, a=0x7ffd1a648df0, ret=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:418
#11 0x00007f19bfc7c2c2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f19c001ff56 in QGuiApplication::screenRemoved(QScreen*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x00007f19c005643c in QScreen::~QScreen() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#14 0x00007f19c005658d in QScreen::~QScreen() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#15 0x00007f19c0004aeb in QWindowSystemInterface::handleScreenRemoved(QPlatformScreen*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#16 0x00007f19bb07f0de in QXcbConnection::destroyScreen(QXcbScreen*) () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#17 0x00007f19bb07f8d8 in QXcbConnection::updateScreens(xcb_randr_notify_event_t const*) () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#18 0x00007f19bb052e70 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#19 0x00007f19bb053276 in QXcbConnection::processXcbEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#20 0x00007f19bb07ce37 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#21 0x00007f19bdde217d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f19bdde2400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f19bdde24a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f19bfc9fb52 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007f19bfc43b0b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007f19bfc4bcb4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x000055669818acd2 in main (argc=1, argv=0x7ffd1a649508) at /tmp/git-sources/plasma-workspace/shell/main.cpp:243

Reported using DrKonqi
Comment 1 Bug Janitor Service 2022-11-08 18:33:31 UTC
Thank you for the bug report!

Please note that Plasma 5.25.5 is not supported for much longer by KDE; supported versions are 5.24, and 5.26 or newer.

If at all possible please upgrade to a supported version and verify that the bug is still happening there.

If you're unsure how to do this, contact your distributor about it.
Comment 2 Nate Graham 2022-11-09 20:02:49 UTC

*** This bug has been marked as a duplicate of bug 454057 ***
Comment 3 Nate Graham 2024-09-25 21:01:28 UTC

*** This bug has been marked as a duplicate of bug 484687 ***