#Commit hash in AppImage desktop file?

21 messages · Page 1 of 1 (latest)

frank shoal
#
  1. I am building my app with Tauri as an AppImage on Ubuntu 22.04, but when I integrate my app with my desktop (I use AppImageLauncher), I see that the name shows up as "my_app (066e...)" instead of just "my_app". The "066e..." is the beginning of the latest commit in my git repository.

2.Also, the name of the window when I hover over it in the dock shows up as "My-app", although I want it to be the same as the title in the window frame, "My App".

How do I fix this?

vivid jasper
#

The .desktop file does not contain a commit hash (you can inspect it by doing ./my-app.AppImage --appimage-mount and then cding into the dir it mounts to), so i have no idea where the hash comes from 🤔 probably forgot something simple here

#

can you open an issue for problem 2 tho? should be an easy fix hopefully

frank shoal
vivid jasper
#

weird, this is not in the desktop file on my end, but i also don't have appimagelauncher on my system so maybeee that's related?

frank shoal
#

I can try booting up a VM without appimagelauncher to see if that could be causing the issue

vivid jasper
#

ah sorry, looked at the wrong desktop file

#

but it's also not set from tauri, so it's something from the appimage tools doing it

#

looks like appimagetool is looking for the VERSION env var, which tauri also doesn't set iirc

#
  • Also, if VERSION is not set and -g is called and if git is on the path, use
  • git rev-parse --short HEAD
frank shoal
#

Hmm, I tried running cargo tauri build -b appimage with VERSION=1.1.0 and the desktop file did have

X-AppImage-Version=1.1.0

, but the app name in the activities view now shows up as my_app (1)

#

https://github.com/AppImage/AppImageKit/issues/662 I found the related issue, it seems to be a feature of appimagelauncher if there is an X-AppImage-Version. I understand why this behavior would be nice, but it's not what I want for my app right now. I think that there should be a configuration option in Tauri that allows you to disable adding X-AppImage-Version to the desktop file. In addition, if X-AppImage-Version is enabled, it should be setting the VERSION env var to the version already specified in the Tauri configuration, to avoid adding a commit hash to the app name.

GitHub

We got this report from someone who has appimaged and lots of different krita appimages: https://twitter.com/AdmiralTofu/status/965374714448351233 , and have https://bugs.kde.org/show_bug.cgi?id=39...

vivid jasper
#

I think that there should be a configuration option in Tauri that allows you to disable adding X-AppImage-Version to the desktop file
Yeah i think so too, that's why i looked into it in the first place, but the problem is that it's outside of our control, no matter what we do it looks like the appimage tools always falls back to something unless we actually specify a version.

#

I agree with setting VERSION to the app version tho

vivid jasper
#

did you try setting VERSION="" ?

frank shoal
#

No, I'm trying that now

#

The desktop file now has X-AppImage-Version=, and the app name is now my_app (1)

vivid jasper
#

sad, i hoped appimaged/appimagelauncher wouldn't fall back to some version if x-appimage-version is set but empty :/

frank shoal
#

what if I just didn't have an x-appimage-version?

#

I don't know how to bundle appimages, but I could modify the desktopfile in the appdir and re-bundle it