Dash ignores NoDisplay=true if desktop file name contains a colon
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
Undecided
|
Unassigned | ||
unity-lens-applications |
Fix Released
|
Low
|
Michal Hruby | ||
unity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
unity-lens-applications (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
If I have a .desktop file with NoDisplay=true, and a mime association, it should create an application that shows up in a mime selection list, but not in the main application search or menu.
If I use a file named test-foo.desktop, and then invoke:
xdg-desktop-menu install test-foo.desktop
it behaves correctly. No search for foo in dash shows anything, but a right click on a .exe offers up Foo as a choice.
If I uninstall test-foo.desktop, copy it to a file named:
test-
and repeat the process, the Foo application appears in a dash search, which it should not.
This impacts all CrossOver installations, and since CrossOver likes to establish mime types to launchers without polluting the menu space, this bug really makes CrossOver + Unity an ugly experience.
Related branches
- Michal Hruby (community): Approve
-
Diff: 12 lines (+1/-1)1 file modifiedsrc/daemon.vala (+1/-1)
- Mikkel Kamstrup Erlandsen (community): Approve
-
Diff: 12 lines (+1/-1)1 file modifiedsrc/daemon.vala (+1/-1)
Changed in unity-lens-applications: | |
status: | New → Confirmed |
Changed in unity (Ubuntu): | |
status: | New → Confirmed |
Changed in unity-lens-applications (Ubuntu): | |
status: | New → Confirmed |
Changed in unity-lens-applications: | |
assignee: | nobody → Michal Hruby (mhr3) |
assignee: | Michal Hruby (mhr3) → nobody |
Changed in unity-lens-applications: | |
assignee: | nobody → Michal Hruby (mhr3) |
importance: | Undecided → Low |
status: | Confirmed → Triaged |
milestone: | none → 5.0.2 |
Changed in unity (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in unity-lens-applications (Ubuntu): | |
importance: | Undecided → Medium |
no longer affects: | unity (Ubuntu) |
Changed in unity-lens-applications: | |
status: | Triaged → Fix Committed |
Changed in unity-lens-applications (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in unity: | |
status: | New → Fix Committed |
Changed in unity: | |
status: | Fix Committed → Fix Released |
Changed in unity-lens-applications (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in unity-lens-applications: | |
status: | Fix Committed → Fix Released |
Changed in unity (Ubuntu): | |
status: | New → Fix Released |
This may well be a duplicate of Bug #879889, although the symptoms reported there seem different than what I've noticed.