*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When I lock the screen and log back in the system tray populates with about a dozen "plasmashell has crashed" errors. Additionally, I'll sometimes be able to log in and not have a desktop wallpaper (black screen) and now taskbar. Pretty generic and I'm sorry for that, but it's happening on the regular for me. STEPS TO REPRODUCE 1. Log out 2. Log back in 3. see tons of "plasmashell has crashed" errors - seems oddly similar to 445752 OBSERVED RESULT Crashed plasmashell with accompanying warnings and sometimes need to restart computer (if I don't have konsole open to kstart plasmashell). EXPECTED RESULT Working plasmashell for accessing and using apps SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 40 x86_64 (available in About System) KDE Plasma Version: 6.1.2 KDE Frameworks Version: Qt Version: qt6 6.7.2-1, qt5 5.15.14 ADDITIONAL INFORMATION
Created attachment 171747 [details] Crash report with the extras downloaded
(In reply to mrford17 from comment #0) > *** > If you're not sure this is actually a bug, instead post about it at > https://discuss.kde.org > > If you're reporting a crash, attach a backtrace with debug symbols; see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > *** > > SUMMARY > When I lock the screen and log back in the system tray populates with about > a dozen "plasmashell has crashed" errors. Additionally, I'll sometimes be > able to log in and not have a desktop wallpaper (black screen) and now > taskbar. Pretty generic and I'm sorry for that, but it's happening on the > regular for me. > > STEPS TO REPRODUCE > 1. Log out > 2. Log back in > 3. see tons of "plasmashell has crashed" errors - seems oddly similar to > 445752 > > OBSERVED RESULT > Crashed plasmashell with accompanying warnings and sometimes need to restart > computer (if I don't have konsole open to kstart plasmashell). > > EXPECTED RESULT > Working plasmashell for accessing and using apps > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: Fedora 40 x86_64 > (available in About System) > KDE Plasma Version: 6.1.2 > KDE Frameworks Version: > Qt Version: qt6 6.7.2-1, qt5 5.15.14 > > ADDITIONAL INFORMATION Yep, totally my bad - didn't attach the file I had sitting open the whole time I was filling out the report, that's on me.
Searchable backtrace Thread 1 (Thread 0x7f398cc006c0 (LWP 3004372)): [KCrash Handler] #5 QtWaylandClient::QWaylandWindow::waylandScreen (this=this@entry=0x556b0c8a6190) at /usr/src/debug/qt6-qtwayland-6.7.2-2.fc40.x86_64/src/client/qwaylandwindow.cpp:956 #6 0x00007f39e8dabb9b in QtWaylandClient::QWaylandWindow::devicePixelRatio (this=0x556b0c8a6190) at /usr/src/debug/qt6-qtwayland-6.7.2-2.fc40.x86_64/src/client/qwaylandwindow.cpp:1519 #7 QtWaylandClient::QWaylandWindow::scale (this=this@entry=0x556b0c8a6190) at /usr/src/debug/qt6-qtwayland-6.7.2-2.fc40.x86_64/src/client/qwaylandwindow.cpp:1516 #8 0x00007f39e1161fdb in QtWaylandClient::QWaylandEglWindow::updateSurface (this=0x556b0c8a6190, create=true) at /usr/src/debug/qt6-qtwayland-6.7.2-2.fc40.x86_64/src/hardwareintegration/client/wayland-egl/qwaylandeglwindow.cpp:70 #9 0x00007f39e1162973 in QtWaylandClient::QWaylandGLContext::makeCurrent (this=this@entry=0x7f3930002210, surface=<optimized out>) at /usr/src/debug/qt6-qtwayland-6.7.2-2.fc40.x86_64/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:318 #10 0x00007f39e81a36ba in QOpenGLContext::makeCurrent (this=0x7f3930001f60, surface=0x556b0c6de4e0) at /usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/gui/kernel/qopenglcontext.cpp:664 #11 0x00007f39e81bbaea in QRhiGles2::ensureContext (this=0x7f39300018c0, surface=<optimized out>) at /usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/gui/rhi/qrhigles2.cpp:632 #12 0x00007f39e92ce873 in QSGRenderThread::invalidateGraphics (this=this@entry=0x556b0c6dc660, window=0x556b0c39feb0, inDestructor=true) at /usr/src/debug/qt6-qtdeclarative-6.7.2-1.fc40.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:473 #13 0x00007f39e92d3d12 in QSGRenderThread::event (this=0x556b0c6dc660, e=0x556b0c58f8e0) at /usr/src/debug/qt6-qtdeclarative-6.7.2-1.fc40.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:368 #14 0x00007f39e92d011b in QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x556b0c6dc660) at /usr/src/debug/qt6-qtdeclarative-6.7.2-1.fc40.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:869 #15 0x00007f39e92d0342 in QSGRenderThread::run (this=0x556b0c6dc660) at /usr/src/debug/qt6-qtdeclarative-6.7.2-1.fc40.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:991 #16 0x00007f39e775463c in operator() (__closure=<optimized out>) at /usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:326 #17 (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > (t=...) at /usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:262 #18 QThreadPrivate::start (arg=0x556b0c6dc660) at /usr/src/debug/qt6-qtbase-6.7.2-3.fc40.x86_64/src/corelib/thread/qthread_unix.cpp:285 #19 0x00007f39e6ea6507 in start_thread (arg=<optimized out>) at pthread_create.c:447 #20 0x00007f39e6f2a40c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Do you have multiple monitors? What graphics card do you have, if any?
Thank you for the bug report! This issue has already been filed and was determined to be an upstream bug in Qt; please see that bug report for updates on a fix. *** This bug has been marked as a duplicate of bug 489180 ***
(In reply to Akseli Lahtinen from comment #4) > Do you have multiple monitors? > > What graphics card do you have, if any? I do have multiple monitors, yes - and I have a Radeon 7600xt graphics card. I saw that this bug was marked as duplicate of 489180 and, after reading through that bug report, I can confirm the behavior is the same: when I turn off my main monitor I can generate the plasmashell crashes. Thanks for looking at this, I'll watch the linked report for a fix.