Does appimagelauncher mess with Synfig normally?

Support
1

I was working with Synfig normally in Linux Mint 22.2 until yesterday.

I needed to reformat and install Linux Mint 22.3. I installed my typical AppImages: Krita, Inkscape, and appimagelauncher: GitHub - TheAssassin/AppImageLauncher: Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages (it creates the menu entry and icon for all appimages).

I found that the Synfig Appimage cannot start while the appimagelauncher (DEB version) is installed. Running the Synfig appimage from the terminal reveals: “Can’t open /tmp/.mount_NNNN/…”

I uninstalled it and Synfig ran fine again. It created its font cache in first run and started.

I did some experiments with appimagelauncher Appimage version and it was a little better. But I stop my story here…

Is appimagelauncher known to interfere with Synfig? Is there a way to make them work together smoothly. If not, I would be OK with just leaving appimagelauncher.

2

In one word, yes #3664

Synfig can be either installed or mounted on-the-fly.

image
image564Ă—196 14.5 KB

If you don’t want the integration and keep track of this choice, it creates a file ~/.local/share/appimagekit/SynfigStudio_no_desktopintegration
image
image466Ă—189 13.5 KB

If you accepted to install it,
~/.local/share/applications/appimagekit-synfigstudio.desktop (user mode) is created
(or /usr/share/applications/appimagekit-synfigstudio.desktop if --mode system)
which contains a Exec command pointing at the .appimage

AppImageLauncher does a bit the same but orchestrate everything staying in memory.

You should try to “Integrate and run” in AppImageLauncher, and to refuse the install (no) from the Synfig prompt, and also disable the question permanentely (yes)

Note that the official .appimage is still V1 format, permissions on /tmp/ can originate from here

1 Like
3

Thank you for you answer :slight_smile: