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 122205 - Random Window Positioning with Gnome's Workspace Switcher.
Random Window Positioning with Gnome's Workspace Switcher.
Status: RESOLVED FIXED
Product: Sawfish
Classification: Deprecated
Component: Window Manager
pre-1.3.x
Other Linux
: Normal major
: 1.5.x
Assigned To: John Harper
sawfish QA Team
Depends on:
Blocks:
 
 
Reported: 2003-09-13 14:04 UTC by chendo
Modified: 2009-08-16 15:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4


Description chendo 2003-09-13 14:04:34 UTC 
Using offical Gnome 2.4 ebuild.
Sawfish 1.3

When switching workspaces, windows randomly reposition themselves offscreen.

It seems that sawfish loses it's sense of where is 0,0 on the screen, or
gnome is not telling sawfish where 0,0 is. 

As this didn't happen in Gnome 2.2, and it happened to a new user, it's not
my config files or sawfish.
Comment 1 PhaseBurn 2003-09-16 07:39:37 UTC 
I also have this same problem, and have noticed that clicking on the 
same workspace, if I hit an application window inside the switcher, also 
causes the windows to shuffle location. 
 
Steps I've taken to remedy this (unsucessfully) have been to recompile 
librep, rep-gtk, and sawfish against the new GTK and gnome libs, 
however that still is not working for me.
Comment 2 Christian Krause 2003-09-16 22:50:23 UTC 
This bug is related to bug #122086. If I remove in libwnck: src/pager.c:
wnck_pager_button_release the call to wnck_screen_move_viewport (as
suggested in the other bug), no windows are shuffled.

But I don't know if this is really a bug of libwnck or of sawfish.
Comment 3 PhaseBurn 2003-09-17 16:08:51 UTC 
Yes, after commenting out that line in libwnck's pager.c file and 
recompiling, my windows and pager applet behaved as expected.
Comment 4 Marinus Schraal 2004-05-04 14:05:23 UTC 
bug #122086 got fixed, so that means that this bug got fixed & can be closed afaics.