Anyone else experiencing issues running Appimage apps on @ubuntu 25.04? Installing libfuse2t64 doesn't fix the issue like in 24.04.

#Librewolf, #Firefox, #Thunderbird, #Microsoft #Edge and #Teams are now all running isolated using #firejail on my #Slackware laptop while installed from #AppImage, DEB files and generic binaries.

Yep, I should blog it down. But I’m not sure how to turn it given that there are some many mixed subjects there.

I'm giving up maintainership of the #Subsurface dive log package on #Flathub. There is a too wide gap between how it is developed and what Flathub/Flatpak expects, and I still can't use the Flathub version with my own dive computer because there are Bluetooth issues I have no idea how to debug.

I cannot justify investing more time on an application I use at most three times a year. Especially when the official #AppImage just works.

Today is the day! — Nitrux 3.9.1 "mk" is available to download — https://nxos.org

We are pleased to announce the launch of Nitrux 3.9.1. This new version combines the latest software updates, bug fixes, performance improvements, and ready-to-use hardware support.

Nitrux 3.9.1 is available immediately.

Changelog: https://nxos.org/changelog/release-announcement-nitrux-3-9-1/

Set an AppImage Application as Default App https://itsfoss.com/set-appimage-as-default/ #AppImage

When it comes to #Linux and packages for the user, #Flatpak for when you need shared dependencies and #AppImage for when you need a portable app. Basically we've already solved both the "app store" and "downloadable executable" problems.

Snaps could compete, if it supported third party repos OOB and wasn't a vendor lock-in situation, but if and buts were candies and nuts...

Flatpaks, Snaps, & AppImages: "Do we really need these Universal App For...
https://youtube.com/watch?v=so_f6OtRWRo

It seems AppImage has been gaining traction as the (sometimes only) distribution format of choice. I use multiple AppImages so to avoid having to manually run them, I set up `appimaged` that handles integration of the packages into the desktop automatically (creating app icons for them etc).
I noticed though that it fires a network request looking for registered app updates every two minutes as part of an auto-update functionality which I don't really need.

Another thing is that it monitors multiple directories for AppImages (so it can do its thing setting them up), but it also watches `~/Downloads` and `~/Desktop` which feels like overkill - an app can get registered even before I put it into its final location, plus the content in both of these locations could be numerous and frequently change, which doesn't seem ideal from a performance perspective when monitoring.

To address these, I forked the repository and applied a few changes to `appimaged`:
- Added an in-source flag to disable AppImage update checks, with the nice side effect of reducing the size of the resulting binary.
- Implemented another flag so that a reduced directory set is watched by default for AppImages, removing Downloads and Desktop (and also system-level directories like `/opt`, which might not be for everyone). It's easy to change though. Also de-duplicated this directory list because all the $PATH items are added to it too.

If you're interested in running this version, I set the main branch of my repo to the one containing these changes. Building is straightforward: `scripts/build.sh appimaged`. It only needs Go, the rest is handled via the container-style build script, cleaning up after itself.

https://github.com/shiide/go-appimage

are all of your #AppImage launches working in k/ubuntu 24.04.2? a few of mine just won't start, so i wonder if it's fixed in the distro update.

قارئ و مشغل #القرآن الكريم مجاني و مفتوح المصدر لأنظمة الحاسوب
#Quran Companion
#Free and #open_source #desktop Quran reader and #player
#gnutux #linux #windows #macos #flatpak #appimage
https://0xzer0x.github.io/projects/quran-companion/

Folio 25.01 has been released, apps stores are building and deploying or grab it from the GitHub release page.

This is a minor bug fix release with changes including; rename a note could cause data loss, new notes might contain garbage characters, sidebar reopening during save if closed, and translation updates as well.

See the whole change log in the Folio->About page or on the GitHub release page (https://github.com/toolstack/Folio/releases/tag/25.01)

GIMP Automatic AppImage development builds

#Linux #appimage #gimp

Automatic builds (sometimes called "nightlies") are generated at regular intervals by our Continuous Integration process. This allows to run the last version of our code, though be aware that it also means you would be running very experimental code!
These builds are meant to test future GIMP versions and help us debug, we do not advise to use these for production.

https://gitlab.gnome.org/GNOME/gimp/-/pipeline_schedules

- Go to GIMP's scheduled pipelines listing and click the `Last Pipeline`.
`Passed` button listed next to the AppImage item.
- Select the job named `dist-appimage-weekly`.
- Click the `Browse` button.
- Navigate to the `build/linux/appimage/_Output/` directory.
- Finally click the `GIMP-3.0.0-RC2+git-x86_64.AppImage` or `GIMP-3.0.0-RC2+git-aarch64.AppImage` file to download and install the AppImage.