[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: digiKam dead, cannot import from camera



On Tue, Jun 27, 2023 at 09:39:26AM -0400, gene heskett wrote:
> On 6/27/23 07:23, Greg Wooledge wrote:
> > How are you performing this download?
> > 
> With digiKam V8.0.0 AppImage's import function. I can see the images on the
> cameras card, but cannot download them the chosen subdir to put them in is a
> "" pathname ack one error message I seen.
> 
> The debian disto's version of digiKam has never worked and is about 3 years
> old at version 7.2 I think. Huum just checking, that was the bullseye
> version.
> 
> But I see the bookworm version is 7.9 so lets see if it works, no, and this
> is logged to the konsole:
> kf.xmlgui: Unhandled container to remove :  Digikam::DigikamApp
> qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3893,
> resource id: 153092204, major code: 18 (ChangeProperty), minor code: 0
> qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3894,
> resource id: 153092204, major code: 18 (ChangeProperty), minor code: 0
> QLayout: Attempting to add QLayout "" to Digikam::DNGConvertSettings "",
> which already has a layout
> digikam.import: Did not identify a valid mount point for ""
> digikam.import: Did not identify a valid mount point for ""
> digikam.import: Did not identify a valid mount point for ""
> digikam.general: Unable to find album for  QUrl("file:///Saw4Bruce/")
> 
> Same as the other 3 appimages.
> call me puzzled. On bullseye, this Just Worked.

I know absolutely nothing about this software, but look at that QUrl in
the last line of the log.  That looks entirely wrong to me.  You said in
another message that the full path of the directory was
/home/gene/Pictures/Saw4Bruce so shouldn't the URL be
file:///home/gene/Pictures/Saw4Bruce/ ?

Unless the application is running chrooted at /home/gene/Pictures/ (which
strikes me as exceedingly unlikely), I don't see how that URL would ever
work.

So, my initial question would be why that URL is wrong.  Is the application
being sent a relative directory path but interpreting it as an absolute
directory path?  Something along those lines.  You'll need to investigate
with people who actually know this software.  Those people may or may not
be on debian-user.


Reply to: