Re: Cannot unlock the UI on Canon EOS M50

Hi,

On Tue, May 26, 2020 at 10:53:39AM +0200, Antonio Cuni wrote:
> An update on this issue:
> 
> 1. I did git bisect and it seems that the culprit commit is this
> one: 50880658e. I tried to revert it on top of the current master and I
> confirm that it works again as before.

I think this is caused by this part of the commit:

-       if (is_canon_eos_m (params)) {
+       if (is_canon_eos_m (params) && 0) {

This is weird, on master the && 0 is not there? 

This should be fixed in 2.5.25 release from the weekend, so current git master?

Or are these by the added set_uilock / reset_uilock calls in the commit?

> 2. Regarding the "BUSY" problem on the Raspberry Pi: it does NOT seem to be
> related to UI lock/unlock: it seems it is enough to connect gphoto2 to the
> camera in order to "unlock" the commands and no longer shows the "BUSY"
> message. It is enough to run "gphoto2 --config" (and exit immediately) or
> even "gphoto2 --summary" to "unbusy" the camera.


> I still don't understand why it happens on the raspberry but not on my PC,
> and whether it is related to gphoto2 at all. I suppose I can write a udev
> hook which unlocks is as soon as the camera is connected, but it would be
> nice to understand what's happening.

One of them probably uses gvfs automounting and the other not. gvfs opens the
camera in the background already.

Ciao, Marcus