#appimage

2 posts · Last used 11d

Back to Timeline
dazo
@dazo@infosec.exchange · Apr 21, 2026
The #AppImage "packaging" approach being embraced by many projects is just another poor approach. It does not really solve what it is expected to should solve: Dependency issues. More and more .AppImage downloads now produce results like these: /tmp/.mount_tumpa-Z5HMuu/usr/python/bin/python3: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory /tmp/.mount_activiXYBUA0/aw-qt: symbol lookup error: /tmp/.mount_activiXYBUA0/libQt6WaylandClient.so.6: undefined symbol: wl_proxy_marshal_flags I dunno if it is due to incorrect packaging or a design artefact with AppImage. I believe #flatpak is the only true sane way to go. At least if you don't want to frustrate users. #linux #foss #opensource #packaging
1
0
0
simgal55
@simgal55@social.vivaldi.net · Apr 29, 2026
I wonder if @Tutanota@mastodon.social plan to update their #appimage to a more recent runtime. Because with the recently released #Fedora44 their apps does not work anymore. #linux #rant
0
2
0

You've seen all posts