Closed Isharfoxat closed 3 weeks ago
Solved!
What happened: for some reason, after a power failure, gvfs went back up. Disabling it through kill and chmod was a good thing but not enough!
The camera stays locked in some weird gvfs mode that a gphoto2 --reset
will NOT disable.
You must turn the camera off then on again, physically! Yes, even if your camera is located in a rather inaccessible place.
May my misadventure help anybody ...
Describe the bug As soon I try a command meant to actually drive the DSLR, it takes a few seconds then gphoto2 throws an error (hereafter retranslated from french). I don't get what is happening, as everything was fine and today, with absolutely no change made, everything goes bad! The closest solved issue I have seen here suggested it was the gvfs library messing with the communication. I already had deactivated gvfs for gphoto2 (through
chmod -x
, works like a charm), so theps auxw|grep gphoto
gives nothing, as expected. DSLR is a Canon EOS 1000D plugged in a Raspberry Pi 4 running an up-to-date Debian 11 with kernel 6.1.21-v8+Commands that don't seem affected:
(see below)
Name the camera
libgphoto2 and gphoto2 version
To Reproduce I would LOVE to be able to determine what caused this. Right now, anything from
gphoto2 --summary
togphoto2 --capture-image-and-download
triggers the error.Attached is the debug file gphoto-logfile.txt
Any help would be great!