Package Details: vial-appimage v0.7.1-2

Git Clone URL: (read-only, click to copy)
Package Base: vial-appimage
Description: Vial is an open-source cross-platform (Windows, Linux and Mac) GUI and a QMK fork for configuring your keyboard in real time, similar to VIA.
Upstream URL:
Keywords: keyboard via vial
Licenses: GPL2
Conflicts: vial
Provides: vial
Submitter: pieterv24
Maintainer: pieterv24
Last Packager: pieterv24
Votes: 9
Popularity: 0.46
First Submitted: 2021-04-01 22:10 (UTC)
Last Updated: 2024-03-28 08:58 (UTC)

Dependencies (1)

Required by (0)

Sources (2)

Latest Comments

1 2 Next › Last »

dmfay commented on 2024-03-31 04:59 (UTC)

Thanks Static_Rocket! That change does the trick on my end.

Static_Rocket commented on 2024-03-30 20:04 (UTC) (edited on 2024-03-30 20:04 (UTC) by Static_Rocket)

diff --git a/PKGBUILD b/PKGBUILD
index 81f9bcc..ddbfcf7 100644
@@ -12,7 +12,7 @@ pkgdesc="Vial is an open-source cross-platform (Windows, Linux and Mac) GUI and
+options=(!strip !debug)

dmfay commented on 2024-03-30 16:12 (UTC) (edited on 2024-03-30 16:13 (UTC) by dmfay)

I'm seeing exactly the same error as Alberto using both pikaur and makepkg. I have fuse2 and 3 installed, and I'm not editing the PKGBUILD. I can run the makepkg-downloaded AppImage directly without issues.

pieterv24 commented on 2024-03-28 08:57 (UTC)

@AlbertoAru I'm unable to reproduce this issue with both yay and makepkg. Might it be related to the path you're using to build this package? It looks like it cannot find the file.

The URL you posted, is the same as the one used by the PKGBUILD, so the file downloaded should be the same.

If you're still unable to fix your issue. Please provide a bit more context on how to reproduce. (aur helper, path etc.)

AlbertoAru commented on 2024-03-28 02:04 (UTC)

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. 
for more information
open dir error: No such file or directory

When using the --appimage-extract option:

This doesn't look like a squashfs image.
Failed to open squashfs image

I saw that if I directly download the AppImage from the source and manually execute it, it works fine

markstos commented on 2023-12-30 19:03 (UTC)

fuse2 should be added as a dependency, otherwise there can be an error:

"dlopen(): error loading"

Static_Rocket commented on 2023-11-07 03:42 (UTC) (edited on 2023-11-07 03:44 (UTC) by Static_Rocket)

Would recommend removing the following line as it attempts to break out of the packaging directory and make a dir that is unnecessary now that the udev rule is being properly installed under /usr/lib/udev/rules.d

diff --git a/PKGBUILD b/PKGBUILD                                                      
index 7fa8ed7..6ce946a 100644                                                         
--- a/PKGBUILD                                                                        
+++ b/PKGBUILD                                                                        
@@ -52,7 +52,6 @@ package() {                                                       
     ln -s "/opt/${pkgname}/${pkgname}.AppImage" "${pkgdir}/usr/bin/${_Pkgname}"      

     # Create udev rule                                                               
-    mkdir -p /etc/udev/rules.d                                                       
     install -Dm644 "$srcdir/92-viia.rules" "$pkgdir/usr/lib/udev/rules.d/92-viia.rules"    

You may also want to add fuse as a dependency as AppImages in general need it to function.

dreieck commented on 2023-10-28 08:47 (UTC) (edited on 2023-10-28 08:47 (UTC) by dreieck)

provides=('vial=${pkgver}') is bogous. The environment variable does not get evaluated because of single quotes (this is simple bash workings). You need to replace it with
(double quotes).
Regards and thanks for maintaining!

dreieck commented on 2023-10-25 11:53 (UTC)

Can you add vial=${pkgver} to the provides array and maybe also vial to the conflicts array?

Regards and thanks for maintaining.

pieterv24 commented on 2023-09-08 12:57 (UTC)

@android Did you check if this same issue is present when using the regular appimage and not the aur package?