There seem to be a lot of subtle conditions that can trigger this. Let's collect them all here in one place.
Here's one that I notice. X11, Neon, Nvidia prop drivers. I have a few dodge toolbars (bottom and right). If plasmashell crashes (which it does) and restarts, the panels no longer dodge. I _think_ this also happens with hiding behavior. The only workaround I've found is to enter edit mode and then exit (don't have to do anything). Then they dutifully pop down like they are supposed to. I think some of the "strange" behavior I've seen is where plasmashell crashes while I'm away, restarts itself and then the panels are unable to hide again but I can't prove that part.
Please open a new bug report for that and mark it as blocking this one. Thanks.
the icons only task manager is Not auto hiding on the main monitor, but does when the panel is moved to a secondary window.
(In reply to LDWilliams from comment #3) > the icons only task manager is Not auto hiding on the main monitor, but > does when the panel is moved to a secondary window. Please open a new bug report for that and mark it as blocking this one. Also note that if the auto-hide panel is on a shared edge between monitors, auto-hide will only start working on wayland in plasma 6.1, and currently there are no plans to implement this on X11 (see BUG 351175). Thanks!
I have no idea how to do that :(
(In reply to fanzhuyifan from comment #4) > (In reply to LDWilliams from comment #3) > > the icons only task manager is Not auto hiding on the main monitor, but > > does when the panel is moved to a secondary window. > > Please open a new bug report for that and mark it as blocking this one. > Also note that if the auto-hide panel is on a shared edge between monitors, > auto-hide will only start working on wayland in plasma 6.1, and currently > there are no plans to implement this on X11 (see BUG 351175). > Thanks! I have no idea how to do that sorry :(
If you want to report a concrete bug, please don't report it here. Instead, please open a new bug report (after checking that it hasn't been reported). Then, in the new bug report, go to the Blocks field and enter the bug number of this bug (478797). If you don't know how to do that, don't worry, someone will do that for you.