Hide Forgot
Created attachment 807603 [details] A screencast showing the problem. Description of problem: When creating a custom launcher with alacarte, it doesn't consider the icon I choose and will display an empty icon in the menu instead. After investigating, it appears that alacarte doesn't add the full path to the icon in the .desktop file, and forgets the extension. In the attached screencast, I try to create a launcher with an icon "/tmp/sample-icon.svg". In the end, the created desktop file has the following line: "Icon=/tmp/sample-icon". Version-Release number of selected component (if applicable): Nom : alacarte Architecture : noarch Version : 3.7.90 Révision : 1.fc19 How reproducible: always Steps to Reproduce: 1. Start alacarte 2. Create a custom launcher 3. Set an icon Actual results: The launcher doesn't display any icon. Also, the created .desktop file lacks the icon extension. Expected results: The launcher should display the chosen icon.
I can confirm that this bug also exists in Fedora 20. Indeed it just forgets the extension when writing to a .desktop file. Best regards
So the work around is the make sure all icons are jpg icons. Would be good to fix this though. The help menu also is broken in ubuntu for this same app. These sorts of polishing bugs should be more of a priority as they certainly lessen the first impressions for ubuntu (and gnome shell where I also encountered the same bug) I guess some think that editing the main menu is not a high priority for new users, perhaps they are right, but for intermediate users, or for those that have abandoned another linux desktop, editing the menu to add additional apps is important. Apps like eclipse use xpm files that just plain don't work. It was only by luck that I happened upon a comment indicating that jpg would work in this situation. Shame this has not been fixed as its an old bug.
It seems menulibre is the new workaround!
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.