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 147449 - After switching resolution (RANDR), workspace switcher shows incorrect desktop size
After switching resolution (RANDR), workspace switcher shows incorrect deskto...
Status: RESOLVED DUPLICATE of bug 114690
Product: gnome-panel
Classification: Other
Component: workspace switcher
2.6.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-07-12 21:19 UTC by Ilkka Tuohela
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Ilkka Tuohela 2004-07-12 21:19:40 UTC
Workspace switcher clips desktops to wrong size after changing desktop size
with gnome-display-properties and new login:

- Set display size to something different with gnome-display-properties (for 
example, 800x600)
- Logoff and login
- Set display size to normal (for example, 1400x1050 in my case)
- The switcher does not use the new size, but clips desktop size to 800x600, 
  even after restarting the panel and applet (did not try logout)

Symptoms after the size change:
- Old desktop size is used in workspace switcher
- If a window is moved outside the old workspace size (to coordinates like 
  900x200 in above example), workspace switcher renders totally incorrect page
- Restarting panel does not help, I don't know where this size is received from

To see examples of this bug, see directory http://hile.dyndns.org/panel-bug/.
- before.png shows how the window on 5th desktop is on the edge of switcher  
  window, but in reality it fills half of the desktop.
- after.png shows how the whole switcher is garbled, when the window is moved 
  'out' from it's display area.
Comment 1 Vincent Untz 2004-08-03 11:23:35 UTC
Thanks for the report. This is a known bug.

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