Apps scope crashes due to malformed AppID in .desktop file
Bug #1530841 reported by
Daniel d'Andrada
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Critical
|
Pat McGowan | ||
unity-scope-click (Ubuntu) |
Fix Released
|
Critical
|
dobey |
Bug Description
Steps to reproduce the issue:
1 - Copy football.desktop (see attachment) to /home/phablet/
2 - Copy football-ball.png [1] to /home/phablet/
3 - Pull down the Apps scope in unity8-dash to refresh it
Expected outcome:
I should see a football icon the Apps scope. Or, if there's something wrong in that desktop file, I should at least see the same list of applications as before.
Actual outcome:
Nothing is shown at all. The apps scope remains empty.
Comments:
I was trying to have an icon in the apps scope point to a test application of mine.
Removing that desktop file from the applications dir makes the apps scope work again
Related branches
lp:~dobey/unity-scope-click/bad-appid
- Charles Kerr (community): Approve
- PS Jenkins bot: Needs Fixing (continuous-integration)
-
Diff: 47 lines (+18/-3)3 files modifiedlibclickscope/click/interface.cpp (+7/-2)
libclickscope/tests/applications/user/badd-appid.desktop (+10/-0)
libclickscope/tests/test_interface.cpp (+1/-1)
Changed in unity-scope-click (Ubuntu): | |
importance: | Undecided → Critical |
assignee: | nobody → Rodney Dawes (dobey) |
status: | Confirmed → In Progress |
Changed in canonical-devices-system-image: | |
assignee: | nobody → Pat McGowan (pat-mcgowan) |
importance: | Undecided → Critical |
milestone: | none → ww02-2016 |
status: | New → Confirmed |
summary: |
- Apps scope stops working due to a simple desktop file + Apps scope crashes due to malformed AppID in .desktop file |
Changed in canonical-devices-system-image: | |
status: | Confirmed → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.