[launcher] Identical desktop files in two different directories are considered different applications
Bug #673546 reported by
Ugo Riboni
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unity-2d |
Invalid
|
Medium
|
Unassigned | ||
| unity-2d (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Instances of the same app launched by two identical copies of the same desktop file but placed in different directories are recognized by the launcher as being different applications (thus with different icons in the launcher)
To reproduce the bug:
- Copy a desktop file in two different directories
- Run unity-qt launcher
- Execute the first copy of the desktop file (icon appears in launcher)
- Execute the second copy of the desktop file
Result:
- Two identical icons appear in the launcher
Expected Result.
- Only one icon should appear, and the two windows should be considered belonging to the same app
Brief investigation seems to point to the way libbamf matches these windows as belonging to different applications.
| summary: |
- [launcher] Identical desktop files in two dirs are considered diferent + [launcher] Identical desktop files in two dirs are considered different applications |
| Changed in upicek: | |
| status: | New → Confirmed |
| summary: |
- [launcher] Identical desktop files in two dirs are considered different - applications + [launcher] Identical desktop files in two different directoris are + considered different applications |
| summary: |
- [launcher] Identical desktop files in two different directoris are + [launcher] Identical desktop files in two different directories are considered different applications |
| Changed in upicek: | |
| importance: | Undecided → High |
| milestone: | none → m3 |
Revision history for this message
| Ugo Riboni (uriboni) wrote | #1 |
| Changed in upicek: | |
| assignee: | nobody → Ugo Riboni (uriboni) |
| status: | Confirmed → In Progress |
| Changed in upicek: | |
| importance: | High → Medium |
| milestone: | m3 → m4 |
| Changed in upicek: | |
| milestone: | 0.4 → none |
| affects: | upicek → unity-2d |
| visibility: | private → public |
| Changed in unity-2d: | |
| status: | In Progress → Confirmed |
| Changed in unity-2d (Ubuntu): | |
| status: | New → Confirmed |
| Changed in unity-2d: | |
| assignee: | Ugo Riboni (uriboni) → nobody |
| Changed in unity-2d: | |
| status: | Confirmed → Invalid |
| Changed in unity-2d (Ubuntu): | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
After talking about this with the bamf developer, we think that fixing it in bamf directly would be the best thing.
Bug #673656 will take care of that.