! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Panel sometimes won't reserve space after switching monitors
Status:
RESOLVED: MOVED

Comments

Description haarp 2018-08-24 20:06:37 CEST
Due to having a laptop, I often switch monitor layouts and enable/disable output. My panel is a simple horizontal one at the bottom with 100% width and set to remain on the Primary output. "Don't reserve space on borders" is disabled, e.g. it should reserve space.

When switching back to a one-monitor layout (laptop-only), with only one output connected and enabled, it often happens that the panel breaks. It will not reserve space around it anymore, causing maximized windows to extend behind the panel. Toggling "Don't reserve space on borders" does not fix the problem, neither does restarting the panel, or Xfwm4.

At this point I'm not sure which component is responsible for this bug.
Comment 1 haarp 2018-09-21 21:52:08 CEST
Curious. once this bug appears, I can move the panel from the bottom to the top, and it WILL correctly reserve space there! When I move it to the bottom again, it still fails to do so.
Comment 2 haarp 2018-09-24 22:47:01 CEST
I have figured it out. This is a Xfwm4 bug.

Reproduction:

1) Have a panel at the bottom set to remain on the Primary output and to reserve space on borders
2) Have one output active where the panel resides on, e.g. 1920x1080
3) Set the framebuffer size larger than this output, e.g. xrandr --fb 1920x1440
4) Restart Xfwm4

Bug: Xfwm4 assumes 1440 to be the bottom of the display. It should use the output size instead, which still is 1080.

5) Reduce the framebuffer size back to actual output size: xrandr --fb 1920x1080

Bug: Xfwm4 does not notice this change, and is stuck at 1440 until restarted.
Comment 3 haarp 2018-09-24 22:49:27 CEST
ccing relevant developer
Comment 4 Git Bot editbugs 2020-05-29 12:22:15 CEST
-- GitLab Migration Automatic Message --

This bug has been migrated to xfce.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.xfce.org/xfce/xfwm4/-/issues/298.

Please create an account or use an existing account on one of our supported OAuth providers. 

If you want to fork to submit patches and merge requests please continue reading here: https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests

Also feel free to reach out to us on the mailing list https://mail.xfce.org/mailman/listinfo/xfce4-dev

Bug #14630

Reported by:
haarp
Reported on: 2018-08-24
Last modified on: 2020-05-29

People

Assignee:
Nick Schermer
CC List:
1 user

Version

Version:
4.13.1

Attachments

Additional information