I have an issue with Ekos using sequences.
If you take a sequence of images, delete the sequence and add another one, Ekos crashes when it starts capturing the second sequence images.

Anyone with the same symptoms? This also happens with simulators.

Can't reproduce the crash. Can you run KStars again via gdb and post the traceback after the crash occurs?

Yes here is the gdb output, but i think it does not give any clue, it just quits without indication of a crash, thats odd:

astro@astro-MacBookPro:~$ gdb --eval-command="set follow-fork-mode child" --args kstars
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kstars...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/kstars
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe30a3700 (LWP 2289)]
[New process 2292]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
process 2292 is executing new program: /usr/bin/python2.7
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Inferior 2 (process 2292) exited normally]
(gdb) Found one coordinate representation.

and this one is indi_simulator_ccd via gdb:

astro@astro-MacBookPro:~$ gdb --eval-command="set follow-fork-mode child" --args indiserver -v indi_simulator_ccd
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from indiserver...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/indiserver -v indi_simulator_ccd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
2016-09-16T06:49:44: startup: /usr/bin/indiserver -v indi_simulator_ccd
[New process 2483]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
2016-09-16T06:49:44: Driver indi_simulator_ccd: pid=2483 rfd=3 wfd=6 efd=7
2016-09-16T06:49:44: listening to port 7624 on fd 4
process 2483 is executing new program: /usr/bin/indi_simulator_ccd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
2016-09-16T06:49:44: Driver indi_simulator_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2016-09-16T06:49:44: Driver indi_simulator_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2016-09-16T06:49:44: Driver indi_simulator_ccd: snooping on CCD Simulator.FILTER_SLOT
2016-09-16T06:49:44: Driver indi_simulator_ccd: snooping on CCD Simulator.FILTER_NAME
2016-09-16T06:49:44: Driver indi_simulator_ccd: snooping on Telescope Simulator.EQUATORIAL_PE
2016-09-16T06:49:44: Driver indi_simulator_ccd: snooping on Focuser Simulator.FWHM

I guess it's something specific on my PC as I can't reproduce it too on a x86-64 ubuntu mate VM.
I will try to investigate some more.

Yes, it happened to me too last week when I did a number of darks and after finishing I wanted to run a second sequence with a different chip temperature. I deleted all old sequence entries, changed the temp, waited to settle and then added new sequence entries but KStars became unresponsive and finally I killed the process. Unfortunately, I haven't it running in debug mode.

EDIT: To be more precise: Before creating a new sequence I stored the current one to a sequence file.

EDIT: Just made an update form the ppa and checked with the simulators but found no issues so far. Will keep an eye on it.

CS
Klaus

I have just updated and tried again. The problem is gone but I dont' know the cause.