Created attachment 7302 panel config I am making a new bug to not spam bug 9338 with issues that are barely related. Panel 4.13.1: The situation has not improved, on the contrary, I feel like the panel goes bonkers when the number or names of outputs changes during the day. - If the panel starts with only LVDS available: There's a roughly 4x4 pixels "thing" in the upper left corner. It seems the panels that don't have anywhere to go get bunched up here. - It also is possible that a panel with nowhere to go sits on the primary output instead, fighting with the primary panel for which one stays in the foreground - When the number of monitors changes, a panel may appear on a monitor correctly but fail to autohide despite it being enabled In general, the panel seems to have a lot of trouble when outputs defined for a panel do not exist. This, along with bug 10725, makes xfce4-panel a bit of a nightmare to deal with on multimonitor systems that are on the move. I've attached my panel config.
Could this be a duplicate of https://bugzilla.xfce.org/show_bug.cgi?id=13620 ?
(In reply to Simon Steinbeiss from comment #1) > Could this be a duplicate of https://bugzilla.xfce.org/show_bug.cgi?id=13620 > ? I don't think so, although I've also seen bug 13620 in action.
Right now, out of 3 active monitors (LVDS1, VIRTUAL7=primary, VIRTUAL8), only VIRTUAL7 and VIRTUAL8 have their correct panels. The LVDS1 panel is missing. What's very interesting, going into the panel settings I see that each panel is set to the Primary output, which is incorrect. According to the Settings Editor, the panels are set to appear on LVDS1, Primary and VIRTUAL8 respectively. This discrepancy warrants further investigation, as it's likely to be a contributing factor to this bug.
I think this may have been fixed already by https://git.xfce.org/xfce/xfce4-panel/commit/?id=81bc29e40dc74d1a3dfbb274d63245f292dd3398 Could you give 4.13.3 a try?
To be honest issues like this one make me consider to drop the binding of panels to individual outputs. It's just too error-prone if outputs are disconnected frequently... (The primary setting should help in many/most cases.)
Sorry for the radio silence, I've been dealing with another problem that amplified panel bugs, which is now solved. Currently I am using Panel 4.13.4 and it seems to be working rather well. At least I haven't spotted any major issues anymore. Panels appear on the output they should and stay there. (In reply to Simon Steinbeiss from comment #5) > To be honest issues like this one make me consider to drop the binding of > panels to individual outputs. It's just too error-prone if outputs are > disconnected frequently... I don't think that's a good idea. I fear this will only results in panels flying around outputs at pretty much random.
(In reply to haarp from comment #6) > Currently I am using Panel 4.13.4 and it seems to be working rather well. At > least I haven't spotted any major issues anymore. Panels appear on the > output they should and stay there. Great, marking the bug as fixed then.