Duplicate webapps launcher confuses bamf
Bug #1300864 reported by
David Barth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BAMF |
New
|
Undecided
|
Unassigned | ||
WebApps: libunity-webapps |
Fix Released
|
High
|
Alexandre Abreu | ||
unity-webapps-qml |
Fix Released
|
High
|
Alexandre Abreu | ||
libunity-webapps (Ubuntu) |
Fix Released
|
High
|
Alexandre Abreu | ||
unity-webapps-qml (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Even with the recent fixes to bamf, I can still be in cases where my webapp launcher does not associate correctly on the launcher.
It happens for no particular webapp. However it stops occuring as soon as I suppress the duplicate desktop file we generate in ~/.local/
Related branches
lp:~abreu-alexandre/unity-webapps-qml/broken-desktop-file-gen
- PS Jenkins bot (community): Approve (continuous-integration)
- David Barth: Pending requested
- WebApps: Pending requested
-
Diff: 29 lines (+12/-0)1 file modifiedsrc/Ubuntu/UnityWebApps/plugin/unity-webapps-api.cpp (+12/-0)
summary: |
- Duplicate webapps launcher confuse bamf + Duplicate webapps launcher confuses bamf |
Changed in libunity-webapps: | |
status: | New → Fix Committed |
importance: | Undecided → High |
assignee: | nobody → Alexandre Abreu (abreu-alexandre) |
Changed in libunity-webapps (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Alexandre Abreu (abreu-alexandre) |
milestone: | none → ubuntu-14.04 |
Changed in unity-webapps-qml: | |
assignee: | nobody → Alexandre Abreu (abreu-alexandre) |
importance: | Undecided → High |
Changed in libunity-webapps (Ubuntu): | |
status: | In Progress → Confirmed |
status: | Confirmed → Fix Released |
Changed in libunity-webapps: | |
status: | Fix Committed → Fix Released |
Changed in unity-webapps-qml: | |
status: | New → Fix Released |
To post a comment you must log in.
To be clear, the consequence of this fix is that we drop support for custom webapp actions for now, ie "compose new message". This API is not fully working right now anyway.
We will restore the custom actions at the system level first, to avoid the desktop file duplication whenever possible.