The Pentax K-5 firmware version is 1.16 (last version).
This morning, when updating and upgrading I saw that indi-gphoto was upgraded.
In order to be sure that the issues were not caused by some settings I changed myself, I reset all settings to factory settings.
When starting the indiserver a warning is shown: [WARNING] Shutter speed widget does not have any valid data (count=0).
The driver name is GPhoto CCD and the Exec is indi_pentax_ccd, version 2.3, interface 10.
I saved a series of capturing sequences in a file for upload when starting.
After uploading the saved sequences and the first start, all sequences go quickly to status complete. The indi_pentax_ccd process continues running.
Resetting the status to Idle for all lines and starting the list of sequences changes the status of the first sequence to "in progress", beside expose an indicator starts turning and the message window opens and informs that the indi_pentax_ccd driver crashed. The indi_pentax_ccd process on the linux machine was initially in a status Sl+ meaning S=uninterruptible sleep, l=is multithreaded and +=is in the foreground process group. After the message that the driver crashed theprocess status was S+ so the multi-threading disappeared.
The driver log did not revealed any issue.
In the KSTARS log the following error appears: INDI Server: "2018-08-05T08:36:36: Driver indi_pentax_ccd: indi_pentax_ccd dispatch error: Property CCD_ABORT_EXPOSURE is not defined in Pentax DSLR K5D 0." from which I deduce that it is not possible to abort the exposure in the PENTAX K5D0. In any case when starting the exposure I would expect the countdown to start and the indicator starts turning.
When disconnecting and reconnecting (without stopping and restarting the indi server) the status of the indi_pentax_ccd process becomes again multi-threaded. Restarting the sequence puts the first sequence again in "in progress" status, the driver does not crash but the linux process is again not multi-threaded anymore, just as the driver would crash but this is not reported.
Remark that after that the driver crashed, the DSLR does not remain blocked. When restarting the indiserver and reconnecting the DSLR the exposure button of the DSLR does not respond when pushing it. The DSLR seems to be under full control of EKOS.

When launching KSTARS under sudo the following error message is printed:

Dispatch command error(-1): INDI: Could not find property CCD_EXPOSURE in GPhoto CCD
<setNumberVector device="GPhoto CCD" name="CCD_EXPOSURE" state="Idle" timeout="60" timestamp="2018-08-05T12:06:38">
<oneNumber name="CCD_EXPOSURE_VALUE" min="0.001" max="3600" step="1">
1
</oneNumber>
</setNumberVector>
Further, I started exploring the command line interface for gphoto2 and this worked marvelously well for my PENTAX K-5, demonstrating that the issues are clearly inside EKOS.

I sent you a private message on how to proceed with this, please check it out.

Jasem, good morning. Could you please drop me a message when the driver is updated? Thanks for the help. Stefan

Come to google chat (in gmail or hangouts).

Ok issue appears fix. Please Pentax & Sony users, test the latest driver in the nightly PPA.

Jasem,
I tested again on the laptop where we corrected yesterday the issues and I do not find any issue. I am confident it is working well.

Because my idea is to connect my gear (mount, guider and DSLR) to my RPi3 as remote indiserver, and run on my laptop KSTARS pointing to the remote mRPi3 for communicating with the instruments, the mount and the guider work perfectly. The DSLR (PENTAX K-5) however not at all. The same issue as we started from yesterday evening. I updated/upgraded from the nightly PPA on the RPi3 but no result.

On the laptop I did not dare updating/upgrading fearing that I would overwrite the modifications we made yesterday.

Will test on my K5IIs and report back later.

My K5Iis is good to go with capture DNG and fits. No problem at all.

Have tried to reinstall on RPi3 as you did on laptop but without success. I can use gphoto2 and set shutterspeed, take pictures and check exiv2 parameters. Setting shutterspeed works for strings of the type '1/100' etc. 2s doesn't work.

Starting indiserver from the command-line gives me for all drivers I intend to use the following error:

2018-08-09T20:42:26: Driver indi_eqmod_telescope: indi_eqmod_telescope: symbol lookup error: indi_eqmod_telescope: undefined symbol: _ZN4INDI9Telescope13ISSnoopDeviceEP8_xml_ele

No logs available in .indi.

Probably an update issue, try to update and install indi-eqmod again.

OK I updated the RPi3 and the driver works now but gives a strange message on stdout, namely:

indiserver -m 100 -p 8000 indi_eqmod_telescope
2018-08-10T18:37:12: startup: indiserver -m 100 -p 8000 indi_eqmod_telescope
2018-08-10T18:37:12: Driver indi_eqmod_telescope: Using prefix /usr/share/indi//indi_eqmod_sk.xml
2018-08-10T18:37:12: Driver indi_eqmod_telescope: Using prefix /usr/share/indi//indi_align_sk.xml
2018-08-10T18:37:12: Driver indi_eqmod_telescope: Using prefix /usr/share/indi//indi_eqmod_simulator_sk.xml
2018-08-10T18:37:12: Driver indi_eqmod_telescope: Using prefix /usr/share/indi//indi_eqmod_scope_limits_sk.xml
2018-08-10T18:37:12: Driver indi_eqmod_telescope: EnumeratePlugins - found plugin SVD Math Plugin
The double / or is a typo somewhere, or there is an issue with a environment variable that should be set and is not. Not nice but not an issue because the driver works.

For the indi_pentax_ccd the situation is different.
I get the following message and the process died and goes to 10 restarts
indiserver -m 100 -p 8000 indi_pentax_ccd
2018-08-10T18:49:56: startup: indiserver -m 100 -p 8000 indi_pentax_ccd
2018-08-10T18:49:56: Driver indi_pentax_ccd: 2018-08-10T18:49:56: Driver indi_pentax_ccd: execlp: No such file or directory
Child process 1388 died
2018-08-10T18:49:56: Driver indi_pentax_ccd: stderr EOF
2018-08-10T18:49:56: Driver indi_pentax_ccd: restart #1
After 10 restarts and every time the same issue indiserver gives up.
So Pentax DSLR on RPi3 is not working at all: He does not find a directory while yesterday the issue was as reported for the eqmod_telescope.
Looking to the previously mentioned aesthetics issue, for the Pentax it may be that the double / makes that a file or directory cannot be found.

I remain online in case there would be a need for more info.
Stefan