track-o-bot crashes when Hearthstone starts

[b-or-q]

Hey there,

when I run track-o-bot the app seems to start fine and looks okay. However when I start Hearthstone by using the battle.net launcher track-o-bot crashes. I get this log in journalctl:

Process 8888 (Track-o-Bot) of user 1000 dumped core.

Stack trace of thread 8888:
#0  0x00007fd7283e6a10 raise (libc.so.6)
#1  0x00007fd7283e813a abort (libc.so.6)
#2  0x00007fd7283df607 __assert_fail_base (libc.so.6)
#3  0x00007fd7283df6b2 __assert_fail (libc.so.6)
#4  0x00000000004370a3 n/a (Track-o-Bot)
#5  0x0000000000436941 n/a (Track-o-Bot)
#6  0x000000000042636d n/a (Track-o-Bot)
#7  0x0000000000426415 n/a (Track-o-Bot)
#8  0x000000000042b976 n/a (Track-o-Bot)
#9  0x000000000042b5d4 n/a (Track-o-Bot)
#10 0x000000000042a9d3 n/a (Track-o-Bot)
#11 0x00007fd7297660ee _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5)
#12 0x00000000004534b3 n/a (Track-o-Bot)
#13 0x00000000004116b5 n/a (Track-o-Bot)
#14 0x000000000041235d n/a (Track-o-Bot)
#15 0x000000000044815f n/a (Track-o-Bot)
#16 0x0000000000447119 n/a (Track-o-Bot)
#17 0x0000000000411069 n/a (Track-o-Bot)
#18 0x00007fd7283d3511 __libc_start_main (libc.so.6)
#19 0x0000000000410f6a n/a (Track-o-Bot)

Stack trace of thread 8889:
#0  0x00007fd72849567d poll (libc.so.6)
#1  0x00007fd72b2f98e0 n/a (libxcb.so.1)
#2  0x00007fd72b2fb679 xcb_wait_for_event (libxcb.so.1)
#3  0x00007fd721b90239 n/a (libQt5XcbQpa.so.5)
#4  0x00007fd72955f6d8 n/a (libQt5Core.so.5)
#5  0x00007fd7290102e7 start_thread (libpthread.so.0)
#6  0x00007fd72849f54f __clone (libc.so.6)

Stack trace of thread 8890:
#0  0x00007fd72849567d poll (libc.so.6)
#1  0x00007fd72607f9b6 n/a (libglib-2.0.so.0)
#2  0x00007fd72607facc g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007fd72607fb11 n/a (libglib-2.0.so.0)
#4  0x00007fd7260a7295 n/a (libglib-2.0.so.0)
#5  0x00007fd7290102e7 start_thread (libpthread.so.0)
#6  0x00007fd72849f54f __clone (libc.so.6)

Stack trace of thread 8892:
#0  0x00007fd72849567d poll (libc.so.6)
#1  0x00007fd72607f9b6 n/a (libglib-2.0.so.0)
#2  0x00007fd72607facc g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007fd72978f07f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#4  0x00007fd7297388ca _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x00007fd72955aa73 _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x00007fd72955f6d8 n/a (libQt5Core.so.5)
#7  0x00007fd7290102e7 start_thread (libpthread.so.0)
#8  0x00007fd72849f54f __clone (libc.so.6)

Stack trace of thread 8891:
#0  0x00007fd72849567d poll (libc.so.6)
#1  0x00007fd72607f9b6 n/a (libglib-2.0.so.0)
#2  0x00007fd72607fd42 g_main_loop_run (libglib-2.0.so.0)
#3  0x00007fd716c88ff6 n/a (libgio-2.0.so.0)
#4  0x00007fd7260a7295 n/a (libglib-2.0.so.0)
#5  0x00007fd7290102e7 start_thread (libpthread.so.0)
#6  0x00007fd72849f54f __clone (libc.so.6)

Stack trace of thread 8893:
#0  0x00007fd72849567d poll (libc.so.6)
#1  0x00007fd72607f9b6 n/a (libglib-2.0.so.0)
#2  0x00007fd72607facc g_main_context_iteration (libglib-2.0.so.0)
#3  0x00007fd72978f07f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#4  0x00007fd7297388ca _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x00007fd72955aa73 _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x00007fd7216dd125 n/a (libQt5DBus.so.5)
#7  0x00007fd72955f6d8 n/a (libQt5Core.so.5)
#8  0x00007fd7290102e7 start_thread (libpthread.so.0)
#9  0x00007fd72849f54f __clone (libc.so.6)

Stack trace of thread 8895:
#0  0x00007fd729016ca6 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007fd710358e44 n/a (libGLX_nvidia.so.0)
#2  0x00007fd702fd5394 n/a (libnvidia-glcore.so.378.13)
#3  0x00007fd71035812c n/a (libGLX_nvidia.so.0)
#4  0x00007fd7290102e7 start_thread (libpthread.so.0)
#5  0x00007fd72849f54f __clone (libc.so.6)

Any suggestions what can be done in this case?

[b-or-q]

Changing the game language to EN US helped