Bug 511874

Summary: PlasmaShell crashed on log in, with inconsistent QPalette focus states in DrKonqi, after ANR'ing before (and during) the previous logout
Product: [Plasma] plasmashell Reporter: Roke Julian Lockhart Beedell <4wy78uwh>
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs-null>
Status: REPORTED ---    
Severity: crash CC: kdedev
Priority: NOR Keywords: drkonqi
Version First Reported In: master   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
See Also: https://bugzilla.redhat.com/show_bug.cgi?id=2411800
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/290964/events/e3f7b4bc9a3041c6a0b388b850eb46fa/
Attachments: New crash information added by DrKonqi
A Screenshot Of The Inconsistent Window
A Screencast That Demonstrates The Inconsistency Of The Window's Colour Scheme Upon Selection

Description Roke Julian Lockhart Beedell 2025-11-09 17:33:51 UTC
Application: plasmashell (6.5.2)

ApplicationNotResponding [ANR]: false
Qt Version: 6.10.0
Frameworks Version: 6.19.0
Operating System: Linux 6.17.7-300.fc43.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 43 (KDE Plasma Desktop Edition)"
DrKonqi: 6.5.2 [CoredumpBackend]

-- Information about the crash:
Without any noticeable interaction from me, the sole visible panel hung. (I neglected to confirm whether the desktop was impacted, but I presume so.) To remediate this, I issued the "Log out" command via KRunner. This appeared to do nothing, so I repeated it. The sound for the first invocation played 15 s late, but I solely heard it once. 3 s after that, I invoked the command again, and approximately 5 s after that, I was dumped to SDDM. When I logged back in, I solely saw a black screen for 3 s. Then, DrKonqi appeared. However, as a screencast, that I shall upload after this, demonstrates, its QPalette is `breezedark` when focussed. However, it utilises Breeze Light when not focussed, as all other applications are, whether focused or not.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#6  0x00007f151d2f940a in sys_futex (addr1=0x557071df2794, op=9, val1=2, timeout=0x0, addr2=0x0, val3=-1) at ../src/util/futex.c:43
#7  futex_wait (addr=addr@entry=0x557071df2794, value=value@entry=2, timeout=timeout@entry=0x0) at ../src/util/futex.c:55
#8  0x00007f151d306830 in do_futex_fence_wait (fence=fence@entry=0x557071df2794, timeout=timeout@entry=false, abs_timeout=abs_timeout@entry=0) at ../src/util/u_queue.c:131
#9  0x00007f151d307a0c in _util_queue_fence_wait (fence=0x557071df2794) at ../src/util/u_queue.c:146
#10 util_queue_fence_wait (fence=0x557071df2794) at ../src/util/u_queue.h:181
#11 util_queue_fence_wait (fence=0x557071df2794) at ../src/util/u_queue.h:178
#12 util_queue_finish (queue=queue@entry=0x55706ae24a30) at ../src/util/u_queue.c:722
#13 0x00007f151d760aaa in si_set_debug_callback (ctx=0x557071fbba90, cb=0x0) at ../src/gallium/drivers/radeonsi/si_pipe.c:449
#14 0x00007f151d761318 in si_destroy_context (context=0x557071fbba90) at ../src/gallium/drivers/radeonsi/si_pipe.c:202
#15 0x00007f151d546a31 in tc_destroy (_pipe=0x5570724d4f80) at ../src/gallium/auxiliary/util/u_threaded_context.c:5400
#16 0x00007f151cec7260 in st_destroy_context_priv (st=st@entry=0x5570726d77d0, destroy_pipe=destroy_pipe@entry=true) at ../src/mesa/state_tracker/st_context.c:356
#17 0x00007f151cec8d4d in st_destroy_context (st=0x5570726d77d0) at ../src/mesa/state_tracker/st_context.c:967
#18 0x00007f151ce2993b in dri_destroy_context (ctx=0x55706b8b1480) at ../src/gallium/frontends/dri/dri_context.c:267
#19 0x00007f151ce2d6be in driDestroyContext (ctx=<optimized out>) at ../src/gallium/frontends/dri/dri_util.c:631
#20 0x00007f152df65669 in dri2_destroy_context (disp=<optimized out>, ctx=0x557070b43a10) at ../src/egl/drivers/dri2/egl_dri2.c:1271


Reported using DrKonqi
Comment 1 Roke Julian Lockhart Beedell 2025-11-09 17:33:52 UTC
Created attachment 186651 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 3 Roke Julian Lockhart Beedell 2025-11-09 17:55:08 UTC
Created attachment 186652 [details]
A Screenshot Of The Inconsistent Window

Apologies about the blur. See https://bugs.kde.org/show_bug.cgi?id=510982#c6.
Comment 4 Roke Julian Lockhart Beedell 2025-11-09 17:56:31 UTC
Created attachment 186654 [details]
A Screencast That Demonstrates The Inconsistency Of The Window's Colour Scheme Upon Selection

I have attached the screencast, as I aforestated.
Comment 5 Roke Julian Lockhart Beedell 2025-11-09 18:07:56 UTC
Comment on attachment 186654 [details]
A Screencast That Demonstrates The Inconsistency Of The Window's Colour Scheme Upon Selection

Perhaps, this inconsistent appearance correlates with https://discuss.kde.org/t/settings-day-night-cycle-isnt-working/41524?u=rokejulianlockhart, if this bug caused it.