Bug 697424 - Second screen ignored when switching workspaces
Summary: Second screen ignored when switching workspaces
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-18 08:31 UTC by Tomasz Torcz
Modified: 2011-04-18 15:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-18 15:44:31 UTC
Type: ---


Attachments (Terms of Use)

Description Tomasz Torcz 2011-04-18 08:31:28 UTC
Description of problem:
I am using dual screen workspace. On the left I have main screen in landscape orientation. On the right second screen, with portrait orientation.

When I move a window to second screen, it stays there when I switch workspaces. I do not have "Occupy all workspaces" enabled for that window. When I move window back to the left screen, switching workspace cause window to properly disappear (leave on workspace it was put to).

Version-Release number of selected component (if applicable):
gnome-shell-3.0.0.2-2.fc15.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Use a dual screen layout
2. Move window to secondary screen
3. Switch to new workspace.
  
Actual results:
Window on the secondary screen is moved to new workspace.

Expected results:
Windows should stay on workspace it was opened on.

Additional info:
This behaviour effectively reduces dual screen layout to single screen with dangling workspace.

Comment 1 Owen Taylor 2011-04-18 15:44:31 UTC
This is working as expected, see, for the design:

 https://bugzilla.gnome.org/show_bug.cgi?id=609258

The upstream bug:

 https://bugzilla.gnome.org/show_bug.cgi?id=645581

Covers the possibility of adding some sort of configurable mode for people who want workspaces to cover both desktops.


Note You need to log in before you can comment on or make changes to this bug.