I cant execute a appimage in Dolphin

Hi All,

I am running Plasma on a Orange PI 5 Plus and I cant execute a appimage in Dolphin. Only “Open with Disk Mounter” is shown as alternative and not Execute.

File is “Raspberry_Pi_Imager-1.9.0-aarch64.AppImage” and it is marked as “execute as a program”.

I have tryed to deal with confirmations, find a dolphin complement but nothing is working for me.

Operating System: Ubuntu 24.04
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
Kernel Version: 6.1.84-vendor-rk35xx (64-bit)
Graphics Platform: Wayland
Processors: 4 × ARM Cortex-A-55, 4 × ARM Cortex-A76
Memory: 15.6 GiB of RAM
Graphics Processor: Mali-G610
Product Name: Orange Pi 5 Plus

.img used to install:
“Armbian - unofficial_25.02.0 - trunk_Orangepi5-plus_noble_vendor _ 6.1.84_kde-neon-kisak _ desktop”

Thanks from Brazil,

Cury

is the appimage file executable, if you check in properties > permissions?

if not, check the executable box and see if that changes anything.

1 Like

Yes, it is marked.

Try a command that will give some useful information. In the konsole type in and hit enter key changing the /path/to/ to the actual location of the file.

/path/to/Raspberry_Pi_Imager-1.9.0-aarch64.AppImage

This should either start it or give the error it is experiencing with starting it.

Hi redgreen925

At command line is running ok…

./Raspberry_Pi_Imager-1.9.0-aarch64.AppImage

It shows this msg. on console:
Could not attach Keys property to: OptionsPopup_QMLTYPE_33(0xaaaadb5f7df0) is not an Item

But it runs ok…

But I want to run it from dolphin, etcher appimage does not run too.

There is something missing in my installation.

Thanks frm Brazil,

Cury

Forget dolphin run it from a .desktop file, here is the one I have for Etcher.

zeus@9600k:~$ cat .local/share/applications/balenaEtcher.desktop 
[Desktop Entry]
Type=Application
Exec=env GTK_USE_PORTAL=1 /home/zeus/bin/balenaEtcher-1.18.11-x64.AppImage --no-sandbox %U
Icon=application-x-iso9660-appimage
Name=balenaEtcher
Comment=Create USB installation media from bootable ISOs
NoDisplay=false
StartupNotify=true
Terminal=false
Categories=Utility;
X-KDE-SubstituteUID=false
X-KDE-Username=​

Could be the sandbox junk messing with you for the Etcher. Try my file in the same directory I have it in and see if it shows up in the Utilities menu to launch it, change the EXEC line to your location. You can do similar for the Pi_Imager just try changing the Exec line to the path you have it at and the Name of course. I am thinking both will now start up from the menu selections.

i just downloaded a random app from the appimagehub and when i double click on in dolphin i get this

and these were the permissions that the download had when i inspected

so that part seems to work fine on kubuntu 22.04 (dolphin 22.04.3)

was also able to launch the app by creating a new item in the application menu… right click, choose edit applications

from the dialog choose submenu where you want the app to appear and choose new item.

select the program to run and browse to the appimage file (downloads for my test), and save.

now your new app should be listed and launchable like any other installed app.

Could this be the libfuse2 issue with appimages on recent distros, ubuntu included? I know that this seems to been fixed in *buntu proper, but I wonder if it is still a thing on the Arm builds

Yes, your .destop (modified) is working for me to start Rasp-Imager.

But I’d like to start from Dolphin… Just like my Debian KDE on a X64 machine,

NO one appimage is starting from Dolphin, I have tested 5 at least.

Thanks for your hint

See You,

Good to read it works for you with the .desktop file, I have no idea on the Dolphin I never use it. I use the Konqueror it allows to split the screen view with up and down panes allowing you to see the full file name, not the stupid split the screen side by side every other program does and waste all that space for file name display. Really Dolphin should start the .appimage if the executable bit is set on it but I have no ideas to try and find out why it is not working on the PI.

I know it is a workaround, but maybe trying Appimagelauncher might be helpful for the moment, at least until we can find out what is missing or different on your Arm build versus a normal x86_64 neon install.

I really need to dust off the build scripts I have and get Plasma on my ChromeOS tablet.

Hi Claydoh,

I read the link and decided to install libfuse2t64.

But apt said “libfuse2t64 is already the newest version (2.9.9-8.1build1)”

I found that article so, so actual, real, and as I am opinionated I decided to remove pkt by apt:

From apt: (some lines are in portuguese, but “undestandable”?!?!
sudo apt remove libfuse2t64
Lendo listas de pacotes… Pronto
Construindo árvore de dependências… Pronto
Lendo informação de estado… Pronto
Os seguintes pacotes foram instalados automaticamente e já não são necessários:
libboost-chrono1.83.0t64 libboost-program-options1.83.0 libfmt9
libspdlog1.12 libtinyxml2-10
Utilize ‘sudo apt autoremove’ para os remover.
Os pacotes a seguir serão REMOVIDOS:
cryfs encfs libfuse2t64 plasma-vault

to confirm…

Lets reintall:

sudo apt install libfuse2t64
Lendo listas de pacotes… Pronto
Construindo árvore de dependências… Pronto
Lendo informação de estado… Pronto
Os seguintes pacotes foram instalados automaticamente e já não são necessários:
libboost-chrono1.83.0t64 libboost-program-options1.83.0 libfmt9
libspdlog1.12 libtinyxml2-10
Utilize ‘sudo apt autoremove’ para os remover.
Os NOVOS pacotes a seguir serão instalados:
libfus e2t64
0 pacotes atualizados, 1 pacotes novos instalados, 0 a serem removidos e 2 não atualizados.

This time only libfuse2t64 were reinstalled, not cryfs, encfs and plasma-vault

and…

and…

and…

BINGO…

DOLPHIN is openning Rasp-imager for execution.

Thanks man…

Now I have 4 problems:

I run apt upgrade every day so libfuse2t64 was updated?!?!?!

or the problems are cryfs, encfs, plasma-vault…

Tomorrow I’ll look for the functions of these 3 pkts and decide if I reinstall them.

Once more Thanks man,

Good night from Brazil,

Cury

1 Like

how does that compare to gear lever which i can find in discover on kubuntu?

Dunno. I’ve used appimagelauncher for ages, though admittedly I don’t have it installed currently, since I did a fresh install of Noble.

I’ve never even heard of gear lever, somehow.
This is actively developed compared to Appimagelauncher, after checking both of their githubs

Appimagelauncher have pre built Arm debs and appimages, though, which is relevant for this thread.

1 Like