Created attachment 163514 [details] Additional indicator when Peek at Desktop is enabled SUMMARY There's an indicator line on top of app icons (and the Kickoff icon) on the panel when Peek at Desktop is active. Check the attached video. STEPS TO REPRODUCE 1. Have open applications 2. Enable Peek at Desktop 3. Hover over app icons on the panel OBSERVED RESULT There's an additional indicator that wasn't present on 5.27 EXPECTED RESULT No indicator SOFTWARE/OS VERSIONS KDE Plasma Version: 5.85.0 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0
PS: This also happens with a non-floating panel.
Can reproduce.
This seems to be the panel focus thingy? Looking into it
*** Bug 477894 has been marked as a duplicate of this bug. ***
A possibly relevant merge request was started @ https://invent.kde.org/plasma/libplasma/-/merge_requests/1036
Git commit 4b32a23fd87ffc878e2b37559eed09cae039f8f3 by Nate Graham, on behalf of Niccolò Venerandi. Committed on 23/01/2024 at 16:33. Pushed by ngraham into branch 'master'. Set Panel to NeedsAttentionstatus when one of its applets is activated The idea is that NeedsAttentionStatus prevents the panel from gaining keyboard input focus unnecessarily, which would result in an extra blue line. FIXED-IN: 6.0 M +4 -1 src/plasma/containment.cpp M +0 -5 src/plasmaquick/plasmoid/plasmoiditem.cpp https://invent.kde.org/plasma/libplasma/-/commit/4b32a23fd87ffc878e2b37559eed09cae039f8f3
*** Bug 480836 has been marked as a duplicate of this bug. ***
*** Bug 483555 has been marked as a duplicate of this bug. ***
My report has been marked as a dup. I still experience it in 6.0.1 + the indicator has a gap to the panel when the panel is floating.
I can confirm that the bug is still there on 6.0.2 on arch.
The bug did get fixed, but then later regressed for other reasons. It was fixed again in Bug 479084.
(In reply to Nate Graham from comment #11) > The bug did get fixed, but then later regressed for other reasons. It was > fixed again in Bug 479084. It's says: FIXED-IN: 6.0.2 But people facing this bug in 6.0.2?
Then something else is going on. The issue described there is fixed for me, so *something*'s fixed. :) Maybe people still affected are using X11 and it's only fixed on Wayland. Maybe their distro mis-packaged things. Could be any number of other things. We'll need more information in there to proceed.
I still(In reply to Nate Graham from comment #13) > Then something else is going on. The issue described there is fixed for me, > so *something*'s fixed. :) >Maybe people still affected are using X11 and > it's only fixed on Wayland. It's also not fixed for me on openSUSE TW + Plasma 6.0.2 using the Wayland session. > Maybe their distro mis-packaged things. Could be > any number of other things. We'll need more information in there to proceed. Now the issue obviously persists on both Arch and openSUSE TW. Either both distros have a packaging problem or maybe your system has some other patch applied, which has not official been rolled out yet?
(In reply to postix from comment #14) > I still(In reply to Nate Graham from comment #13) > Now the issue obviously persists on both Arch and openSUSE TW. Either both > distros have a packaging problem... I can reproduce it on Neon User Edition using a Wayland session, so that doesn't seem to be the case.
Created attachment 167341 [details] Screenshot on TW 6.0.2: Double highlight Actually I managed to get two highlights: 1) Open Kickoff 2) Click on Peak to desktop (Kickoff closes then) 3) Open Kickoff again 4) Click on Peak to desktop The second highlight floats above the panel and is also visible for the icon only task manager on hover.
Are people reproducing the original issue *exactly* as described in comment 0? If not, it's a different issue, and we should be a new bug report about it.
(In reply to Nate Graham from comment #17) > Are people reproducing the original issue *exactly* as described in comment > 0? If not, it's a different issue, and we should be a new bug report about > it. I'm reproducing the exact same issue
Ok, please attach a screen recording so I can see how you're doing it and attempt to replicate that. Also, are you reproducing it on X11, or Wayland, or both?
(In reply to Nate Graham from comment #19) > Ok, please attach a screen recording so I can see how you're doing it and > attempt to replicate that. > > Also, are you reproducing it on X11, or Wayland, or both? I can't upload a new screen record because I'm outside now, but there is a screen recording in the bug: https://bugs.kde.org/show_bug.cgi?id=477894 (the exact same steps)
(In reply to Nate Graham from comment #19) > Ok, please attach a screen recording so I can see how you're doing it and > attempt to replicate that. > > Also, are you reproducing it on X11, or Wayland, or both? And I can reproduce them in x11 and Wayland both
Edip, what's in Bug 477894 isn't helpful since that was from months ago. I need a screen recording from today, on a system verified to be using Plasma 6.0.2.
Created attachment 167420 [details] Video : Bug is still here in Plasma 6.0.2 The bug on Plasma 6.0.2 on arch using Wayland
Thanks. As I had suspected, that's a different issue from the one described and fixed here. I can reproduce it too, but it's not the same thing. Please submit a new bug report about it.
(In reply to Nate Graham from comment #24) > Thanks. As I had suspected, that's a different issue from the one described > and fixed here. I can reproduce it too, but it's not the same thing. Please > submit a new bug report about it. Is the bug seen in the video i've sent the same as this one ? https://bugs.kde.org/show_bug.cgi?id=480836
Created attachment 167423 [details] Screen recording: Plasma 6.0.2 Wayland on openSUSE TW @Nate, this seems pretty much the same as shown in the OT, which I experience with 6.0.2 on Wayland with a newly created user account. Also please check second 10 and later, there are two indicators for kickoff.
(In reply to Nate Graham from comment #24) > Thanks. As I had suspected, that's a different issue from the one described > and fixed here. I can reproduce it too, but it's not the same thing. Please > submit a new bug report about it. im sure that is the same issue but as u want, i created a new Bug 483928
(In reply to postix from comment #26) > Created attachment 167423 [details] > Screen recording: Plasma 6.0.2 Wayland on openSUSE TW > > @Nate, this seems pretty much the same as shown in the OT, which I > experience with 6.0.2 on Wayland with a newly created user account. Also > please check second 10 and later, there are two indicators for kickoff. Thanks. The screen recording depicts the exact issue that was fixed in Bug 479084. Exactly. So I suspect there may be a packaging issue in the distro; maybe that commit got patched out or broken or something. One other option I can think of is that maybe the fix for that bug doesn't work unless https://invent.kde.org/plasma/libplasma/-/commit/988161d805526a527bf96a94af066757774c552b is also applied, but that hasn't been rolled out to users yet since it's scheduled for release in Frameworks 6.1. If so, that would explain how all the developers (who build everything from git master) think it's fixed. Let me investigate that.
Hmm, nope, still works fine for me with that commit locally reverted. Also, I was wrong about one thing: that commit is not in a framework since libplasma was moved to the plasma release schedule. Gotta get used to this!
Since we're getting multiple reports of the problem still happening, I've re-opened the most recent bug report about it, which is Bug 479084. Let's let this one stay closed as it was fixing and earlier manifestation of the issue, and use Bug 479084 as the master bug report for all new reports of it still happening. Thanks for your patience, folks.