#990501 connman: Connman disrupted network during upgrade on system where it does not manage network

Package:
connman
Source:
connman
Description:
Intel Connection Manager daemon
Submitter:
Jesse Rhodes
Date:
2021-09-25 12:15:02 UTC
Severity:
normal
#990501#5
Date:
2021-06-30 21:04:11 UTC
From:
To:
Dear Maintainer,

This system has two desktop environments installed: KDE Plasma, which is used primarily; and LXQT, for backup. Network connections are managed by NetworkManager whenever I am using Plasma, which I was when I discovered this bug.

On upgrade to 1.36-2.2, connman triggered something to restart the network, the wifi connection dropped, and apt appeared to hang at:

I noticed after a few minutes, used my acpi hotkey to re-enable wifi, and the upgrade proceeded, with:

The associated systemctl status output was:

It appears that connman was waiting for some kind of network-up condition, which would never arrive because connman was not managing the network. It should be able to detect a system where something else (n-m, ifupdown, etc) is being used, and proceed with the upgrade without trying to mess with it.

Please let me know if you need any more information.

Jesse (sney)
#990501#10
Date:
2021-09-25 12:12:37 UTC
From:
To:
Hi,

in case you have plasma-nm installed, cmst (connman) shouldn't have been installed at all.

Lxqt metapackage recommends cmst (connman) or nm-tray (network-manager) or network-manager-gnome (network-manager) or plasma-nm (network-manager) or wicd (wicd-daemon).

In case you have network-manager without plasma-nm installed, avoid the lxqt metapackage, or add network-manager to its recommends.

Cheers,
Amy