pkg2appimage: appimagekit-meshmixer.desktop: error: value "2.7" for key "Version" in group "Desktop Entry" is not a known version
When I launch the MeshMixer AppImage on Fedora 25, it asks me the following question:
But nothing happens if i click Yes. I’ve tried in terminal an there’s an error:
/home/churchyard/.local/share/applications/appimagekit-meshmixer.desktop: error: value "2.7" for key "Version" in group "Desktop Entry" is not a known version
Error on file "/tmp/.mount_miK9kd/meshmixer.desktop": Failed to validate the created desktop file
The latest specification says:
Version of the Desktop Entry Specification that the desktop entry conforms with. Entries that confirm with this version of the specification should use 1.1. Note that the version field is not required to be present.
The entire MeshMixer/MeshMixer.AppDir/meshmixer.desktop
contents form the machine I created the AppImage:
[Desktop Entry]
Version=2.7
Name=MeshMixer
Name[en_GB]=MeshMixer
GenericName=Mesh processing
GenericName[en_GB]=Mesh processing
Comment=Application for aggregating, fixing and editing meshes, and for preparing them for 3d printers.
Type=Application
Exec=meshmixer.wrapper %F
Icon=meshmixer
Terminal=false
Categories=Graphics;
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 29 (29 by maintainers)
Commits related to this issue
- Run desktop-file-validate, addresses #166 — committed to AppImageCommunity/pkg2appimage by probonopd 7 years ago
- Copy meshmixer.png to usr/share/icons/hicolor/128x128/apps https://github.com/probonopd/AppImages/issues/166#issuecomment-271158558 — committed to AppImageCommunity/pkg2appimage by probonopd 7 years ago
- Address issues in #166 — committed to AppImageCommunity/pkg2appimage by probonopd 7 years ago
I’ll email them to follow up and see what they plan to do; I have annual leave coming up, so I do have some time to chase things.
That is unfortunate, but seems only (from that article) to be related to eagle and meshmixer is still marked prominently as free (kostenlos).
I’m happy to take up contacting them as a neophyte to AppImage, but it it might be more effective with someone with more experience/clout with AppImage (corpthink).
We could add
desktop-file-validate
to the Recipe so that we see these kinds of errors during AppImage creation time…