Amarok does not register with the menu
Bug #693316 reported by
Conor Curran
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Amarok |
Fix Released
|
Medium
|
Aurélien Gâteau | ||
amarok (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Due to the different location of the Desktop file for Amarok on Ubuntu systems the application now cannot currently register and therefore be controlled by the applicaton.
Related branches
Changed in indicator-sound: | |
milestone: | none → 0.5.4 |
assignee: | nobody → Conor Curran (cjcurran) |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in indicator-sound: | |
status: | Confirmed → Fix Committed |
Changed in indicator-sound: | |
status: | Fix Committed → Confirmed |
assignee: | Conor Curran (cjcurran) → Aurélien Gâteau (agateau) |
Changed in amarok (Ubuntu): | |
status: | New → Fix Committed |
tags: | added: patch |
Changed in amarok: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
I thought the automatic lookup would solve this but alas no, the problem lies with the desktop file name being returned by the MPRIS root interface. Inorder for the new DesktopAppInfo( string desktop-file-d) to work the amarok desktop file id needs to actually be 'kde4-amarok, desktop' and not 'amarok.desktop'. The MPRIS spec is misleading here. To put simply the desktopentry on the root MPRIS interface for Amarok needs to return 'kde4-amarok'