Passing program windows across workspaces works in reverse

[Christopher Grey]

Setup:
Ubuntu 13.04 (32bit) setup for multiple workspaces (4).
ATI Video Card

Note, workspaces are disabled by default in Raring. To enable, go to Appearance and click the checkbox to "Enable Workspaces."

With workspaces, you generally pass windows between workspaces by right-clicking the window's title bar and use the right-click menu to move windows between workspaces. However you apparently can also manually move windows across workspaces just by sliding a non-maximized windows across to adjacent workspaces. However the direction you must pass a window is backwards from the navigation direction as viewed when using CTRL-ALT-ArrowKeys.

So for example, I have the standard 4 workspace setup in the standard checkerboard formation when viewing the "popup" while navigating between workspaces using CTRL-ALT-ArrowKeys.

1 | 2
------
3 | 4

If I'm in Workspace 1 (as displayed above), I would expect to be able to move a window to the right to slide it over to Workspace 2. However what I'm finding is, I move it to the left on Workspace 1. I move it such that some of the window is off-view in Workspace 1. When I navigate to Workspace 2 (CTRL-ALT-RightArrow), I see the other portion of the window on the right side.

Moving windows downward appears to work as expected. Thus it seems one portion of the Unity UI views the workspaces as:
2 | 1
------
4 | 3

You can see this by taking a window in Workspace 1, and sliding it both to the Left and Bottom of Workspace 1 so that a portion of the window exists in all 4 workspaces. Now navigate through all 4 workspaces, and you'll see what I mean.

I don't have a camera to take a picture of what I'm seeing, but if need, I can certainly do that.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1224541/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Paul White (paulw2u)]

Christopher,

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Presumably this problem was a one time occurrence and/or is no longer an issue? Can this bug report now be closed?

If we do not hear from you the bug report will close itself in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

[Christopher Grey (cgrey)]

This was still an issue in Ubuntu 14.04 (32-bit) as far as I can remember. However I've moved on to Ubuntu 16.04 (64-bit) and this is no longer an issue on this version.

From my standpoint, this has been fixed. What I don't know is when, exactly, this got fixed, or if the fix had anything to do with me transferring from 32-bit to 64-bit. For example, I can't say if Ubuntu 16.04 (32bit) will duplicate this problem. But given the push toward 64-bit operating systems in the desktop/server realm, I'm actually amazed Ubuntu maintains a 32-bit version.

[Paul White (paulw2u)]

Thanks for your reply Christopher.

As the issue was never confirmed I'll close this by marking as "Invalid".