Edit: Es scheint, dass #AppImageLauncher der Culprit ist. Obwohl von #LibreWolf empfohlen 😳 Kaum deinstalliert, funktioniert LibreWolf wie als wäre nichts gewesen!

#Manjaro #LibreWolf #AppImage #FediHelp #FollowerPower  

Ich habe ein neues #AppImage von #LibreWolf heruntergeladen. AppImages werden normalerweise über #AppImageLauncher gestartet (und ALLE außer LibreWolf funktionieren einwandfrei). Nachdem der Doppelklick nichts tat, startete ich via Terminal mit folgendem Output...

Leider war die verlinkte Seite keine Hilfe und diese ebenfalls nicht: https://docs.appimage.org/user-guide/troubleshooting/fuse.html

Kann mich jemand in die richtige Richtung lenken? Wie kann ich das Problem lösen?

Gear Lever

Gear Lever

INSTALL

DESCRIPTION:

  • Integrate AppImages into your app menu with just one click
  • Drag and drop files directly from your file manager
  • Keep all the AppImages organized in a custom folder
  • Open new AppImages directly with Gear lever
  • Manage updates: keep older versions installed or replace them with the latest release
  • Save CLI apps with their executable name automatically
  • Modern and Fresh UI

#appimage #appimageLauncher

GitHub - TheAssassin/AppImageLauncher: Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages

Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages - TheAssassin/AppImageLauncher

GitHub

I am a happy user of #logseq. For Linux, it is available as #appimage which I usually install using #AppImageLauncher.

Unfortunately, after upgrading Ubuntu, Logseq couldn't be launched anymore in the usual way. After some searching online, I found a workaround.

You need to locate and open the desktop file and add `--no-sandbox %u` to the end of the line starting with `Exec`.

Not an ideal solution, but it'll have to do for now. See this post for more details. https://ecodiv.earth/post/logseq_desktop_integration/

Logseq on Ubuntu – Ecodiv.earth

As short note about issues with the integration of the Logseq Appimage with Ubuntu desktop, and how this can be fixed.

¿Usas #GNULinux, navegas en #gemini con #Lagrange, instalado desde #AppImageLauncher, pero al pulsar una URL que inicia con `gemini://`, desde fuera de Lagrange no pasa nada o se abre en otro programa?
Quizás seas la única persona con ese perfil en mi red, pero si esto te ayuda me doy por bien servido:
Abre `.local/share/applications/defaults.list`, agrega al final:

```
x-scheme-handler/gemini=appimagekit_NúmerosGeneradosPorAppImageLauncherUsaLosTuyos-fi.skyjake.Lagrange.desktop
```

Y guarda

AppImageLauncher - integrate AppImages to your application launcher - LinuxLinks

AppImageLauncher is C++ software which integrates AppImages to your application launcher with a single click.

LinuxLinks

"How did I install application XYZ again? It seems to reside in /opt/... hmm I don't even have #appimagelauncher installed on this machine... so probably a local dpkg..."

Is it just me or is this actually insanity? #linux #flatpak #appimage #packagemanager

Integrate AppImages To Application Menu Using AppImageLauncher - OSTechNix

This guide explains what AppImageLauncher is and how to integrate AppImages to application menu using AppImageLauncher utility in Linux.

OSTechNix

Which #linux packaging format do you prefer?

My choice is usually #rpm but in some cases I prefer #Flatpak because of #flatseal that makes app permissions easy to manage. And many apps are only available as a Flatpak (or the rpm doesn't work well like the Kdenlive rpm from #rpmfusion lol) #appimage is also pretty decent with #appimagelauncher installed.
But I avoid #snap at all cost because #snapstore is proprietary.
#packaging #package #deb #fosserytech

traditional (deb, rpm etc.)
63.8%
Flatpak
26.7%
Snap
4.3%
AppImage
5.2%
Poll ended at .