Device mount point is disabled (and fixed to wrong device)

[Jef Driesen]

On 03-02-18 18:05, Berthold Stoeger wrote:
> On Samstag, 3. Februar 2018 17:46:10 CET Rob Mason wrote:
>> Hi Berthold - the subgear is irda, not bluetooth. It has worked previously
>> on older versions, but unable to connect on 4.7.6-1 on Mint Linux 18.3. --
> 
> Yes I know. Nevertheless, the "interface consistency fix" in commit  d23bd46
> enables the device field only for serial transport.
> 
> To my defense - I just copied old buggy code, but made it more noticeable. I
> pushed a fix to github. If you can compile from source, you can use this. If
> not, there is a workaround: Select a dive computer with serial transport (I
> think the XP-Air is), change the device and then go back to the XP-10. This
> should be saved to the preferences, so you only have to do it once (until you
> change dive computer).

The reason why the dropdown is disabled is because IrDA communication doesn't 
use a device node at all. Libdivecomputer will automatically discover the IrDA 
device address. So it doesn't matter what is shown in the dropdown box, because 
it's not used for anything.

If the download fails because no dive computer is found, that means the 
discovery did not found any IrDA device (or at least not one that matches a 
known dive computer). Enable the libdivecomputer logfile checkbox and send us 
the log. That should tell us what is going on.

Jef