[opensuse] Digikam, etc. cannot upload from iPhone 6S
Not sure if this is a KDE or Solid (or other) issue . . . sorry for message length but trying to include all relevant data I know of . . . Digikam has worked great importing/deleting photos from iPhone 6S for a year, working on 13.2. I recently upgraded 13.2 => 42.1 => 42.2 about a month ago. I can't honestly say whether this problem arose with the Leap upgrade, or with an update since. When Digikam opens it displays the following error message: The specified camera ("/org/kde/solid/udev/sys/devices/ pci0000:00/0000:00:12.2/usb1/1-1/1-1:4.2/net/eth2") is not supported. ~>lsusb shows the camera as: Bus 001 Device 002: ID 05ac:12a8 Apple, Inc. Switching to a different port , , , ~>lsusb Bus 004 Device 003: ID 05ac:12a8 Apple, Inc. Digikam then throws this error when started: The specified camera ("/org/kde/solid/udev/sys/devices/ pci0000:00/0000:00:13.2/usb4/4-2/4-2:4.2/net/eth1") is not supported. Yet still Digikam (and other photo apps) autodetects the phone. It is shown under the Import menu, and when Import for the phone is selected the second Digikam windows opens. At bottom it shows the correct camera media capacity and amount used, while under the Device menu it shows the phone is recognized on the correct usb port. It shows that upload and delete are supported functions. But it cannot see the photo files. (It is seen as an "iPhone5 (PTP mode)"; gphoto2 --list-cameras does not show iPhone6 but that was not a problem before; the udev hwdb shows the same phone ID for both iPhone5 and iPhone6. Tested this with my wife's iPhone 5 and the errors were the same.) gphoto2: --list-ports sees the correct port --list-folders sees the "store_feedface" folder but no files. --abilities shows iPhone 5 with USB support, file preview and upload = yes When I try kio camera:/ in Dolphin I get: camera:/Apple%2520iPhone%25205%2520(PTP%2520mode)@usb:001,002/ An "Apple iPhone 5 (PTP Model)" folder appears with the sub-folder "store_feedface" but no DCIM folder nor any photos. When I try gtkam it can see the iPhone "store-feedface" but not DCIM, no files. Experimenting with this app I once got this error, too: An error occurred in the io-library ('Could not claim the USB device'): Could not claim interface 0 (Device or resource busy). Make sure no other program (gvfs-gphoto2-volume-monitor) or kernel module (such as sdc2xx, stv680, spca50x) is using the device and you have read/write access to the device. Similarly, when I tried Shotwell it threw: Unable to fetch previews from the camera: Could not claim the USB device (-53) But strangely, darktable uploads (and deletes) the iPhone files even though it uses libgphoto2.so.6 just as all the other apps do. Still works fine with my Canon A570. Digikam Version 5.4.0 Using: KDE Frameworks 5.26.0 Qt 5.6.1 (built against 5.6.1) My suspicion is that the problem is connect to the error "could not claim USB device", as I've seen that several times. Just a wild-ass guess. I checked Bugzilla KDE and Solid, found multiple instances of PTP cameras being recognized but files not retrievable over the last ~5 years. But nothing recent. I did find a 2011 bug report on Ubuntu Launchpad which was reported again in Dec claiming a regression in Digikam, but it wasn't verified. (And that was Digikam4, not 5). Any suggestions where to look further? Again, apologies for length. TIA, Dennis P.S. KDE folks might want to note that the Device Notifier entry always displays the camera twice rather than just once when it's attached, and when the "Open with File Manager" option is chosen, the app errors on not finding the KDE4 version of Dolphin: KDEInit could not launch 'dolphin4': Could not open library 'libkdeinit5_dolphin4'. Cannot load library libkdeinit5_dolphin4: (libkdeinit5_dolphin4: cannot open shared object file: No such file or directory) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, January 18, 2017 11:01:06 PM EST Jan Ritzerfeld wrote:
Thanks Jan for the pointer to ifuse. I found that too, and it does work. Fwiw, I also got the camera:/ kio slave to work in dolphin by using this kluge: Plug in phone, "Trust" if necessary, open dolphin and enter the kio slave but when the phone folder is displayed do not open it. Open a second dolphin instance and again enter the kio, when the folder is displayed this time it can be opened and instead of the "storefeed" folder you should see a numbered folder inside of which is the DCIM folder. I found this to work most of the time, but not always.
That said, I tested all photo apps that use libgphoto2 to access the photo files. With all, the phone is recognized but the files cannot be seen. libgphoto2 uses different code than the camera:/ kio, so there appears to be an issue with libgphoto2 as well. Thanks again, --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Donnerstag, 19. Januar 2017, 11:20:49 CET schrieb Dennis Gallien:
[...] Thanks Jan for the pointer to ifuse. I found that too, and it does work.
Ah, okay.
Very cool workaround! I will try that next time I need access to my photos
Using a Windows VM, I accidentally clicked on my already trusted iPhone in the Explorer. Then, the iPhone asked me whether I trust this computer explicitly for photos and videos. I have never seen this before and I think that this new kind of trust in 10.2 is simply not supported by libimobiledevice, yet. https://github.com/libimobiledevice/libimobiledevice/issues/445 from https://lists.opensuse.org/opensuse-de/2017-01/msg00305.html Gruß Jan -- Every solution breeds new problems. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Donnerstag, 19. Januar 2017, 11:20:49 CET schrieb Dennis Gallien:
I tested it and it works sometimes. Regarding the different folder names, it looks like the storefeed folder is shown when the iPhone is locked and the other numbered store_... folder when it is unlocked. IIRC I have never been able to access all photos without unlocking the iPhone. Gruß Jan -- Sometimes the fool who rushes in gets the job done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday, January 22, 2017 4:56:56 PM EST Jan Ritzerfeld wrote:
Yes, it must be unlocked. Apparently a problem some have experienced is that the "trust" handshake dialog phone <=> computer doesn't happen. The intended behavior seems to be that once a computer is trusted, it isn't necessary to trust it again. I had to reset my network settings to get this working again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Donnerstag, 19. Januar 2017, 11:20:49 CET schrieb Dennis Gallien:
Are you sure? /usr/share/doc/packages/kio_kamera/README | You need libgphoto 2.4, 2.5 (or later). Maybe it is a problem in libgphoto2? But you said darktable upload and delete the iPhone files... Gruß Jan -- Nobody really knows what is going on anywhere in your organization. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday, January 22, 2017 5:13:00 PM EST Jan Ritzerfeld wrote:
Re the camera:/ kio being different, I probably could have worded that better. What I found in my research - but I didn't take note of the link - stated that the kio was believed to work because it is coded differently. You are correct that the kio and all the camera access apps use libgphoto2. It's conceivable that the kio is using libgphoto2 differently than the apps. I don't know, other than that the kio works and the apps do not. Strangely, when I ran tests again, darktable stopped working like the other. As an aside, it's interesting that the config file libgphoto2 uses to identify cameras by each ID, does not have entries for iPhone 6 or 7. The 6 has the same ID as the 5, which is why the 6 is recognized as a 5. Dunno about the 7. Or even whether this is relevant; just an observation. --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/19/2017 10:20 AM, Dennis Gallien wrote:
This has been a giant game of whatck-a-mole with IOS updates/gphoto2 catchup that's been played since IOS 4 days. Luckily our own Markus Meissner is quite active with gphoto2 and can generally provide additional information as well as help with resolving the problem. You may want to post to the gphoto2 list (gphoto-devel@lists.sourceforge.net) for the best source of information on the issue. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Montag, 16. Januar 2017, 16:45:18 CET schrieb Dennis Gallien:
This is the Ethernet device IIRC used for tethering and obviously not supported. However, solid-hardware5 query "IS Camera" shows the normal iPhone and the eth* here. I think these two "cameras" are the cause for
Gruß Jan -- You are better off not knowing how sausages and laws are made. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Montag, 16. Januar 2017, 16:45:18 CET schrieb Dennis Gallien:
There are some good news. It looks like the underlying libgphoto2 has to be changed to deal with iOS 10.2. Marcus and an apt user already accomplished a lot after me being stumped: https://github.com/gphoto/libgphoto2/issues/132 Now, we are awaiting iOS 10.3. :-D Gruß Jan -- Don't worry if it doesn't work right. If everything did, you'd be out of a job. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday, March 10, 2017 8:06:02 PM EST Jan Ritzerfeld wrote: . . .
Thanks very much Jan for that update. I read the thread and indeed it provides an excellent technical description of what I saw, and explaining the reason for the kio workaround working sometimes but sometimes not - that is, the "3 second delay" issue. I'm copying the KDE list because one of the comments suggests there is at least a possibility that the libgphoto2 fix may not work with other apps than the tested Shotwell or could affect other cameras. Digikam is my preferred photo manager and it is basically useless with this bug. But re the 10.3 issue I'm not holding my breath. It sure is a PITA to have to reset my phone's network settings with every import! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Samstag, 11. März 2017, 12:33:56 CET schrieb Dennis Gallien:
Yes, the other user was a big help sorting that out!
Would you mind trying the patched version of libgphoto2 in my home? Here, Dolphin was able to access the photos again at a first glance: http://download.opensuse.org/repositories/home:/jritzerfeld:/branches:/graph...
But re the 10.3 issue I'm not holding my breath. It sure is a PITA to have to reset my phone's network settings with every import!
We will see ... Gruß Jan -- If all else fails, immortality can always be assured by spectacular error. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday, March 12, 2017 12:07:06 AM EDT Jan Ritzerfeld wrote: . . .
Hot damn!!! Dolphin went right down the iPhone photo folder tree with the camera:/ kio on first attempt. I also tried waiting a while after making the camera connection before going down the tree; apparently no "3 second grace delay" issue, either. And good news on the Digikam side, too. It is able to see and import the photos as it should. Finally, I noticed that the "store_nnnnnnn" folder name is incrementing by one digit each time the phone is accessed again, as I understand it needs to do. Also interesting is that I did not have any problem with the IOS "Trust" function. It is persistent for this computer connection across new phone sessions. Of course if the phone goes to sleep the connection must be re- initiated before it can be accessed again; when that happens the "store" folder still increments. AFAICT, libphoto2 works! Thanks for all the great help, Jan! --Dennis Gallion SuSE since 7.0 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Sonntag, 12. März 2017, 12:16:01 CET schrieb Dennis Gallien:
Interesting indeed. Our trust "issues" seem to have been a red herring.
Then and when, while the phone is awake and unlocked, a session is closed and reopened more than 3 seconds later. Maybe they fixed an unknown exploit in iOS 10.2.
AFAICT, libphoto2 works!
Fine. And Marcus thinks about releasing the next libgphoto2 version as an update.
Thanks for all the great help, Jan!
Don't praise the messenger! Thank Marcus and ObsidianParis. Gruß Jan -- Mediocrity thrives on standardization. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. 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. 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? Also as was suggested here previously, I've copied the gphoto-devel mailing list to alert Markus to this problem. --dg On Sunday, March 12, 2017 5:38:37 PM EDT Jan Ritzerfeld wrote:
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Mittwoch, 10. Mai 2017, 13:48:53 CEST schrieb Dennis Gallien:
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 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.
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 -- There are two reasons for doing things, a very good reason and the real reason. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday, May 12, 2017 8:19:46 PM EDT Jan Ritzerfeld wrote:
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
Am Sonntag, 21. Mai 2017, 15:34:24 CEST schrieb Dennis Gallien:
Glad to hear!
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!
However, in case you suspect your iPhone having trust issues, try "idevicepair unpair" and then "idevicepair pair" again. Gruß Jan -- Rust Never Sleeps. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, January 18, 2017 11:01:06 PM EST Jan Ritzerfeld wrote:
Thanks Jan for the pointer to ifuse. I found that too, and it does work. Fwiw, I also got the camera:/ kio slave to work in dolphin by using this kluge: Plug in phone, "Trust" if necessary, open dolphin and enter the kio slave but when the phone folder is displayed do not open it. Open a second dolphin instance and again enter the kio, when the folder is displayed this time it can be opened and instead of the "storefeed" folder you should see a numbered folder inside of which is the DCIM folder. I found this to work most of the time, but not always.
That said, I tested all photo apps that use libgphoto2 to access the photo files. With all, the phone is recognized but the files cannot be seen. libgphoto2 uses different code than the camera:/ kio, so there appears to be an issue with libgphoto2 as well. Thanks again, --dg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Donnerstag, 19. Januar 2017, 11:20:49 CET schrieb Dennis Gallien:
[...] Thanks Jan for the pointer to ifuse. I found that too, and it does work.
Ah, okay.
Very cool workaround! I will try that next time I need access to my photos
Using a Windows VM, I accidentally clicked on my already trusted iPhone in the Explorer. Then, the iPhone asked me whether I trust this computer explicitly for photos and videos. I have never seen this before and I think that this new kind of trust in 10.2 is simply not supported by libimobiledevice, yet. https://github.com/libimobiledevice/libimobiledevice/issues/445 from https://lists.opensuse.org/opensuse-de/2017-01/msg00305.html Gruß Jan -- Every solution breeds new problems. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Donnerstag, 19. Januar 2017, 11:20:49 CET schrieb Dennis Gallien:
I tested it and it works sometimes. Regarding the different folder names, it looks like the storefeed folder is shown when the iPhone is locked and the other numbered store_... folder when it is unlocked. IIRC I have never been able to access all photos without unlocking the iPhone. Gruß Jan -- Sometimes the fool who rushes in gets the job done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday, January 22, 2017 4:56:56 PM EST Jan Ritzerfeld wrote:
Yes, it must be unlocked. Apparently a problem some have experienced is that the "trust" handshake dialog phone <=> computer doesn't happen. The intended behavior seems to be that once a computer is trusted, it isn't necessary to trust it again. I had to reset my network settings to get this working again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Donnerstag, 19. Januar 2017, 11:20:49 CET schrieb Dennis Gallien:
Are you sure? /usr/share/doc/packages/kio_kamera/README | You need libgphoto 2.4, 2.5 (or later). Maybe it is a problem in libgphoto2? But you said darktable upload and delete the iPhone files... Gruß Jan -- Nobody really knows what is going on anywhere in your organization. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
David C. Rankin -
Dennis Gallien -
Jan Ritzerfeld