Attached is a stack trace.
This is 100% reproducible for me.
I realize it has been discussed before, but I wanted to check if it's possible to look into this without having to trash the userdb.sqlite because that means redoing lots and lots of configs in all modules and for every profile.

Basically I needed a new profile for some tests:
1)Create new profile
2)Connect
-> Expected: Optical trains popup
-> Effective: no Optical trains prompt
3)Switch to Capture or any other module using trains
-> No Train is defined
-> Edit trains button does nothing
4)Try to start a capture
-> Segmentation Fault

Attached is also my sqlite db if Jasem wants to see if there is a case-specific corruption going on.

Nothing super explanatory in the logs, but here's the crash lines

This is still happening. I'm out right now and can't build a new profile I need. If I create a profile without the mount (indi_celestron_gps), it works, as soon as I add a mount, the trains break and if I take an exposure it crashes

Your user database is probably corrupted. Delete (or backup) ~/.local/share/kstars/userdb.sqlite and run KStars again.

Hi Jasem,
Tried and didn't solve the issue, however I found a way to reproduce AND solve it: if I disable "Port selector" for the profile, Trains are invoked and work correctly. If port selector is active, celestron driver inhibits recall of the correct train and new profiles don't get the first start train dialog.
Either removing the mount from the profile OR disabling port selector solve the issue