Icon not added by "AppImage Launcher"

• Jan 24, 2021 - 22:32
Reported version
3.6
Type
Graphical (UI)
Frequency
Few
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project

Appimage has been installed using Appimage Launcher. System running is Linux Mint 20.1 Cinnamon.

More of a trivial annoyance rather than anything else... there does not appear to be an icon attached to the appimage in the latest release. This means that if you "pin" to the task bar for easy launching it is invisible. It also does not show up with an launcher icon anywhere - it just shows as text in the cinnamon menu, for example.


Comments

Frequency Once Many

Hello, I have the same issue here in Ubuntu 20. When I "Integrate and Run" the AppImage with AppImageLauncher, the MU icon appears in the side bar, but in the Applications desktop menu, MuseScore 3.6-portable has the default system "gear" icon. When I close the first run of the application and re-open it from the desktop menu shortcut, Musescore uses the gear icon in the side bar. ~/.local/share/icons/hicolor/{size}/apps/ also does not contain the MuseScore icon for any of the sizes. Can you help me with this?

Generally, we have no control over how third-party utilities like "AppImage Launcher" work, and indeed, often they don't. I recommend installing the AppImage the supported way we provide ourselves and document in the installation instructions: simply run the AppImage with the "install" option. This should do the necessary integrations.

However, on some systems, there can be a problem due to a mismatch between the application name in the desktop file and the name the application actually runs as. I find on my Debian-based system, I need to edit the desktop file to change the application name from "MuseScore 3.6.2 Portable AppImage" to simply "MuseScore 3", then the icon works. Maybe a similar fix would help with the AppImage Launcher too, but I don't know anything about how that works. I know with the regular support install option, the desktop file goes to ~/.local/share/applications and you edit it there.

Title Appimage icon not showing in latest release Icon not added by "AppImage Launcher"

OK, it's still not clear if this is a bug on the "AppImage Launcher" program or a side effect of the discrepancy in the naming, but anyhow, it's definitely something we'd like to work better for all systems in the future.

In reply to by Marc Sabatella

Well, I have other appimages which do not have this problem (as in, the icons show up just fine without any further intervention), and as far as I can tell (I'm really not an expert), the end result of running the "appimage launcher" program is the same as if I had installed it "manually" - it is just a little more convenient. So for my system, at any rate, it does seem related to the musescore appimage somehow. My very small sample of other appimages (only two!) were all developed using Electron I believe.

Could simply be an unwarranted assumption made by that third party installer program - something that happens to be true for some AppImages but not necessarily all. Which again is why we recommend using the "install" we provide and support ourselves - but as mentioned, on some systems at least, you still need to customize the desktop file to set the application name to "MuseScore 3".

I'll comment here, beyond just "I'm also experiencing this issue".

I decided to try the MuseScore AppImage after an Ubuntu 20.04.3 LTS update made the MuseScore snap unusable.

According to https://appimage.org/, the story is:

> Download an application, make it executable, and run! No need to install.

and:

> To run an AppImage, simply:
> - Make it executable
> $ chmod a+x Subsurface.AppImage
> - and run!
> $ ./Subsurface
.AppImage
> That was easy, wasn't it?

The implication, from that marketing copy, is that everything the app needs to run should be contained in the AppImage and should not need to be "installed".

Since I don't knowing the technical details of AppImages, how they're built, or what the software contract for them is, I myself would be cautious about making "unwarranted assumptions" in either direction. However, one thing I do know in the world of software is that one person's unwarranted assumption is another person's poorly documented contract.

That said, part of the whole story for AppImages is to enable ease of distribution, ease of use, ease of update/removal, etc. Third-party tools like AppImageLauncher exist because they fill gaps in that process in predictable and automated ways, rather than a random install argument to an AppImage that is supposed to "just work".

(Note that I'm not sure how I would have discovered the magic install argument to the MuseScore AppImage if I had not experienced this icon problem myself and happened to find this forum discussion, as I never would have known to look for such an argument to an AppImage. Is there an equivalent "uninstall" to remove the detritus later on?).

How about we all work together and figure out why some AppImages such as KeePassXC work fine without installing, and MuseScore has difficulty with that? Is this a limitation in the AppImage format? (Note that I picked KeePassXC as an example because it, like MuseScore, also uses Qt5). How can the community help MuseScore improve this?