There's nothing obvious that I can see in the log. You have focus, scheduler, capture and guiding all active at around the time. These segfaults are hard to diagnose unless you can catch where it is in debug at the time. I run focus at bin 2 but usually capture at bin 1 so if this is related to the problem it must be an edge case. Still, if you think its related you could try focus at bin 1 and see if you still get the issue.

Worth putting verbose mode on in the logging for the active modules to see if you can capture any more clues, and consider running kstars under some form of debugger (if you are able to).

Read More...