After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 513685 - Panel sized to wrong monitor in dual-head xrandr configuration
Panel sized to wrong monitor in dual-head xrandr configuration
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: general
2.20.x
Other All
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-01 13:05 UTC by Klaasjan Brand
Modified: 2020-11-06 20:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Klaasjan Brand 2008-02-01 13:05:08 UTC
Please describe the problem:
When attaching a second monitor using an xrandr configuration the panel on the primary head is resized to fit on a screen the size of the secondary head.
This means that on a 1600x1200 screen the panel shrinks to a quarter screen when attaching an 800x600 monitor - while remaining on the 1600x1200 screen.

This problem leads to another bug: when attaching a lower-resolution screen there's a big "dead zone" on the primary screen which isn't covered by desktop anymore. Doing anything (like dragging an icon there) seems to hang nautilus or the desktop ocasionally.

Another case is some drivers report "ghost" monitors with a bogus resolution, which also leads to the same problem. 

I haven't tested what happens when attaching a higher-resolution secondary monitor.

Steps to reproduce:
1. Start up Gnome on randr enabled system
2. Attach second monitor with lower resolution
3. Enable monitor with xrandr

Actual results:
Second monitor is initialized. Panel on first screen is resized.

Expected results:
I wouldn't expect the panel to resize or move at all.

Does this happen every time?
Yes.

Other information:
Maybe this is a bug in a lower level library (like gtk/gdk).

I've seen this in two cases on different videocards (r300 and intel). In both cases, xrandr -q lists the second head first which could confuse something.
Comment 1 André Klapper 2020-11-06 20:21:51 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.