Add ModemManager warning/support

[jhansonxi]

I just spent a ridiculous number of hours troubleshooting a Motorola V195 connection problem. I had a separate issue with a camera that was also failing to connect over USB which misled me into thinking they were related.

The phone problem was a conflict over ttyACM0 access. I've never used tethering so I didn't know ModemManager existed and had taken control of the port.

There either needs to be a warning when ModemManager is active and in control of the port or its API needs to be supported for access, if possible. A log-only message of "Error opening device. Unknown, busy or no permissions." is vague and process killing is not user-friendly.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[nijel]

Can you please provide debug log from that?

[nijel]

Also we've documentation for this: https://wammu.eu/docs/manual/faq/general.html#mutliple-programs-using-same-device-cause-various-errors-how-to-fix-that

[jhansonxi]

The wizard dialog says:

Wammu is now searching for phone:
Checking /dev/ttyACM0 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
Finished /dev/ttyACM0 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']
All finished, found 0 phones
No phone has been found!

Which isn't informative since it doesn't indicate a conflict exists. The documentation isn't useful if the user doesn't know what to look for. Most users will assume that their phone is not supported. Log attached.
wammuHmBheu.log.txt