YARC-Launcher
YARC-Launcher copied to clipboard
YARC-Official
Hanging or crashing on startup
YARC fails to start on my system, either crashing or hanging except when run as root, which works as expected. git bisect says the first bad commit is 7b46245d1b5edef9937ec524dceb1eed8f6f873d.
$ uname -a
Linux mint-desktop 5.15.0-131-generic #141-Ubuntu SMP Fri Jan 10 21:18:28 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
Sometimes an assertion fails instead of hanging.
yarc-launcher: tpp.c:83: __pthread_tpp_change_priority: Assertion `new_prio == -1 || (new_prio >= fifo_min_prio && new_prio <= fifo_max_prio)' failed.
And rarely segfaulting, but I can't get any symbols on the backtrace due to the temporary mount folder being deleted.
Core was generated by `yarc-launcher'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000000003f00000 in ?? ()
[Current thread is 1 (LWP 2271268)]
(gdb) bt
#0 0x0000000003f00000 in ?? ()
#1 0x0000563ee956c6f6 in ?? ()
#2 0x0000563f00353c70 in ?? ()
#3 0x0000000000000001 in ?? ()
#4 0x0000563f00353c70 in ?? ()
#5 0x0000563ee956ce22 in ?? ()
#6 0x0000563f00463810 in ?? ()
#7 0x0000563f00463888 in ?? ()
#8 0x0000000000000073 in ?? ()
#9 0x0000563ee9589a4e in ?? ()
#10 0x0000563f00353c70 in ?? ()
#11 0x0000563ee957aaa3 in ?? ()
#12 0x0000563eea747476 in ?? ()
#13 0x6c96bad958999200 in ?? ()
#14 0x0000563f00463800 in ?? ()
#15 0x0000000000000000 in ?? ()
When running inside GDB there's a large number of threads being created and dying when the program hangs. I ran the program a few times, and any time I could send an interrupt, the program was inside a futex lock or wait routine.
GDB log
$ gdb bin/yarc-launcher_1.0.2_amd64.AppImage
Reading symbols from bin/yarc-launcher_1.0.2_amd64.AppImage...
(No debugging symbols found in bin/yarc-launcher_1.0.2_amd64.AppImage)
(gdb) r
Starting program: /home/lazula/bin/yarc-launcher_1.0.2_amd64.AppImage
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 624569]
process 624566 is executing new program: /usr/bin/env
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
process 624566 is executing new program: /usr/bin/bash
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 624574]
[Detaching after fork from child process 624576]
[Detaching after fork from child process 624577]
process 624566 is executing new program: /tmp/.mount_yarc-lYnDFHZ/AppRun.wrapped
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
process 624566 is executing new program: /tmp/.mount_yarc-lYnDFHZ/usr/bin/yarc-launcher
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffecfce640 (LWP 624609)]
[New Thread 0x7fffe7fff640 (LWP 624610)]
Gtk-Message: 05:58:34.182: Failed to load module "xapp-gtk3-module"
[New Thread 0x7fffe77fe640 (LWP 624611)]
[New Thread 0x7fffe75fd640 (LWP 624612)]
[New Thread 0x7fffe4dfc640 (LWP 624613)]
[New Thread 0x7fff8fffd640 (LWP 624614)]
[Detaching after fork from child process 624615]
[New Thread 0x7fff8d7fc640 (LWP 624616)]
[New Thread 0x7fff8cffb640 (LWP 624617)]
[New Thread 0x7fff87fff640 (LWP 624618)]
[Detaching after fork from child process 624619]
[New Thread 0x7fffe45fb640 (LWP 624620)]
[New Thread 0x7fffe43fa640 (LWP 624621)]
[New Thread 0x7fff8c7fa640 (LWP 624622)]
[New Thread 0x7fff8c5f9640 (LWP 624623)]
[New Thread 0x7fff8c3f8640 (LWP 624624)]
[New Thread 0x7fff877fe640 (LWP 624625)]
[2025-06-05][10:58:34][DEBUG][reqwest::connect] starting new connection: https://releases.yarg.in/
[New Thread 0x7fff875fd640 (LWP 624626)]
Gtk-Message: 05:58:34.554: Failed to load module "xapp-gtk3-module"
[Thread 0x7fff8cffb640 (LWP 624617) exited]
[Thread 0x7fff875fd640 (LWP 624626) exited]
[Thread 0x7fff87fff640 (LWP 624618) exited]
[Thread 0x7fffe75fd640 (LWP 624612) exited]
^C
Thread 1 "yarc-launcher" received signal SIGINT, Interrupt.
Register Information
rax 0xfffffffffffffe00 -512
rbx 0x5555573c65d0 93825024157136
rcx 0x7ffff12202c0 140737238926016
rdx 0x2 2
rsi 0x80 128
rdi 0x5555573bb090 93825024110736
rbp 0xffffffffffffff88 0xffffffffffffff88
rsp 0x7fffffffa478 0x7fffffffa478
r8 0x0 0
r9 0x0 0
r10 0x0 0
r11 0x282 642
r12 0x555557486e00 93825024945664
r13 0x555557486e70 93825024945776
r14 0x0 0
r15 0x555557486e00 93825024945664
rip 0x7ffff12202c0 0x7ffff12202c0 <__GI___lll_lock_wait+48>
eflags 0x282 [ SF IF ]
cs 0x33 51
ss 0x2b 43
ds 0x0 0
es 0x0 0
fs 0x0 0
gs 0x0 0
Execution Context
=> 0x7ffff12202c0 <__GI___lll_lock_wait+48>: cmp rax,0xfffffffffffff000
0x7ffff12202c6 <__GI___lll_lock_wait+54>: jbe 0x7ffff122029e <__GI___lll_lock_wait+14>
0x7ffff12202c8 <__GI___lll_lock_wait+56>: add eax,0xb
0x7ffff12202cb <__GI___lll_lock_wait+59>: cmp eax,0xb
0x7ffff12202ce <__GI___lll_lock_wait+62>: ja 0x7ffff12202db <__GI___lll_lock_wait+75>
0x7ffff12202d0 <__GI___lll_lock_wait+64>: mov edx,0x881
0x7ffff12202d5 <__GI___lll_lock_wait+69>: bt rdx,rax
0x7ffff12202d9 <__GI___lll_lock_wait+73>: jb 0x7ffff122029e <__GI___lll_lock_wait+14>
Local Variables
__ret = -512
err = <optimized out>
err = <optimized out>
__ret = <optimized out>
resultvar = <optimized out>
__arg4 = <optimized out>
__arg3 = <optimized out>
__arg2 = <optimized out>
__arg1 = <optimized out>
_a4 = <optimized out>
_a3 = <optimized out>
_a2 = <optimized out>
_a1 = <optimized out>
futex_wait (private=0, expected=2, futex_word=0x5555573bb090) at ../sysdeps/nptl/futex-internal.h:146
146 ../sysdeps/nptl/futex-internal.h: No such file or directory.
Wow, you're still running on the 5.15 kernel? Can't fault you for a stable kernel.
I'm encountering the same issue. YARG launcher works just fine when running the appimage as root, but totally hangs and doesn't provide any feedback when running as a normal user.
Running Linux Mint 22.1 on kernel 6.8.0-71
Likely still related to issue #45 , the fix provided there with a complete system reinstall is NOT in my cards. I haven't touched my gtk systems, so I don't see why the launcher would be having a rough time.
