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 626832 - Desktop switcher - change settings to 18 virtual desktops corrupts the desktop
Desktop switcher - change settings to 18 virtual desktops corrupts the desktop
Status: RESOLVED DUPLICATE of bug 625781
Product: gnome-panel
Classification: Other
Component: panel
2.30.x
Other Linux
: Normal major
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-13 13:28 UTC by Hans-Peter Sorge
Modified: 2010-09-23 08:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Hans-Peter Sorge 2010-08-13 13:28:15 UTC 
Problem encountered with Fedora 13.

Changing the switcher settings to 18 virtual desktops will corrupt the desktop
after logoff / logon.

The desktop switcher settings can not be fully accessed any more after login. 
Only the number of lines setting continues to work.

Other windows loose frame and title bar and are pinned to the upper left corner
and can't be moved freely. 

Users "tricked" into changing the number of virtual desktops to 18 and more
might experience this problem as denial of service.

I migrated from F12 to F13 using the F12-HOME dir. 
After quite some while I did a logoff/logon with above nasty side effect.

To fix the actual situation I changed num_workspaces in
/home/joy/.gconf/apps/metacity/general/%gconf.xml
to
<entry name="num_workspaces" mtime="1266018720" type="int" value="16"/>

The problem can be repeated on Fedora 13 with a newly added user and
just changing the desktop-switcher settings to 18 virtual desktops.
Comment 1 Danilo Segan 2010-09-23 08:31:31 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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