SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install Plasma 6.0 RC2 (kde-unstable repository on Arch is my source) 2. Open Kicker 3. Try to use keyboard to navigate Kicker, or hover over items in the menu OBSERVED RESULT Nothing is highlighted in any way. EXPECTED RESULT Items hovered over, or selected with the keyboard, should be highlighted. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I have not yet tried a fresh install of Arch Linux, so this may be an issue of configuration. If you cannot reproduce it I will try a fresh install.
Created attachment 165674 [details] Screenshot of Kicker's lack of highlighting.
Created attachment 165675 [details] The current day in the clock's calendar pop-up isn't highlighted either.
Cannot reproduce lack of highlighting on Kicker or Calendar Widget Operating System: KDE neon Testing Edition KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-17-generic (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Pro WX 3200 Series
Could this be another Qt 6.7 related issue?
Created attachment 165716 [details] There's also no volume sliders under "Applications" in the audio widget
Likely a configuration issue or an issue with your theme. If you do not use Breeze, please check if this issue also happens with the Breeze or Breeze Dark theme. If you can reproduce using the Breeze theme, please try with a new user. (In reply to Yao Mitachi from comment #0) > I have not yet tried a fresh install of Arch Linux, so this may be an issue > of configuration. If you cannot reproduce it I will try a fresh install. Note: You do only need to create a new user to test your config files, no need to reinstall
I am using Breeze Dark. Haven't customized it. Also noticed the issue with light Breeze.
Created attachment 165738 [details] Same issue with a new user.
Info provided -> reopening
I have/had the same issue with the exception of the volume slider. Based on the comments, I created a new user and tested it there. Everything worked and after I switched back, it started to work again on my account as well. I'm also on Arch and using Breeze Dark. KDE Plasma: 5.27.10 KDE Framework: 5.115.0 Qt Version: 5.15.12
Why the LTS version of Qt, rLy? Does the problem come back if you install Qt 6.7?
(In reply to Yao Mitachi from comment #11) > Why the LTS version of Qt, rLy? Does the problem come back if you install Qt > 6.7? I just choose not to go with the RC version and wait for the full rls.
Possibly related: it also looks like desktop icons don't highlight when hovered with the mouse. I pretty much had the same experience as comment #10 (I'm also using Arch). Except it didn't automatically fix itself when switching back to my regular user. I was able to fix it by removing the following things from ~/.cache (there's probably things I didn't need to remove here, but it was faster to just remove anything that looked related to plasmashell or QT): kcmshell5 plasmashell qtshadercache qtshadercache-x86_64-little_endian-lp64 icon-cache.kcache plasma-svgelements plasma_theme_breeze-dark_v5.115.0.kcache qt_compose_cache_little_endian_24803eb77a9d48f4b169d2e8e9305b2f I will note that I only saw this bug happen on my laptop that has a touchscreen, but not my desktop that has a near identical software configuration. Is there some sort of behavior that would cause Plasma to not highlight things if touch was detected as in input method?
I tried deleting those things in my ~/.cache folder but it didn't make a difference on my end. Justin Jacobs, what version of Qt are you using?
(In reply to Yao Mitachi from comment #14) > I tried deleting those things in my ~/.cache folder but it didn't make a > difference on my end. Justin Jacobs, what version of Qt are you using? KDE Plasma: 5.27.10 KDE Framework: 5.115.0 Qt Version: 5.15.12 I *did* delete the cache files from a separate TTY console without being signed into a Plasma session. I think the cache files get recreated on logout otherwise.
I didn't have kcm*, generic qtshadercache folder, or plasma-svgelements in there. Also I had a "default" theme kcache file rather than Breeze Dark specifically. However I'm on Plasma 6 (5.93) while you're on 5.27 so that is probably why our files were a bit different. Having deleted the files again from a TTY this time before logging in (actually svgelements showed up, never mind?) and some other files and folders related to KDE, just in case... No dice Might be something about Qt6.7 or Plasma 6 that prevents any workaround for working for me.
Can reproduce on arch, git source build. Seems like a recent regression, but I haven't had the time to bisect it yet. Are there any people who can reproduce this on some distro other than arch though?
Not sure when it happened, but the calendar, volume mixer, and highlighting in kicker are all working for me now. Might have been something fixed in the Arch packaging. (kde-unstable repo)
I was also affected by this problem (on Manjaro). The problem started with the updates published the 22/2/2024. I tried to downgrade the packages starting with "k" one by one, but nothing changed. I then downgraded everything else and the problem was fixed. I then tried to upgrade again one by one, but I am now unfortunately unable to reproduce the problem. I can provide the pacman log of that day if needed, but there are more than 300 packages.
The issue disappeared for me after recent updates. Is this still happening for anyone?
The problem did not appear again for me after what I explained above.
I still have this issue, even though i just updated this morning. Tried X11 and wayland, same issue. Tried removing everything in ~/.cache/ from console while starting, before KDE loads, it doesn't fix anything
Your Plasma theme is broken, or else its cache is broken. Did you forget to reboot after upgrade? That can cause issues like this. Based on other comments, it seems like there may also have been a bad update. In any event, not a Plasma bug.