Arch Linux User Repository

I've set up some basic Python automation to automatically update the AUR packages I maintain for speedier update times. Currently, new updates are checked for once every hour.

The source code is still in an early iteration, so small hiccups are expected. The source code is available on GitHub.

Is checksum correct?

==> Validating source files with sha512sums...
    Chatbox-1.5.0-x86_64.AppImage ... FAILED
==> ERROR: One or more files did not pass the validity check!

Directly running 'Chatbox' will result in the following error:

dlopen(): error loading libfuse.so.2

AppImages require FUSE to run. 
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information

Please add the dependency 'fuse2' 'fuse2fs' has changed its dependency from 'fuse' to 'fuse3' on May 21, which is probably why 'Chatbox' can not run directly.

diff --git a/PKGBUILD b/PKGBUILD
index 9e84c8c..fccddad 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -14,7 +14,7 @@ license=('GPL')
 depends=('fuse2fs')
 provides=("$pkgname")
 conflicts=("${_pkgname}-bin")
-options=(!strip)
+options=(!strip !debug)
 _appimage="${_pkgname}-${pkgver}-${arch}.AppImage"
 source=("${url}/releases/download/v${pkgver}/${_appimage}")
 noextract=("$_appimage")

I found this can resolve the problem after some experiments, although I'm unclear about the reason behind this.

I am very sorry for my lack of responsiveness; I have been extremely busy writing my master's thesis and have not been able to dedicate as much time as I would like to proper maintenance of the AUR package.

I have managed to reproduce the issue on my end and have spent some time trying to identify its root cause. However, with the limited time I have had, I have not yet pinpointed the exact source of the problem.

I have not made any changes to the underlying PKGBUILD, so it is quite puzzling that the issue has arisen. I would greatly appreciate any feedback on a potential fix, but otherwise, I will investigate it further as soon as my thesis is completed!

// Frederik

I encountered the same issue where I found that the appimage file in the opt directory seemed to have been altered. When I manually replaced it, everything went back to normal. I tried checking the PKGBUILD file but couldn't find any suspicious areas.

➜  chatbox-appimage git:(master) ✗ ls -lha /opt/Chatbox/Chatbox-1.3.6-x86_64.AppImage 
-rwxr-xr-x 1 root root 184K  5月 8日 10:53 /opt/Chatbox/Chatbox-1.3.6-x86_64.AppImage*
➜  chatbox-appimage git:(master) ✗ sudo cp Chatbox-1.3.6-x86_64.AppImage /opt/Chatbox/Chatbox-1.3.6-x86_64.AppImage
➜  chatbox-appimage git:(master) ✗ ls -lha /opt/Chatbox/Chatbox-1.3.6-x86_64.AppImage
-rwxr-xr-x 1 root root 99M  5月 8日 10:54 /opt/Chatbox/Chatbox-1.3.6-x86_64.AppImage*

Now running into problem of:

This doesn't look like a squashfs image.

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
open dir error: No such file or directory

Thank you @frederikstroem for your quick reply. Thank you for your pointers. It didn't work for me but it worked after rebooting the system. Bit strange but I have it working now :)

Hi @kuba-gaj,

I haven't been able to replicate the issue on my end. 🫤 Maybe you could try clearing the package cache and reinstalling?

rm -rf ~/.cache/yay/chatbox-appimage
yay -S chatbox-appimage

I hope that resolves the issue!

I have an error during installation: /home/kuba/.cache/yay/chatbox-appimage/PKGBUILD: line 25: ./Chatbox-1.2.1-x86_64.AppImage: cannot execute: required file not found
==> ERROR: A failure occurred in prepare().
Aborting...
-> error making: chatbox-appimage-exit status 4

I've set up some basic Python automation to automatically update the AUR packages I maintain for speedier update times. Currently, new updates are checked for once every hour.

The source code is still in an early iteration, so small hiccups are expected. The source code is available on GitHub.