Re: Cannot unlock the UI on Canon EOS M50

On Tue, May 26, 2020 at 11:17 AM Marcus Meissner <[email protected]> wrote:

> > 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?
>

I don't think it's the "&& 0" part: as you say, it's already gone on master
but this does not solve the issue.
This is the diff which I have applied on top of acafc3324:
http://paste.openstack.org/show/793979/


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

I think so. Basically, the effect that I see is that on the current master,
whenever I exit gphoto my camera is in UI LOCK mode.
Moreover, tying to set uilock=0 always fails. So, I suspect that gphoto
successfully locks the UI in "ptp_canon_eos_setuilock()", but fails to
unlock in "ptp_canon_eos_resetuilock (params)".



> > 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.
>

Ok, this makes sense. So, you confirm that seeing "BUSY" it is the
correct/expected behavior by default?

Thanks!
Antonio

_______________________________________________
Gphoto-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gphoto-user