Created attachment 165970 [details] Panels hiding/moving to screen edge when they shouldn't 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. Set up desktop with panels that are floating and/or set to dodge windows 2. open a window on the screen that is small enough that it doesn't touch or come close to either panel OBSERVED RESULT Panels behave as if they are contacting the window- floating panels retreat to edge of screen, dodging panels dodge EXPECTED RESULT panels should be unaffected unless actually touched by a window SOFTWARE/OS VERSIONS 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-18-generic (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Pro WX 3200 Series ADDITIONAL INFORMATION Seems to be a new issue as of an update from the last few days (I didn't have access to the computer for the weekend, so can't be more specific.)
Effects both X11 and Wayland
Cannot reproduce the issue with today's git master.
*** Bug 481638 has been marked as a duplicate of this bug. ***
Marking this as confirmed, since it has been reported by another user.
FWIW I make heavy use of dodge windows panels and I can't reproduce this on masyer build
Does this also happen when you create a new user, and use a default panel? Would any of the reporters be willing to compile a custom version of plasma-workspace including some extra debug prints and report the output? Basically we need to take a look at regionGeometry and windowGeometry reported here: https://invent.kde.org/plasma/plasma-workspace/-/blob/master/libtaskmanager/taskfilterproxymodel.cpp?ref_type=heads#L367 This can also be done using the gdb, by setting a breakpoint and printing these two values.
(In reply to fanzhuyifan from comment #6) > Does this also happen when you create a new user, and use a default panel? > > Would any of the reporters be willing to compile a custom version of > plasma-workspace including some extra debug prints and report the output? > > Basically we need to take a look at regionGeometry and windowGeometry > reported here: > > https://invent.kde.org/plasma/plasma-workspace/-/blob/master/libtaskmanager/ > taskfilterproxymodel.cpp?ref_type=heads#L367 > > This can also be done using the gdb, by setting a breakpoint and printing > these two values. With a new user/default panel, it does not happen. I am willing to try compiling Plasma-workspaces. But am I able? I have set up a KDE development environment before (I've wiped and reinstalled my OS since then and so will have to do it all again), but haven't gone beyond compiling the Kcalc example. Will plasma-workspace be significantly more complex?
(In reply to Doug from comment #7) > I am willing to try compiling Plasma-workspaces. But am I able? I have set > up a KDE development environment before (I've wiped and reinstalled my OS > since then and so will have to do it all again), but haven't gone beyond > compiling the Kcalc example. Will plasma-workspace be significantly more > complex? After you install all the dependencies, it is a simple `kdesrc-build workspace` (https://community.kde.org/Get_Involved/development/Build_software_with_kde-builder) You have to wait quite a while for everything to finish compiling though, so we could try to investigate a bit further before doing that. Or maybe I could write a gdb script that prints those variables when I have time. > With a new user/default panel, it does not happen. Does this only happen when there are certain widgets on the panel? Does this happen with a new user, but when you duplicate the panel setup?
> > With a new user/default panel, it does not happen. > > Does this only happen when there are certain widgets on the panel? Does this > happen with a new user, but when you duplicate the panel setup? Removing the "Peek at Desktop" widget from my bottom dock panel which was set to Dodge Window fixed the issue. Putting the "Peek at Desktop" widget back onto the dock did not cause the issue to recur. I could not replicate the issue on a new user with a similar panel setup.
(In reply to Doug from comment #9) > > > With a new user/default panel, it does not happen. > > > > Does this only happen when there are certain widgets on the panel? Does this > > happen with a new user, but when you duplicate the panel setup? > > Removing the "Peek at Desktop" widget from my bottom dock panel which was > set to Dodge Window fixed the issue. Putting the "Peek at Desktop" widget > back onto the dock did not cause the issue to recur. I could not replicate > the issue on a new user with a similar panel setup. Did you just update from plasma 5? If so might be an issue caused by the migration....
(In reply to fanzhuyifan from comment #10) > (In reply to Doug from comment #9) > > > > With a new user/default panel, it does not happen. > > > > > > Does this only happen when there are certain widgets on the panel? Does this > > > happen with a new user, but when you duplicate the panel setup? > > > > Removing the "Peek at Desktop" widget from my bottom dock panel which was > > set to Dodge Window fixed the issue. Putting the "Peek at Desktop" widget > > back onto the dock did not cause the issue to recur. I could not replicate > > the issue on a new user with a similar panel setup. > > Did you just update from plasma 5? If so might be an issue caused by the > migration.... No, I think I installed at RC2.