Package: modemmanager
Version: 1.10.0-1
Severity: serious
Justification: missing dependency
Hi,
A basic modemmanager installation doesn't result in a functional mmcli
command. The following might work (e.g. after a reboot, to make sure the
modem detection is fine):
# mmcli -L
/org/freedesktop/ModemManager1/Modem/0 [QUALCOMM INCORPORATED] QUECTEL
Mobile Broadband Module
But trying to force a scan (e.g. before or instead of rebooting)
doesn't:
# mmcli -S
error: couldn't request to scan devices:
'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Failed: PolicyKit
authorization failed: 'GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
The name org.freedesktop.PolicyKit1 was not provided by any .service files''
Trying to establish a connection doesn't work either:
# mmcli -m 0 --simple-connect apn=orange
error: couldn't connect the modem:
'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Failed: PolicyKit
authorization failed: 'GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
The name org.freedesktop.PolicyKit1 was not provided by any .service files''
Given the error message, it's pretty clear the problem is at the D-Bus
level, so isn't actually limited to mmcli: trying to toy with the modem
over D-Bus directly (e.g. using Python bindings) would result in the
same problems.
It looks to me policykit-1 should be at least in Recommends, possibly in
Depends. This might have been unreported until since end users are
likely using NetworkManager from a desktop environment, and
network-manager does list policykit-1 in Depends.
I've double checked those findings with buster myself, but I'm told the
same happens with bullseye as well, which would be consistent with the
facts Depends/Recommends didn't change between buster's version and
bullseye's.
This would seem worth fixing in both distributions.
Cheers,
--
Cyril Brulebois (k...@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
