Description of Problem:
When selecting "Send window to" -> "[Previous|Next] Workspace" (topleft
corner menu) when in the [first|last] workspace, a new (in my case fifth)
workspace is created, which extends the applet in the panel to 5
workspaces. The new workspace seems impossible to remove without logging
out and starting a new session, even when entering the configuration and
selecting 4 workspaces.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start gdm
2. Log in
3. Bring up a window
4. Select "Send Window to"->"Previous workspace"
New workspace created as described above
Windows sent to last workspace ("wrapping around" to the last)
It also pushes the clock to the left, such that the least significant digit of
the munites is not visible.
This is a configuration option. Open the Sawfish capplet and go to the Desktops
section. There you can select whether to stop/cycle/continue when going past
the last workspace. You have "continue" set; select "cycle" for the behavior
Also, you *can* remove workspaces. It works fine for me by resetting them in
the capplet. However, the capplet does not seem to notice when you add a
workspace by moving a window to another workspace in the "continue" mode
Havoc, I guess we can mark this as notabug.
I don't think autocreate should be our default setting. "stop" is the right
I upgraded to the new sawfish-1.0.1-1 (RawHide) and found this option (which is
found in the "Workspaces" capplet). Note that "Meta" -> "Options for" has to be
set to "expert users" for this option to be present. Thus the correct resolution
marking might be "RawHide". I don't think the option was present in my
sawfish-0.38-11, although I am not sure, as a downgrade I did to check it
corrupted my sawfish capplets. It could be that I never turned on the "expert"
options at the same time as checking the "Workspaces" capplet.
In conclusion, the bug can be closed, marked as "RawHide" if sawfish-1.0.1-1 is
needed, or "Notabug" if not.
I think the default should be "wrap-around" or "stop" for both settings.
1.0.1-5 should disable this by default, though for people who've touched the
setting it may remain enabled of course.