I installed gphoto2 and it came with the following versions:
gphoto2 2.5.9 gcc, popt(m), exif, no cdk, aa, jpeg, readline
libgphoto2 2.5.14.1 all camlibs, gcc, ltdl, EXIF
libgphoto2_port 0.12.0 gcc, ltdl, USB, serial without locking

I had the impression that all was more stable after having run the sudo apt-get install gphoto2, but just before writing this reply the camera was hanging again.
I created 2 sequences to be run one after the other. The first was 5s exposure with ISO 800 followed by 1s and ISO 1600. Running one after the other I heard the 5s mirror flipping and the 1s mirror flip but the ISO setting did not change and remained on 800. Further I also noticed that the frame displayed after changing the ISO was the last frame taken and not the new one taken with the new ISO value. Could it be that the buffer is not emptied?

Stefan

You're the second person today to point out this problem with the K-5. Dang, hope its not a GPhoto2 problem because that guy is pretty busy!

Actually this issue not only happen on Pentax users. indilib.org/forum/ekos/3195-darks-frames-same-as-lights.html

I already told Jasem about this issue. Maybe my english is not up to his standard to understand. I hope someone with better english can report this issue to him.

Regards,
Tom

Debug logs are required when reporting issues. These things are quite complex as you can imagine, I cannot make an assessment (usually) alone from the description of the problem. I don't know why sometimes it returns the _last_ image. If anything in the logs looks funny when this happen, then this would be a place to start investigating. I'll see if there is a way to clear _everything_ whenever a capture is taken as well.

I made a small modification to the GPhoto driver where it now deletes the complete folder to ensure there are no ghost images left behind. Not sure if this would really solve anything. Only way to find out is for those who reported this issue must test it. Either compile the code from GIT, or use the Nightly PPA to get it. Make sure debug logging is turned on!!

I upgraded before starting and must state the the situation is more stable.
Two sequences have been defined with different ISO. The first sequence works fine but the frame is showed in the viewer before the next frame is taken. I have the impression the frames are not saved. After the first sequence, the ISO setting has been changed and communicated to the DSLR. This did not work before. The second sequence is launched but no frames are shown in the viewer.
This time I attach the log.
The gphoto2 version is as follows:
gphoto2 2.5.9 gcc, popt(m), exif, no cdk, aa, jpeg, readline
libgphoto2 2.5.16.1 all camlibs, gcc, ltdl, EXIF
libgphoto2_port 0.12.0 iolibs: disk ptpip serial usb1 usbdiskdirect usbscsi, gcc, ltdl, USB, serial without locking

You forgot to attach.

First of all, thanks Jasem. After upgraded to new version of kstars, I am now using the Pentax DSLR option but not the Gphoto CCD option. So, my question is do I need to switch back to gphoto CCD just to test out your small modification?

Regards,
Tom

Sorry Jasem, here it is.
After some reflection, during the execution of a sequence, the frame is shown in the viewer leaving the option to save or not, but the dialogue does not wait until you reply. As a consequence, frames are not saved at all. Is this normal? I have not understood why watching a frame in the viewer is not an option. When you do not take the option, frames are just saved in a predefined directory.

Pentax DLSR option??? what's that?

Good question. Does that mean that today beside Canon and Nikon DSLR drivers we have now also a Pentax DSLR driver?

In the latest 2.9.4, Pentax DSLR option already in the list. Now Jasem is fixing the ghost image issue but only available in nightly build which I am using it now.