[spread] Corruption when switching workspaces after windows have been moved to other workspaces
Bug #760787 reported by
Ugo Riboni
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unity-2d |
Fix Released
|
Critical
|
Ugo Riboni | ||
| unity-2d (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When switching workspaces with the spread, the windows appear corrupted after the spread disappears.
An example of the corruption can be seen in the screenshot attached.
I can reproduce consistently this way:
- Open two windows on workspace 1, make them not maximized and overlapping
- Right click on their titlebars and select "move to workspace right" from the menu
- Press Super+s or click on the workspaces button in the launcher
- When the workspaces switcher comes up, select workspace 2 and then click on one of the windows on it
At this point the current workspace becomes workspace 2, and the windows displayed there appear corrupt.
Moving the windows around will clear the corruption by forcing them to repaint.
Revision history for this message
| Ugo Riboni (uriboni) wrote | #1 |
| Changed in unity-2d: | |
| assignee: | nobody → Ugo Riboni (uriboni) |
| milestone: | none → 3.8.4 |
| importance: | Undecided → Critical |
Revision history for this message
| Ugo Riboni (uriboni) wrote | #2 |
| Changed in unity-2d: | |
| status: | New → Confirmed |
| Changed in unity-2d: | |
| milestone: | 3.8.4 → 3.10 |
| Changed in unity-2d: | |
| status: | Confirmed → Fix Committed |
| Changed in unity-2d (Ubuntu): | |
| status: | New → Fix Committed |
| Changed in unity-2d: | |
| milestone: | 3.10 → 3.8.8 |
| Changed in unity-2d: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in unity-2d (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The problem in this bug was formerly tracked as part of bug 740387 but it was split since this issue is specific to unity-2d while the other bug was specific to the classic gnome session.