There's still something wrong with the build. It's outside of my direct control (I think), but I just submitted a bug report with the details. The fix should be pretty simple, so hopefully it will be updated soon.
It should install now with the nightlies on Ubuntu Mate 32 bit. If by chance you were on a 64 bit, there was a problem with the 64 bit build, so maybe tomorrow for that.
FYI, as I was afraid of, the driver isn't working with PTP mode the way it was compiled, so stick with MSC mode for now. The main advantage of PTP mode so far appears to be live view, anyway. I'll have to see again if I can figure out what's different in the way it gets compiled on Raspbian versus Ubuntu Mate.
I tested the driver but unfortunately it kept crashing, it looks like its missing a file "Driver indi_pentax: indi_pentax: error while loading shared libraries: libRicohCameraSDKCpp.so: cannot open shared object file: No such file or directory"
I was able to get the camera to connect successfully once i installed the SDK, however i was not able to take any pictures successfully. I tried 1 second and 31 second images in bulb mode each time the shutter opened and closed immediately, and finished exposure prior to the end of the 31 second limit. When i tried in manual mode the shutter would fire but then would not close and failed to download. I tried a 3rd attempt in Bulb mode at 60 seconds and noticed that the countdown timer did not go above 30. Its like it does not recognize that the camera is in bulb mode.
Thanks for testing it out, Lenny. It looks to me like it never recognized you were in bulb mode. And then the camera looks like it got into a weird state. I think we had a similar problem on K3II. I wish I had something besides the K-70 to test with.
I'm not sure how much additional testing you're up for, but if you have some time, it'd help to know:
1) Can you check to see if it downloaded any images to your device? The log seemed to indicate it did, but of course that doesn't necessarily mean anything.
2) If you start the driver in M mode, and never switch to another mode, what are the results?
3) If you haven't already, could you by chance download pktriggermode by itself and let me know how that works with your camera? The driver is just wrapping the code for pktriggermode, so if you've used pktriggermode before and it worked, then we're having a driver problem. Otherwise, there's a fundamental problem with pktriggermode, and there may not be much I can do.
If you can respond to those questions, I can spend some time this weekend updating the driver a bit so it can spit out more helpful debug information.
I should mention that when the camera gets into a weird state, sometimes you have to pull all power (i.e. take out the battery) before it will behave normal again--turning it off is not enough. So for #2, what I'm looking to find out is what happens if you start totally clean with both the driver and the camera in M mode.