Application: plasmashell (6.2.4) ApplicationNotResponding [ANR]: false Qt Version: 6.8.0 Frameworks Version: 6.8.0 Operating System: Linux 6.12.1-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 6.2.4 [CoredumpBackend] -- Information about the crash: This happened after unlocking my workstation after leaving if for about 2 hours. I have a shader wallpaper for the lock screen. It behaved normally until I successfully enterned my password. Then, only the application windows and no KDE desktop was available. I am using a single display at 7680x2160 (32:9 ratio) monitor. I have noticed this ratio and resolution seems to push the system a bit. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x000076500a0f1750 in QOpenGLContext::isValid (this=0x764e943b8d80) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qopenglcontext.cpp:520 #6 QOpenGLContext::doneCurrent (this=0x764e943b8d80) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qopenglcontext.cpp:746 #7 0x000076500a0fc252 in QGuiGLThreadContext::~QGuiGLThreadContext (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qopenglcontext.cpp:35 #8 qThreadStorage_deleteData<QGuiGLThreadContext> (d=0x764ff4025fb0) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthreadstorage.h:56 #9 QThreadStorage<QGuiGLThreadContext*>::deleteData (x=0x764ff4025fb0) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthreadstorage.h:99 Reported using DrKonqi
Created attachment 176253 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Searchable backtrace Thread 1 (Thread 0x764f90ff96c0 (LWP 184862)): [KCrash Handler] #5 0x000076500a0f1750 in QOpenGLContext::isValid (this=0x764e943b8d80) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qopenglcontext.cpp:520 #6 QOpenGLContext::doneCurrent (this=0x764e943b8d80) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qopenglcontext.cpp:746 #7 0x000076500a0fc252 in QGuiGLThreadContext::~QGuiGLThreadContext (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qopenglcontext.cpp:35 #8 qThreadStorage_deleteData<QGuiGLThreadContext> (d=0x764ff4025fb0) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthreadstorage.h:56 #9 QThreadStorage<QGuiGLThreadContext*>::deleteData (x=0x764ff4025fb0) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthreadstorage.h:99 #10 0x00007650096e0e0c in QThreadStorageData::finish (p=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthreadstorage.cpp:164 #11 QThreadStorageData::finish (p=0x5e0527431918) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthreadstorage.cpp:135 #12 0x000076500982a0a0 in operator() (__closure=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthread_unix.cpp:364 #13 (anonymous namespace)::terminate_on_exception<QThreadPrivate::finish(void*)::{lambda()#1}>(QThreadPrivate::finish(void*)::{lambda()#1}&&) [clone .isra.0] (t=...) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthread_unix.cpp:263 #14 0x00007650096cf608 in QThreadPrivate::finish (arg=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthread_unix.cpp:344 #15 operator() (__closure=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthread_unix.cpp:293 #16 QScopeGuard<QThreadPrivate::start(void*)::<lambda()> >::~QScopeGuard (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/tools/qscopeguard.h:41 #17 QScopeGuard<QThreadPrivate::start(void*)::<lambda()> >::~QScopeGuard(void) (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/tools/qscopeguard.h:38 #18 0x0000765008e4e4ff in __GI___call_tls_dtors () at cxa_thread_atexit_impl.c:156 #19 0x0000765008ea3164 in start_thread (arg=<optimized out>) at pthread_create.c:452 #20 0x0000765008f2849c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thank you for the bug report. Based on the backtrace it seems very similar to bug 489643. I'm marking this as a duplicate of that one. You can follow the progress of this issue in the other report. *** This bug has been marked as a duplicate of bug 489643 ***