From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1
Description of problem:
I have a laptop with a dual monitor setup. I am using an ATI radeon video card. My xorg configuration is set up to create two separate desktops instead of one wide desktop.
The workspace switcher works fine on the default desktop, however when I try to use the keyboard shortcuts to change workspaces on the external monitor it moves one desktop to the right, and then stops working. I can, however select the workspace manually by clicking on it with the mouse.
The error message says:
Window manager warning: Attempt to perform window operation 24 on window none when operation 24 on none already in effect.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up gnome and xorg for dual monitor, separate desktops
3. CTRL-ALT-RIGHTARROW again (at this point nothing happens, and you can't go back to the first workspace either)
Actual Results: Workspace switcher stops working, except if you click it with your mouse.
Expected Results: Should be able to move between workspaces freely.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thank you in advance.
(this message is mass message)