Pips show incorrect status after attaching or detatching second screen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) | ||
unity (Ubuntu) |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) |
Bug Description
Intel based laptop in docking bay. Two screens connected and enabled. Some applications spread over both screens.
Detach the second screen (in my case, pull the laptop out of the docking bay).
Notice that the pips show empty triangles as if the applications are on another workspace when in fact they're on workspace 1 (current)
Move to another (empty) workspace and back, and note the triangles fill back in.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.12+bzr2384ubu
ProcVersionSign
Uname: Linux 3.2.0-26-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
CompizPlugins: [core,composite
CrashDB: unity
Date: Thu Jul 12 22:19:06 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- PS Jenkins bot (community): Approve (continuous-integration)
- Brandon Schaefer (community): Approve
-
Diff: 19 lines (+2/-0)1 file modifiedlauncher/ApplicationLauncherIcon.cpp (+2/-0)
summary: |
- Pips show incorrect status after detatching second screen + Pips show incorrect status after attaching or detatching second screen |
Changed in unity: | |
milestone: | 5.14.0 → 5.16.0 |
Changed in unity: | |
milestone: | 5.16.0 → 5.18.0 |
Changed in unity: | |
milestone: | 5.18.0 → 5.20.0 |
Changed in unity: | |
milestone: | 5.20.0 → 5.22.0 |
Changed in unity: | |
milestone: | 5.22.0 → 5.24.0 |
Changed in unity: | |
milestone: | 5.24.0 → 7.2.1 |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
Changed in unity (Ubuntu): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
status: | Confirmed → In Progress |
Changed in unity: | |
status: | Confirmed → In Progress |
Changed in unity: | |
milestone: | 7.2.1 → 7.2.2 |
Changed in unity: | |
milestone: | 7.2.2 → 7.2.3 |
Changed in unity: | |
milestone: | 7.2.3 → 7.3.1 |
no longer affects: | unity/7.2 |
Changed in unity: | |
status: | In Progress → Fix Released |
milestone: | 7.3.1 → none |
Changed in unity: | |
milestone: | none → 7.2.0 |
I tried this with one of my laptops, and this doesn't seem to happen on the current version in precise-updates (5.12-0ubuntu1.1). So it's a problem with trunk it seems.