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 646853 - gnome-shell doesn't play nice with multi screen setups
gnome-shell doesn't play nice with multi screen setups
Status: RESOLVED DUPLICATE of bug 636963
Product: gnome-shell
Classification: Core
Component: general
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-04-05 19:39 UTC by leomcardle
Modified: 2011-04-05 19:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of #1 (900.34 KB, image/png)
2011-04-05 19:39 UTC, leomcardle
Details
Screenshot of #2 (182.98 KB, image/png)
2011-04-05 19:40 UTC, leomcardle
Details

Description leomcardle 2011-04-05 19:39:32 UTC
Created attachment 185228 [details]
Screenshot of #1

3 problems:

1) if one has two screens set up with one on top of the other and one puts the gnome shell on the bottom of the two screens it's only possible to move a window onto the top screen by holding down alt and dragging, even then it's not possible to maximise the window on the top screen and about 200px of the window stays on the bottom screen

2) if one has the dual screen setup described above, but with the gnome shell on the top screen, the black gradient of the notification area (at the bottom) appears at the top of the bottom screen only to slide up onto the top screen when one hits the bottom of the top screen with pinpoint precision

3) only the screen that has the gnome shell on it 'does' workspaces, e.g. when I press Ctrl + Alt + Down it only changes the workspace on the screen on which the gnome shell is

(see attachments)
Comment 1 leomcardle 2011-04-05 19:40:23 UTC
Created attachment 185229 [details]
Screenshot of #2
Comment 2 Owen Taylor 2011-04-05 19:41:57 UTC
1, 2 are covered by bug b
3 is intentional - see bug 609258

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