air-controller-desktop
air-controller-desktop copied to clipboard
AirController launches for a second than crashes with a segfault
Describe the bug AppImage opens up then exits with a segfault. Here is the error left behind:
(air_controller_desktop:36769): Gdk-CRITICAL **: 15:34:19.797: gdk_monitor_get_geometry: assertion 'GDK_IS_MONITOR (monitor)' failed
(air_controller_desktop:36769): Gdk-CRITICAL **: 15:34:19.797: gdk_monitor_get_workarea: assertion 'GDK_IS_MONITOR (monitor)' failed
(air_controller_desktop:36769): Gdk-CRITICAL **: 15:34:19.797: gdk_monitor_get_model: assertion 'GDK_IS_MONITOR (monitor)' failed
(air_controller_desktop:36769): Gdk-CRITICAL **: 15:34:19.797: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
Segmentation fault (core dumped)
To Reproduce
- Download latest AirController AppImage
- Make it executable
- Run app in terminal or file explorer
- See error
OS (please complete the OS information): OS: Arch Linux
App version(please complete the versions information):
- AirController desktop: 0.3.1
Hi, @Seren541 Thank you for your feedback. I can't reproduce this error, could you provide more information about this issue?
When I run Air Controller in gdb, I get the same error, but the application stalls until I force quit it. This is what has changed:
(air_controller_desktop:43305): Gdk-CRITICAL **: 21:50:33.498: gdk_monitor_get_geometry: assertion 'GDK_IS_MONITOR (monitor)' failed
(air_controller_desktop:43305): Gdk-CRITICAL **: 21:50:33.498: gdk_monitor_get_workarea: assertion 'GDK_IS_MONITOR (monitor)' failed
(air_controller_desktop:43305): Gdk-CRITICAL **: 21:50:33.498: gdk_monitor_get_model: assertion 'GDK_IS_MONITOR (monitor)' failed
(air_controller_desktop:43305): Gdk-CRITICAL **: 21:50:33.498: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed
Thread 1 "air_controller_" received signal SIGSEGV, Segmentation fault.
0x00007ffff4f6ff7d in ?? () from /usr/lib/libc.so.6
Can't really debug without the -g flag being attached to whatever executables are being ran within your appimage. Same thing happens when I extract your appimage and run the executable itself.
OK,thank you so much