Bug 207263

Summary: workspace switching is strange
Product: [Fedora] Fedora Reporter: Bill Nottingham <notting>
Component: compizAssignee: Kristian Høgsberg <krh>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: bnocera, fedora, rvokal
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-25 23:21:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bill Nottingham 2006-09-20 09:47:24 UTC
With compiz-0.0.13-0.27.20060817git.fc6, workspace switching has become strange.

Examples:
1. Workspaces get lost - I can cycle through workspaces seeing some two or three
times before one pops up.
2. When moving windows between workspaces, sometimes the window jumps to the top
or the bottom of the screen.

Comment 1 Bill Nottingham 2006-09-20 09:50:38 UTC
Upon further playing... it may not be that the workspaces are 'lost'; just that
the windows on them disappear.

Comment 2 Søren Sandmann Pedersen 2006-09-20 19:54:15 UTC
Are you using the cube plugin? Ie., do you have "Workspaces on a cube" checked
in the desktop effects dialog?

Comment 3 Bill Nottingham 2006-09-20 20:43:49 UTC
Yes.

Comment 4 Søren Sandmann Pedersen 2006-09-22 22:06:58 UTC
My current understanding of what's going on:

The code in moveScreenViewports() that tries to keep windows on the virtual
screen and move them around to maintain the continuousness of the cube, is
triggering in the Y direction for windows that are close to the edges of the
screen. It is also triggering in the X direction, but usually people have more
than one column, so the windows stay on screen.

The reason the code triggers is that compiz windows have an extra 'output' area
containing the shadow etc.

I'm not yet sure how to fix this.


Comment 5 Søren Sandmann Pedersen 2006-09-25 23:03:05 UTC
Fixed in the build that is currently underway (-28).

Comment 6 Søren Sandmann Pedersen 2006-09-25 23:21:42 UTC
which failed, but fortunately a new identical build finished successfully.

Comment 7 Thorsten Leemhuis 2006-09-26 11:59:58 UTC
*** Bug 207128 has been marked as a duplicate of this bug. ***