Window management - When a monitor is disconnected, the windows do not move to the remaining monitor and the Launcher pips do not update
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ayatana Design |
Fix Released
|
Critical
|
John Lea | ||
| Compiz |
Fix Released
|
High
|
Brandon Schaefer | ||
| 0.9.8 |
Won't Fix
|
Medium
|
Unassigned | ||
| Compiz Core |
Triaged
|
Medium
|
Unassigned | ||
| compiz (Ubuntu) |
Fix Released
|
High
|
Brandon Schaefer | ||
Bug Description
When a monitor is disconnected in a multi-monitor environment, the Launcher pips do not update
Steps to reproduce, example 1:
1. Open two GEdit window on one monitor (using a computer with two monitors)
2. Disconnect the monitor the two windows are on, and press "Detect Displays" in 'Settings/Displays'
Current incorrect behaviour: The Launcher on the remaining monitor continues to display the hollow triangle next to the GEdit icon, and the two windows are not moved on to the remaining monitor.
What should happen: The Launcher on the remaining monitor should display two pips next to the GEdit icon, and the windows should be moved on to the remaining monitor.
Steps to reproduce, example 2:
1. Open one GEdit window on each monitor (using a computer with two monitors)
2. Disconnect one of the two monitors, and press "Detect Displays" in 'Settings/Displays'
Current incorrect behaviour: The Launcher on the remaining monitor continues to display only one pip next to the GEdit icon. Clicking on the GEdit icon does not spread the window that was one the other monitor, it is as if it has disappeared! (but it has incorrectly been moved to a different workspace).
What should happen: The Launcher on the remaining monitor should display two pips next to the GEdit icon, and the window on the disconnected monitor should be moved on to the remaining monitor.
Related branches
- Daniel van Vugt: Needs Information
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 13 lines (+2/-1)1 file modifiedplugins/place/src/place.cpp (+2/-1)
- Stephen M. Webb: Approve
- Sam Spilsbury: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 18 lines (+8/-0)1 file modifiedplugins/place/src/place.cpp (+8/-0)
| tags: | added: udp |
| Changed in ayatana-design: | |
| assignee: | nobody → John Lea (johnlea) |
| importance: | Undecided → Critical |
| Changed in unity: | |
| milestone: | none → backlog |
| Changed in ayatana-design: | |
| status: | New → Triaged |
| Changed in unity: | |
| status: | New → Triaged |
| Changed in unity (Ubuntu): | |
| status: | New → Triaged |
| summary: |
- multimonitor, window management - When a monitor is disconnected, the - Launcher pips do not update + multimonitor, window management - When one monitor is disconnected in + multi-monitor environment, the windows to not move to the remaining + monitor and the Launcher pips do not update |
| tags: | added: multimonitor |
| Changed in compiz: | |
| status: | New → Confirmed |
| milestone: | none → 0.9.8.0 |
| Daniel van Vugt (vanvugt) wrote Re: When a monitor is disconnected, the windows do not move to the remaining monitor and the Launcher pips do not update | #2 |
| summary: |
- multimonitor, window management - When one monitor is disconnected in - multi-monitor environment, the windows to not move to the remaining + When a monitor is disconnected, the windows do not move to the remaining monitor and the Launcher pips do not update |
| Changed in ayatana-design: | |
| status: | Triaged → Fix Committed |
| Changed in unity: | |
| importance: | Undecided → High |
| Changed in compiz: | |
| importance: | Undecided → High |
| Changed in compiz: | |
| milestone: | 0.9.8.0 → 0.9.8.1 |
| summary: |
- When a monitor is disconnected, the windows do not move to the remaining - monitor and the Launcher pips do not update + Window management - When a monitor is disconnected, the windows do not + move to the remaining monitor and the Launcher pips do not update |
| Changed in unity (Ubuntu): | |
| importance: | Undecided → High |
| Changed in compiz (Ubuntu): | |
| importance: | Undecided → High |
| no longer affects: | unity (Ubuntu) |
| Changed in unity: | |
| status: | Triaged → Confirmed |
| Changed in compiz (Ubuntu): | |
| status: | New → Confirmed |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in unity (Ubuntu): | |
| status: | New → Confirmed |
| Changed in compiz: | |
| milestone: | 0.9.8.2 → 0.9.8.4 |
| Changed in unity: | |
| milestone: | backlog → none |
| tags: | added: exbacklog |
| Changed in compiz: | |
| milestone: | 0.9.8.4 → 0.9.9.0 |
| Changed in compiz: | |
| status: | Confirmed → Triaged |
| Changed in unity: | |
| status: | Confirmed → Triaged |
| Changed in unity (Ubuntu): | |
| status: | Confirmed → Triaged |
| Changed in compiz (Ubuntu): | |
| status: | Confirmed → Triaged |
| Changed in unity (Ubuntu): | |
| importance: | Undecided → High |
| Changed in compiz: | |
| assignee: | nobody → Brandon Schaefer (brandontschaefer) |
| Changed in compiz (Ubuntu): | |
| assignee: | nobody → Brandon Schaefer (brandontschaefer) |
| Changed in compiz (Ubuntu): | |
| status: | Triaged → In Progress |
| Changed in compiz: | |
| status: | Triaged → In Progress |
| Changed in unity: | |
| status: | Triaged → Invalid |
| Changed in unity (Ubuntu): | |
| status: | Triaged → Invalid |
| no longer affects: | unity |
| no longer affects: | unity (Ubuntu) |
| Changed in compiz: | |
| status: | In Progress → Fix Committed |
| Changed in compiz (Ubuntu): | |
| status: | In Progress → Fix Committed |
| Changed in compiz-core: | |
| milestone: | none → 0.9.7.14 |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in compiz (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Changed in compiz: | |
| status: | Fix Committed → Fix Released |
| Changed in ayatana-design: | |
| status: | Fix Committed → Fix Released |
I believe this is a duplicate and/or fixed upstream already anyway. Just can't find the other bug right now.