X11 Crash under Linux (Debian 12)

RobertPHeller

I am getting this error:

heller@debian:~$ ./Digital_Character_Sheet_3-v1-Demo.AppImage

(Digital_Character_Sheet_3-v1-Demo.AppImage:5462): Gdk-ERROR **: 15:42:46.865: The program 'Digital_Character_Sheet_3-v1-Demo.AppImage' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
(Details: serial 180 error_code 10 request_code 130 (MIT-SHM) minor_code 1)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap

(This is in a minimal x86_64 Debian 12 VM hosted on a Raspberry Pi5 running ARM64 Debian 12)

MrNate

Interesting! Thanks for the report. Does it allow you to run it as sudo?

Your setup is definitely unorthodox. If I'm understanding correctly, you're running Debian 12 ARM64 on the RPi hardware, you're running a virtual machine image of Debian 12 x86_64 on top of it.

From what I can tell, it seems like the AppImage doesn't like that it's trying to run on the virtual memory of the VM. What VM software are you using?

You might try this command:
sudo QT_X11_NO_MITSHM=1 ./Digital_Character_Sheet_3-v1-Demo.AppImage

RobertPHeller

MrNate I did --appimage-extract and ran the program that way and it works that way. I wanted to compare your program with my RolePlayingDB3.

RobertPHeller

I am just using qemu-system-x86_64 directly from the command line with a LVM volume:

marchhare% less -X Debian12amd64.sh
#!/bin/bash
qemu-system-x86_64 \
-machine type=q35 \
-smp 2 \
-drive if=ide,driver=raw,file=/dev/MarchHare/Debian12amd64 \
-netdev bridge,br=qemubr0,id=n1 \
-device virtio-net,netdev=n1,mac=52:54:98:76:54:32 \
-m 2G \
-vga virtio \
-usb \
-device usb-tablet \
-display none

-cdrom debian-12.6.0-amd64-netinst.iso \

-display gtk

RobertPHeller

Running "QT_X11_NO_MITSHM=1 ./Digital_Character_Sheet_3-v1-Demo.AppImage" also works.

MrNate

Great!

I'm happy to hear your feedback once you've had a chance to play around.

RobertPHeller

The only working Intel-flavored system on my LAN is an older MacBook Pro. Everything is some flavor of ARM. My AMD desktop system's motherboard died (after well over 10 years of 24/7 operation). It was cheaper to just get a Pi 5 then a new motherboard, processor, and memory.

MrNate

I do have a mostly working mac build. However that one I only send out by explicit request because it feels janky.

RobertPHeller

I only use the Mac for Zoom, Teams, and as a build box for MacOSX targets. Have you considered creating ARM/ARM64 linux AppImages?

MrNate

RobertPHeller

Honestly I haven't. I've not spent the time to research if compiling to that target would just work, or throw in a whole bunch of work for almost no benefit.

RobertPHeller

I have found that if something builds for linux-x86 it will also build for linux-x86_64, linux-arm, and linux-aarch64. Esp. if the "linux" is the same distro/version (or pretty close to the same distro/version -- eg close vintages of Raspbian and Debian and Ubuntu and Armbian -- eg with closely matching library versions). Linux is Linux. The only gotchas would be something that digs into the kernel or something like that. If is just "standard" user-mode using standard libraries, things just work, with the only issues being way out of date library or compiler versions. And with QEMU, you don't even need physical build boxes.