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 689610 - All panels on one screen when using separate x screens
All panels on one screen when using separate x screens
Product: gnome-panel
Classification: Other
Component: panel
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Reported: 2012-12-04 11:41 UTC by Alberts Muktupāvels
Modified: 2013-09-08 21:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Fix panels in separate x screens (1.18 KB, patch)
2012-12-12 19:32 UTC, Alberts Muktupāvels
committed Details | Review

Description Alberts Muktupāvels 2012-12-04 11:41:25 UTC
I'm trying to use separate x screens on nvidia card with 3 monitors. I'm expecting one top panel + one bottom panel on each screen, but instead i have got all panels on one screen.

Restarting gnome panel (gnome-panel --replace) it will create two extra (blank) panel pairs on same screen, but new applets will be added on first panel pair. Screenshot ilustrating problem can be found here -

I tried to manualy set screen key (org->gnome->gnome-panel->layout->toplevels->top-panel->screen) on wich screen panel should appear with dconf Editor. But restarting gnome-panel that key will be reseted.
Comment 1 Alberts Muktupāvels 2012-12-12 19:32:08 UTC
Created attachment 231411 [details] [review]
Fix panels in separate x screens

1) Don't set screen to default screen when it exist. 
2) Set screen for menu, otherwise menu always appears on first screen.
Comment 2 Dmitry Shachnev 2013-04-27 12:05:14 UTC

Jonathan / Josselin, any chance you can commit this?
Comment 3 Jeremy Bicha 2013-05-20 14:56:52 UTC
Attachment 231411 [details] pushed as 3bee9c8 - Fix panels in separate x screens
Comment 4 André Klapper 2013-09-08 21:20:48 UTC
*** Bug 707731 has been marked as a duplicate of this bug. ***