On Friday, May 12, 2017 8:19:46 PM EDT Jan Ritzerfeld wrote:
Am Mittwoch, 10. Mai 2017, 13:48:53 CEST schrieb Dennis Gallien:
Regrettably, I have to report that apparently libgphoto2 is again not working with the iPhone 6S, or perhaps more accurately stated, the recent update to iOS 10.3. As before, the phone is recognized and the store_interface folder is loaded, but the DCIM folder is not seen.
You mean "store_feedface"? This folder is shown if the iPhone is not unlocked. And ObsidianParis from github and me verified that the fix works with iOS 10.3.1.
I had been successfully using the interim version provided by Jan. Then I updated libgphoto2 from the Main Update Repository to version 2.5.13-2.3.1 shortly following its release in mid-April. A week or two later iOS 10.3 was released. I had not tried to upload photos after the new libgphoto2 release but before the iOS 10.3 update so I can't say whether Jan's version would have worked with 10.3 or not. Jan's version is no longer available, so I can't go back to test it.
I removed my repository in March because there was (and still is) an officially fixed libgphoto2-6 version in http://download.opensuse.org/repositories/graphics/openSUSE_Leap_42.2/ Someone on the opensuse-de mailing list confirmed that it works since libgphoto2-6 2.5.12.1-180.1.
However, since libgphoto2-6 2.5.13 you have installed contains the fix, it is very odd that it does not work anymore.
From the other messages in the previous thread on this, it appears there has been an on-going problem with iOS updates. Likely that this has occurred again?
I just tested it with libgphoto2-2.5.13-183.1 from the above mentioned graphics repository and iOS 10.3.1: I can still access my photos after unlocking the phone.
Gruß Jan
Thanks very much for the reply, Jan. After the 10.3.1 upgrade I attempted the upload multiple times with no success. I suspect that the problem was indeed that the phone was not unlocked. I have noticed though that the phone does not always ask me to "Trust". Supposedly once unlocked, this does not need to be repeated for the same machine again, but that apparently is not always true. I don't know how to unlock the phone once it is not unlocked through the "Trust" interface. In any event, I updated the phone yesterday to 10.3.2, and now it is working again. It did not ask me to Trust. But it must be unlocked. So I'm very baffled by the inconsistent behavior by the phone. Grrrr! --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org