[launcher] icons no longer active after an incomplete drag
Bug #768812 reported by
Jani Monoses
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-2d |
Fix Released
|
Critical
|
Florian Boucault | ||
unity-2d (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: unity-2d
While trying to click on the thunderbird icon in the sidebar I manged to click and drag it a bit upwards, so it moved up and covered part of the icon above (xchat).
Now all icons on the sidebar are unresponsive to clicks.
Related branches
lp:~fboucault/unity-2d/launcher_interrupted_drag
- Olivier Tilloy (community): Needs Fixing
- Pi Delport (community): Approve
-
Diff: 18 lines (+8/-0)1 file modifiedlauncher/ListViewDragAndDrop.qml (+8/-0)
Changed in unity-2d (Ubuntu): | |
status: | Incomplete → New |
summary: |
- sidebar icons no longer active + [launcher] icons no longer active after an incomplete drag |
Changed in unity-2d: | |
importance: | Undecided → High |
Changed in unity-2d: | |
status: | New → Confirmed |
Changed in unity-2d (Ubuntu): | |
status: | New → Confirmed |
summary: |
- [launcher] icons no longer active after an incomplete drag + [launcher] icons no longer active after an incomplete drag (no reliable + way to reproduce yet) |
Changed in unity-2d: | |
importance: | High → Critical |
milestone: | none → 3.10 |
Changed in unity-2d: | |
assignee: | nobody → Florian Boucault (fboucault) |
status: | Confirmed → In Progress |
Changed in unity-2d (Ubuntu): | |
status: | Confirmed → In Progress |
summary: |
- [launcher] icons no longer active after an incomplete drag (no reliable - way to reproduce yet) + [launcher] icons no longer active after an incomplete drag |
Changed in unity-2d: | |
status: | In Progress → Fix Committed |
Changed in unity-2d (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in unity-2d: | |
milestone: | 3.10 → 3.8.8 |
Changed in unity-2d: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
@Jani: this looks like a pretty bad issue. Do you have a way to reliably reproduce it?