I'm a bit new to digikam, and having trouble with import
procedures. Trying to
import using the generic USB PTP Class camera or the digikam
suggested option "Huawei P9 Plus" both yield the same error:
I'm using
digikam-5.8.0-01-x86-64 under Ubuntu 16.04.3 LTS Would very
much appreciate any thoughts on how to proceed.
TIA Tony
|
Well, the PTP protocol is implement through Gphoto2 driver. If this kind of error appear, this can be a dysfunction located in Gphoto2 driver. To have more details about, run the appimage from a console and look debug trace printed while you try to read the phone contents. Gilles Caulier 2018-02-11 4:30 GMT+01:00 Tony Bazeley <[hidden email]>:
|
There's always "Plan B":d/l the images to the machine directly and then let digiKam handle them from there. Sure, it's an extra step or two. Given the current problem, though, it may be the easiest way to fix the problem. :) On Sun, Feb 11, 2018 at 5:49 AM, Gilles Caulier <[hidden email]> wrote:
|
In reply to this post by Gilles Caulier-4
I had a similar problem with an iPhone. I got it to work by
fiddling around some. See
http://digikam.1695700.n4.nabble.com/Import-from-iPhone-5-behaves-strangely-td4704878.html
Ralph On 02/11/2018 07:14 AM, Richard B.
Emerson wrote:
|
I use an iphone 7 here. I need to grant computer on phone to be able to see items in import tool, else nothing appear. That all. After all, it's Apple security stage, as usual... Gilles Caulier 2018-02-11 17:19 GMT+01:00 lachenmaier <[hidden email]>:
|
In reply to this post by Gilles Caulier-4
Output on attempting to import is
below - I'm assuming the ALSA errors are not related
digikam.geoiface: "setting backend marble" But outside the appimage I can access the Huawei device tonbaz@muscat:~$ gphoto2 --auto-detectI'm not that familiar with appimage, but understand it to contain all the libraries required. If that's the case it appears that the problem lies in the digikam appimage or it's interface with Ubuntu. As Richard suggests I can transfer files to a Ubuntu directory and import from that directory as a work around. Should I report this as a digikam bug, or is Is there something else I can do? Tony On 11/02/18 21:19, Gilles Caulier wrote:
|
Free forum by Nabble | Edit this page |