Anyone running the simulator on Arch Linux?

Hello. I just ordered my first Garmin watch and i want to start developing apps.

I installed the SDK and the VS code plugin and they work fine.

I can build the prg, but i can't launch it with the simulator.

When i try to run it, it prints "Unable to connect to simulator.".

I tried running the simulator manually, which i found in the following path ".Garmin/ConnectIQ/Sdks/{SDK_VERSION}/bin/",

but it immediately segfaults:

20:34:04: Debug: Adding duplicate image handler for 'JPEG file'
[1]    357496 segmentation fault (core dumped)  ./simulator

I have tried different versions (7.0.2 Beta, 6.4.2, 4.2.4), but it's always the same.

Has anyone got any idea why this is happening?

Thank you.

0 jotamudo over 1 year ago

Got the same experience, spent the last 5 hours setting up a docker container (https://github.com/waterkip/connectiq-sdk-docker) and fixing it up for the development, but the simulator doesn't connect to my NRF52DK, so I've given up for now. I'd love some suggestions

0 jotamudo over 1 year ago

0 7863591 over 1 year ago in reply to jotamudo

I'm in the exact same situation as you my friend. cant get https://github.com/waterkip/connectiq-sdk-docker running. when i use the compose the container immediately stops with exit code 0. when running it from bash can you share your fixes on github.
do i need to setup the sdk manager in my host system?

0 heimerzieher over 1 year ago

I ran exactly into the same issue with the same segfault message and managed to fix it on my machine. debugging with gdb showed that the segfault occurs in TT_New_Context() which pointed towards an issue with the fonts. I use Gnome. What fixed the problem: I reset all fonts in Gnome Tweaks to the default ones. Now the simulator works. It seems that the simulator uses gtk 3, so on desktop environments different from Gnome resetting or playing around with the gtk font setting should fix it.

0 jotamudo over 1 year ago in reply to heimerzieher

tried doing the same at the time but didn't really understood at which point the stack trace __actually__ had given up. Gonna try that next time I'm cursed into using this tooling

0 GDask over 1 year ago in reply to heimerzieher

In the end I managed to run it by installing Ubuntu on a VM and running it there. If I remember correctly, while I was trying to run it on Arch i guessed it needed an older version of a gtk library. I tried installing it but there was some conflict and I just gave up