BAMF doesn't consider desktop files in ~/.local/share/applications
Bug #771172 reported by
Alex
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BAMF |
Fix Released
|
Undecided
|
Marco Trevisan (Treviño) | ||
Unity |
Fix Released
|
Undecided
|
Marco Trevisan (Treviño) | ||
Unity Foundations |
Fix Released
|
Undecided
|
Marco Trevisan (Treviño) | ||
unity-2d |
Fix Released
|
Undecided
|
Marco Trevisan (Treviño) | ||
bamf (Ubuntu) |
Fix Released
|
Undecided
|
Marco Trevisan (Treviño) | ||
unity (Ubuntu) |
Fix Released
|
Undecided
|
Marco Trevisan (Treviño) |
Bug Description
Binary package hint: unity
I made a custom Launcher following Jorge Castro's Guide on ask-ubuntu: http://
After placing the Launcher in ~/.local/
The bug IMHO is that now its available system wide - when in truth it is a customization only for my user. I consider this a security risk too - of course depending on the implemented feats of the custom Launcher.
Related branches
lp:~3v1n0/bamf/fixes
- Jason Smith (community): Approve
- Unity Community Hackers: Pending requested
-
Diff: 1121 lines (+555/-236)3 files modifiedsrc/bamf-application.c (+27/-14)
src/bamf-application.h (+4/-4)
src/bamf-matcher.c (+524/-218)
visibility: | private → public |
summary: |
- Custom Unity Launcher entries not from .local/share/applications + Custom Unity Launcher entries not from ~/local/share/applications |
Changed in unity (Ubuntu): | |
status: | Incomplete → New |
Changed in unity: | |
status: | New → Confirmed |
Changed in unity-2d: | |
status: | New → Confirmed |
Changed in bamf: | |
assignee: | nobody → Treviño (Marco Trevisan) (3v1n0) |
Changed in bamf (Ubuntu): | |
assignee: | nobody → Treviño (Marco Trevisan) (3v1n0) |
Changed in bamf: | |
status: | Confirmed → In Progress |
Changed in bamf (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in bamf (Ubuntu): | |
status: | In Progress → Confirmed |
Changed in bamf: | |
status: | In Progress → Confirmed |
Changed in bamf: | |
status: | Confirmed → Fix Committed |
Changed in unity-foundations: | |
status: | Confirmed → Fix Committed |
Changed in unity: | |
status: | Confirmed → Fix Committed |
Changed in unity-2d: | |
status: | Confirmed → Fix Committed |
Changed in bamf (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in unity-foundations: | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
Changed in unity-2d: | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
Changed in unity: | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
Changed in bamf: | |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
Changed in bamf: | |
status: | Fix Committed → Fix Released |
Changed in unity-foundations: | |
status: | Fix Committed → Fix Released |
Changed in unity: | |
status: | Fix Committed → Fix Released |
Changed in unity-2d: | |
status: | Fix Committed → Fix Released |
Changed in bamf (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in unity (Ubuntu): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
status: | New → Fix Released |
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.