is there any hope for a solution to my problem?

[Gilles Caulier]

The problem is not gogo to as well but the process turning in background
and locking the access to the device. I suspect that Shotwell is
responsible of that on your Gnome desktop. It monopolize the access to the
device and deny all 3rd party application…

Gilles

Le mer. 26 juil. 2023 à 17:00, gene heskett <gheskett at shentel.net> a écrit :

> On 7/26/23 09:26, Gilles Caulier wrote:
> > Hi,
> >
> > The warnings printed by the AppImage at startup are nothing to do with
> > your problem. It's just Qt warnings for other stuff.
> >
> > I suspect that your desktop runs in the background a program to handle
> > the camera connection and lock the access to digiKam. As I know Canon
> > cameras are managed with a Gphoto2 driver.
> >
> > Use a memory card reader instead of your camera, and use digiKam to
> > open the memory using the USB Mass Storage device.
>
> This may be a red herring. Shotwell has no such problem w/o gphoto2, but
> it buries the import in a Pictures/year/month/date/subdir. And I do mean
> buried. At my age, I often forget what if anything I had for breakfast
> and the current crop of clocks does NOT report the date, kde thinks the
> tz city is far more important than todays date. What were they thinking?
> gphoto2 has been removed since the first time it was mentioned. But
> removing libgphoto-2.6 will tear down the system with its dependencies.
> And I suspect lots of gfx stuff will die if I remove the exec bits from it.
>
> Looking at the lsof output, there is no diff in the count when turning
> the camera on and off. if libgphoto is grabbing it, shouldn't the count
> go up?
> gene at coyote:~$ lsof |wc -l (camera off for several minutes)
> 186898
> gene at coyote:~$ lsof |wc -l (5 secs after camera on)
> 186898
> it does not, inferring that gphoto2 is not the cause.
>
> I'm open to suggestions that work. But I'm not willing to teardown the
> system to prove they didn't cause the problem.  I'd blame it on the
> AppImage format, but debians 7.8 version also fails. I have the feeling
> its something about my raid10 /home directory, or possibly a new ACL
> problem, they claim the security has been tightened but that doesn't
> explain the 1 minute plus that an AppImage takes to open a file
> requestor, digiKam won't wait, openscad and cura will so I sit and OD on
> coffee while I wait after clicking the mouse to just do it.  Damned
> frustrating.
>
> Thank you Gilles
> > Best
> >
> > Gilles Caulier
> >
> > Le mer. 26 juil. 2023 à 15:19, gene heskett <gheskett at shentel.net> a
> écrit :
> >>
> >> Greetings all;
> >> digiKam is july 24th edition of 8,2.0
> >> I can run it, and see any pix on my drive.
> >> I can turn on my usb plugged in camera, a Canon SX420 IS, open the
> >> import window, select the camera, an see every pix I've ever taken that
> >> on the sd card in it. I can select by hand, a pix to import, click on
> >> download, select the folder I want to put the pix in, click on do it,
> >> get the attached advisory popup.
> >>
> >> There are NO errors output to the screen diiKam was launched from that
> >> you haven't seen before and all that is reported, is shown before the
> >> import attempt, at launch time IOW.
> >> copy/paste:
> >> gene at coyote:~$ digiKam
> >> -- digiKam Linux AppImage Bundle
> >> -- Use 'help' as CLI argument to know all available options for digiKam
> >> application.
> >> -- Notes: to integrate this bundle to your desktop, use
> AppImageLauncher.
> >> --        to enable all debug messages on the console, use 'export
> >> QT_LOGGING_RULES="digikam*=true"'.
> >> --        to extract the bundle contents locally, use option
> >> '--appimage-extract' on the command line.
> >> -- Detected host Linux -64-
> >> -- AppImage mounted directory: /tmp/.mount_digiKa0aUKbQ
> >> Check library libudev.so.0
> >> Check library libxcb-dri3.so.0
> >> Check library libcrypto.so.1.1
> >> Check library libssl.so.1.1
> >> Check library libnss3.so
> >> Check library libnssutil3.so
> >> Check library libsmime3.so
> >> Check library libgmodule-2.0.so.0
> >> -- Preloading shared libs:
> >>
> :/tmp/.mount_digiKa0aUKbQ/usr/lib/libavif.so.13:/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
> >> [0726/090254.088534:WARNING:resource_bundle_qt.cpp(119)]
> >> locale_file_path.empty() for locale
> >> [0726/090254.205907:WARNING:resource_bundle_qt.cpp(119)]
> >> locale_file_path.empty() for locale
> >> [0726/090254.205953:WARNING:resource_bundle_qt.cpp(119)]
> >> locale_file_path.empty() for locale
> >> [0726/090256.567552:WARNING:resource_bundle_qt.cpp(119)]
> >> locale_file_path.empty() for locale
> >> unknown: Unhandled container to remove :  Digikam::DigikamApp
> >>
> >> What more can I get you?
> >>
> >> Thanks.
> >>
> >> Cheers, Gene Heskett.
> >> --
> >> "There are four boxes to be used in defense of liberty:
> >>    soap, ballot, jury, and ammo. Please use in that order."
> >> -Ed Howdershelt (Author, 1940)
> >> If we desire respect for the law, we must first make the law
> respectable.
> >>    - Louis D. Brandeis
> >> Genes Web page <http://geneslinuxbox.net:6309/>
> > .
>
> Cheers, Gene Heskett.
> --
> "There are four boxes to be used in defense of liberty:
>   soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author, 1940)
> If we desire respect for the law, we must first make the law respectable.
>   - Louis D. Brandeis
> Genes Web page <http://geneslinuxbox.net:6309/>
>
> --
Send with Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20230726/d9e3542d/attachment.htm>