-
-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error running Beyond All Reason thru flatpak on m1 #1367
Comments
Also there’s a bug with flatpak you might want to install with —arch to get the x86 package instead of the aarch64 one flathub/flathub#2755 |
This cpu longjmp error happens on the x86 version of ballz too |
I don't understand. Are you using qemu or box64 there? |
I’m not sure if flatpak comes with qemu and uses that by default but what I did was I compiled and installed box64 since its not packaged right for the m1 on fedora and then did flatpak install —arch=x86_64 |
I understand, but that error looks like a qemu assert to me. Do you see any box64 logs happening what you launch your stuffs? |
No that’s what confused me too I read somewhere it should just work but maybe flatpak doesn’t use binfmt the same way I was thinking it might be more useful for risc v since most flatpaks already have an aarch64 version but I don’t have a board to test on |
Check with flatpak maintainer how it works maybe? Also maybe related to #1361 altho that's for the "static build" of box64 that doesn't have opengl / vulkan support so probably not what you need here. |
Yup fedora comes with qemu user by default I’ll close this since it’s not a box64 issue |
I’ve make installed and restarted the service but flatpak can’t run bar
**$XDG_DATA_HOME "$ @"
ERROR:../accel/tcg/cpu-exec.c:532:cpu_exec_longjmp_cleanup: assertion failed: (cpu == current_cpu)
Bail out! ERROR:../accel/tcg/cpu-exec.c:532:cpu_exec_longjmp_cleanup: assertion failed: (cpu == current_cpu)
/app/bin/run.sh: line 6: 34 Trace/breakpoint trap (core dumped) zypak-wrapper.sh /app/main/beyond-all-reason --disable-launcher-update -w
The text was updated successfully, but these errors were encountered: