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 347815 - panels move to wrong monitor after re-docking (multihead)
panels move to wrong monitor after re-docking (multihead)
Status: RESOLVED DUPLICATE of bug 562944
Product: gnome-panel
Classification: Other
Component: general
2.12.x
Other All
: Normal major
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks: randr-tracker
 
 
Reported: 2006-07-17 18:02 UTC by Steve Kelem
Modified: 2009-08-12 13:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Steve Kelem 2006-07-17 18:02:27 UTC
Please describe the problem:
I have a dual-head system when my laptop is docked (to the left of the secondary monitor). I keep the panels on the left side of the laptop. If I boot undocked, then the panels are where they should be, on the left side of the only display, the laptop.  If I reboot docked, then the panels appear on the left side of the monitor instead of the laptop.  This location is in the middle of the combined screen, obscuring the middle of important content. I then have to unlock the panels, drag them over to the left side of the laptop, then re-lock them.

Steps to reproduce:
1. Boot docked.
2. Lock panels to left side of laptop.
3. Reboot undocked.
4. Reboot docked.  The panels move to the secondary monitor.


Actual results:
See above

Expected results:
The panels should stay on the laptop.

Does this happen every time?
Yes

Other information:
Comment 1 Johannes Schmid 2008-08-15 11:41:10 UTC
I can confirm that and I would like to have another option:
=> Resize the panel so it convers both monitors because I don't want to have separate panels on them and when I add new panels and unplug the monitor they do not dissappear but are moved to the first monitor.


=> Major because this sucks badly on xrandr setups (which are quite common these days).
Comment 2 Vincent Untz 2009-08-12 13:44:43 UTC
This is really bug 562944, with a patch.

*** This bug has been marked as a duplicate of 562944 ***