Gearlever doesn't detect appimages that don't have an icon file
Closed this issue · 10 comments
I set the directory where I store my appimages ('/user/Applications') in the gearlever's Preferences and expected it to display these appimages everythime it's opened. But at every startup Gearlever asks me to add an appimage or select a folder (even though the folder is registered in the Preferences)…
Maybe this is the expected behaviour but I find it quite strange as it reduces the app's usefulness…
Hi @rene-coty
The latest update .18 fixes a bug which may have prevented some appimages to show up in the list
Has this update already gone out to flathub? I'm seeing the issue now on 1.0.18:
$ flatpak info it.mijorus.gearlever
Gear Lever - Manage AppImages
ID: it.mijorus.gearlever
Ref: app/it.mijorus.gearlever/x86_64/stable
Arch: x86_64
Branch: stable
Version: 1.0.18
License: GPL-3.0-or-later
Origin: flathub
Collection: org.flathub.Stable
Installation: system
Installed: 10.2 MB
Runtime: org.gnome.Platform/x86_64/45
Sdk: org.gnome.Sdk/x86_64/45
Commit: 3c05bdaa94eb397feb140cf4e6d82a82646a8b91d5b977e26d70b9023eff8fc9
Parent: 141b6c8e2b2238d60450d247ad42658be6017458411bcc59d0b7136f88a0346a
Subject: Update it.mijorus.gearlever.json (44140a7a)
Date: 2023-12-30 20:21:34 +0000
It is, yes.
The issue might be caused by something else then.
Could you please paste here the .desktop files of one of the missing apps ?
Also, please note that Gear Lever only detects desktop files in your home directory, under ~/.local/share
I'm trying to "restore" Gearlever to a new machine without using the UI.
Beyond restoring the ~/AppImages folder, what other files need to be restored? Just the correlating .desktop files in ~/.local/share?
That resolved it: by backing up both ~/AppImages/ and /.local/share/applications/, the full state of Gearlever can be restored onto a new machine noninteractively. 👍
Ah, spoke too soon: just tried the above but Gearlever doesn't see the app.
Where else does Gearlever store it's state? I'd like to be able to transparently restore it doing something like the above.
Based on the below I would expect Balena Etcher to show up enabled and tracked by Gearlever:
For what it's worth I don't see any modifications in ~/.var/app/it.mijorus.gearlever after manually installing an appimage with Gearlever, suggesting no data for app installs lives there.
Eureka: figured it out.
- It looks like
~/AppImages/.iconsneeds to be backed up and restored as well. - Any
.desktopfiles in~/.local/share/applicationsneeds to use the full/home/<username>/path, not~:
Once these issues were ironed out, Gearlever "detects" that it had already configured the AppImage:
For others trying to backup/install Gearlever, here is my Chezmoi setup:
$ chezmoi add ~/.local/share/applications/to sync your desktop files.$ chezmoi add ~/AppImages/.icons/to sync your desktop icons.- Create a run_once-setup-appimages.sh to install your AppImages.
- Always use the same username on your machines to ensure
.desktopfiles work.
Cheers.
Hello! I got quite the same issue with FreeCAD-0.21.2-Linux-x86_64.AppImage
This file doesnt have an icon so after unlocking and pressing "move to the app menu" it stucks with three dots ...
Debian 12
Hello! I got quite the same issue with FreeCAD-0.21.2-Linux-x86_64.AppImage This file doesnt have an icon so after unlocking and pressing "move to the app menu" it stucks with three dots ... Debian 12
Hi, version 1.5.2 should address this issue. Now freecad should show its icon correctly
Thanks for contributing with this bug report.
If you want to support my work, please consider a small donation.