[MU4 Issue] App Icon in Linux Task Bar is Generic X-Windows Icon

[JeffRocchio]

Very minor issue. On fedora-35 the running MS4 app icon in the taskbar displays the generic X-Windows icon vs a MuseScore icon.

I am running X-Windows still as I am still having issues with Wayland.

Screenshot:

Platform:

• fedora-35
• X-windows
• running the MS4 appimage: MuseScore-4.0.0-x86_64.AppImage

[MarcSabatella]

Did you install the AppImage yet (run from command line with “install” option)? This works for me.

[JeffRocchio]

I confess I do not understand what you mean by using the 'install' option. I should have added to my Platform info that I am running the KDE desktop. What I did was:

• Downloaded the appimage file from the MuseScore site (into my 'AppImages' directory).
• Set permission on the appimage file to Execute.
• Made a KDE desktop app-launcher file, which executes the command: /home/jroc/AppImages/MuseScore-4.0.0-x86_64.AppImage when double-clicked.

In creating the desktop file I did hunt around for a MuseScore icon for the desktop file to use as it's desktop display icon, but wasn't able to find one (probably I could get one off the github, but of course a normal user should need to go to such lengths).

I did google up appimage install and did see a little bit about some utility for Ubuntu that would auto-create the desktop file and add it to the menu system. But that seemed like it was just automating what I had already done. And I didn't see anything pertaining to fedora/KDE. I did take a shot at execting a few command variants in the terminal with 'install'; but only got errors back.

[MarcSabatella]

I mean, literally adding "install" as a command line option. That's how you install the AppImage. So from a terminal, type the filename of the AppImage, follow by a space and the word "install" (without the quotes. This is what integrates the AppImage into the desktop environment, setting up the desktop file, the icons, and everything else needed to make it work normally.

[JeffRocchio]

Ok, that did actually work Marc. Old dog, new trick - thank you.

But now I'm down a rabbit hole trying to understand why it worked. 30 mins this morning with google searches and I still can't find any documentation on this - other than a separate utility - "AppImageLauncher" - which I do not have installed on my machine. When I look at the terminal output it gives me the sense that 'install' was a parameter that the MuseScore appimage handled (as opposed to a directive to the Linux or KDE system). I get this impression because it appears to have installed two libraries (libjack.so.0 and libnss3.so) which must be specific to MuseScore. That and also that to make it work I did have to invoke it with the usual bash 'run this executable, don't treat this like a bash command' ./ prepend.

Just for my own education I'd be interested in understanding what component(s) of my system are responding to and handling the AppImage 'install' parameter.

Install Terminal Log: MS4_App-toolbar-icon_InstallLog.txt

[MarcSabatella]

The main thing the install option does is create a ".desktop" file in ~/.local/share/applications. That's how your desktop environment knows about things like which icons go with which programs, how to start them from a menu or taskbar or launcher or whatever your specific environment provides, etc. The install option also moves the AppImage itself to ~/.local/bin, and also copies the icons and/or other files needed to corresponding locations. All this is done by the AppImage itself, no other programs needed as far as I know.

JACk and NSS are not specific to MuseScore, and I don't think those libraries are actually installed by this process. But there are some fallback versions used, I think, so that MuseScore can use your own already-installed version if they are available, or the fallback versions if not. That's a bit of a mystery to me. But when you run the AppImage normally from the command line (without the "install") it should tell you which is being used - the installed version or the fallback.

[JeffRocchio]

JACk and NSS are not specific to MuseScore...

Yeah, after I posted my reply I did think to look at the timestamps on those two lib files - they were already on my system, which makes sense as they'd be needed by some other apps as well. So probably all that was happening was that the AppImage 'install' was checking to see if they were there.

Thanks for your help Marc.