ptitSeb
Wine AppImage Won't Run, Missing Syscall
I am attempting to run the Wine AppImage from a PineTab2 running ALARM.
I downloaded the AppImage from https://github.com/mmtrt/WINE_AppImage/releases. I am using 9.12-devel.
I am seeing the following error.
~/Downloads/wine-devel_9.12-x86_64.AppImage
Dynarec for ARM64, with extension: ASIMD AES CRC32 PMULL SHA1 SHA2 PageSize:4096 Running on Cortex-A55 with 4 Cores
Params database has 38 entries
Box64 with Dynarec v0.2.6 ddd62a1 built on Jan 2 2024 15:24:27
BOX64: Detected 48bits at least of address space
Counted 76 Env var
BOX64 LIB PATH: ./:lib/:lib64/:x86_64/:bin64/:libs64/:/lib/x86_64-linux-gnu/:/usr/lib/x86_64-linux-gnu/
BOX64 BIN PATH: ./:bin/:/home/thwright/bin/:/usr/local/sbin/:/usr/local/bin/:/usr/bin/:/var/lib/flatpak/exports/bin/:/usr/lib/jvm/default/bin/:/usr/bin/site_perl/:/usr/bin/vendor_perl/:/usr/bin/core_perl/:/var/lib/snapd/snap/bin/:/home/thwright/.local/bin/:/home/thwright/bin/
Looking for /home/thwright/Downloads/wine-devel_9.12-x86_64.AppImage
Rename process to "wine-devel_9.12-x86_64.AppImage"
Error: Unsupported Syscall 0x13h (19)
My apologies for the delay. I just built the latest source on a PineTab2.
I am now seeing the following error.
./wine-devel_9.12-x86_64.AppImage -v
Dynarec for ARM64, with extension: ASIMD AES CRC32 PMULL ATOMICS SHA1 SHA2 PageSize:4096 Running on Cortex-A55 with 4 Cores
Will use Hardware counter measured at 24.0 MHz emulating 3.0 GHz
Params database has 90 entries
Box64 with Dynarec v0.3.1 1978ec8b built on Sep 19 2024 22:05:34
BOX64: Detected 48bits at least of address space
Counted 31 Env var
BOX64 LIB PATH: BOX64 BIN PATH: ./:bin/:/home/thwright/bin/:/usr/local/sbin/:/usr/local/bin/:/usr/bin/:/var/lib/flatpak/exports/bin/:/usr/lib/jvm/default/bin/:/usr/bin/site_perl/:/usr/bin/vendor_perl/:/usr/bin/core_perl/:/var/lib/snapd/snap/bin/:/home/thwright/.local/bin/:/home/thwright/bin/
Looking for ./wine-devel_9.12-x86_64.AppImage
argv[1]="-v"
Rename process to "wine-devel_9.12-x86_64.AppImage"
Error: Unsupported Syscall 0xA5h (165)
4553|SIGSEGV @0x34feb638 (???(./wine-devel_9.12-x86_64.AppImage+0x7eb638)) (x64pc=0x453cd2/"/home/thwright/Downloads/wine-devel_9.12-x86_64.AppImage + 0x53cd2", rsp=0xffff821f8bd8, stack=0xffff81a00000:0xffff82200000 own=(nil) fp=0x4630f7), for accessing 0x28 (code=1/prot=0), db=(nil)((nil):(nil)/(nil):(nil)/???:clean, hash:0/0) handler=(nil)
RSP-0x20:0x0000000000000000 RSP-0x18:0x0000000060000a80 RSP-0x10:0x0000000000000022 RSP-0x08:0x0000000060000550
RSP+0x00:0x0000000000457c4a RSP+0x08:0x0000000000000002 RSP+0x10:0x0000ffff821ff190 RSP+0x18:0x0000ffff821f8d58
RAX:0x000000000046bd80 RCX:0xfefefefeff3f1b00 RDX:0x0000000000492da8 RBX:0x0000000000000000
RSP:0x0000ffff821f8bd8 RBP:0x00000000004630f7 RSI:0x0000000000000000 RDI:0x0000000000000002
R8:0xfefefefefefefeff R9:0xfefefefefefefeff R10:0x000000000000000e R11:0x0000000000000000
R12:0x0000ffff821f8d58 R13:0x0000ffff821fe158 R14:0x000000000048f0c0 R15:0x0000ffff821fc158
ES:0x002b CS:0x0033 SS:0x002b DS:0x002b FS:0x0043 GS:0x0053 x64opcode=48 8B 76 28 0F B7 3C 78 (opcode=f9400341)
Segmentation fault (core dumped)
It looks like this may be another unsupported syscall:
Error: Unsupported Syscall 0xA5h (165)
Here is the coredump:
PID: 4553 (wine-devel_9.12)
UID: 1000 (thwright)
GID: 1000 (thwright)
Signal: 11 (SEGV)
Timestamp: Thu 2024-09-19 23:00:28 EDT (5min ago)
Command Line: ./wine-devel_9.12-x86_64.AppImage -v
Executable: /usr/local/bin/box64
Control Group: /user.slice/user-1000.slice/session-4.scope
Unit: session-4.scope
Slice: user-1000.slice
Session: 4
Owner UID: 1000 (thwright)
Boot ID: b144b94c31cb46258601504bc3478de0
Machine ID: 44d8ff32182c42e9a6ae9921b43ba429
Hostname: thw-pt2.m.redemption.studio
Storage: /var/lib/systemd/coredump/core.wine-devel_9\x2e12.1000.b144b94c31cb46258601504bc3478de0.4553.1726801228000000.zst (present)
Size on Disk: 177.1K
Message: Process 4553 (wine-devel_9.12) of user 1000 dumped core.
Module /home/thwright/Downloads/wine-devel_9.12-x86_64.AppImage without build-id.
Stack trace of thread 4553:
#0 0x0000000034feb638 Run (box64 + 0x7eb638)
#1 0x0000000034a0cf4c emulate (box64 + 0x20cf4c)
#2 0x0000000034a07140 main (box64 + 0x207140)
#3 0x0000ffff82408294 n/a (libc.so.6 + 0x28294)
#4 0x0000ffff82408378 __libc_start_main (libc.so.6 + 0x28378)
#5 0x0000000034a071b0 _start (box64 + 0x2071b0)
ELF object binary architecture: AARCH64
^[[B^[[BGNU gdb (GDB) 15.1
…
Reading symbols from /usr/local/bin/box64...
^[[B
warning: BFD: warning: /var/tmp/coredump-pQ7NIZ: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010001
warning: BFD: warning: /var/tmp/coredump-pQ7NIZ: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010002
[New LWP 4553]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `./wine-devel_9.12-x86_64.AppImage -v '.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 Run (emu=emu@entry=0x4d18d4c0, step=<optimized out>, step@entry=0) at /home/thwright/Dev/box64/src/emu/x64run.c:770
770 GD->q[0] = ED->q[0];
Ok, I have added that syscall.
(it's strange that you get all those error, I run many AppImage without already)
I built the latest. Now when I run it, I see the following. It just hangs here, never completing the call to report the wine AppImage's version or the help information, as examples.
Dynarec for ARM64, with extension: ASIMD AES CRC32 PMULL ATOMICS SHA1 SHA2 PageSize:4096 Running on Cortex-A55 with 4 Cores
Will use Hardware counter measured at 24.0 MHz emulating 3.0 GHz
Params database has 91 entries
Box64 with Dynarec v0.3.1 6e0b5358 built on Oct 6 2024 21:07:42
BOX64: Detected 48bits at least of address space
Counted 73 Env var
BOX64 LIB PATH: BOX64 BIN PATH: ./:bin/:/home/thwright/bin/:/usr/local/sbin/:/usr/local/bin/:/usr/bin/:/var/lib/flatpak/exports/bin/:/usr/lib/jvm/default/bin/:/usr/bin/site_perl/:/usr/bin/vendor_perl/:/usr/bin/core_perl/:/var/lib/snapd/snap/bin/:/home/thwright/.local/bin/:/home/thwright/bin/
Looking for /home/thwright/Downloads/wine-staging_9.16-x86_64.AppImage
argv[1]="--version"
Rename process to "wine-staging_9.16-x86_64.AppImage"
Warning, CALL to 0x0 at 0x401efd (0x401efc)
Any thoughts on what I can test to debug this further?
AppImages tend to be silent on what is happening inside the container. Maybe try to extract the image with --appimage-extract and run the software dirrectly from the exracted squashfs-root/ folder and see if you have more message?
Will do. Attempted to extract on the device and got a missing syscall:
./wine-staging_9.16-x86_64.AppImage --appimage-extract
Dynarec for ARM64, with extension: ASIMD AES CRC32 PMULL ATOMICS SHA1 SHA2 PageSize:4096 Running on Cortex-A55 with 4 Cores
Will use Hardware counter measured at 24.0 MHz emulating 3.0 GHz
Params database has 91 entries
Box64 with Dynarec v0.3.1 6e0b5358 built on Oct 6 2024 21:07:42
BOX64: Detected 48bits at least of address space
Counted 31 Env var
BOX64 LIB PATH: BOX64 BIN PATH: ./:bin/:/home/thwright/bin/:/usr/local/sbin/:/usr/local/bin/:/usr/bin/:/var/lib/flatpak/exports/bin/:/usr/lib/jvm/default/bin/:/usr/bin/site_perl/:/usr/bin/vendor_perl/:/usr/bin/core_perl/:/var/lib/snapd/snap/bin/:/home/thwright/.local/bin/:/home/thwright/bin/
Looking for ./wine-staging_9.16-x86_64.AppImage
argv[1]="--appimage-extract"
Rename process to "wine-staging_9.16-x86_64.AppImage"
Warning, CALL to 0x0 at 0x401efd (0x401efc)
Warning, CALL to 0x0 at 0x40d515 (0x40d514)
squashfs-root/.DirIcon
Error: Unsupported Syscall 0x58h (88)
I'm extracting it on an x86_64 machine and will sync it over to test it further.
EDIT 20241126: I haven't been able to test this heavily. I did play around with extracting the appimage on x86_64 and syncing it over but I have not had any particular success.
A recent attempt at running the wine 9.19 AppImage with a --version resulted in the call hanging, stalling at the same point above as below and never returning the wine version number:
Warning, CALL to 0x0 at 0x401efd (0x401efc)
Attempting to extract 9.19 results in the same unsupported syscall:
Error: Unsupported Syscall 0x58h (88)
There have been some improvments on AppImage handling latelly. Closing the ticket as there has been no activity. Feel free to open a new one if some new issue appear.