[Pkg-utopia-maintainers] Bug#970500: Bug#970500: network-manager does not start at boot
Ansgar
ansgar at debian.org
Fri Sep 18 11:14:22 BST 2020
On Thu, 2020-09-17 at 14:32 +0200, Hans wrote:
> OK, I have rechecked my configurations. It appears, that network-manager is
> started, when I do a "systemctl enable NetworkManager". However, still /etc/
> init.d/network-manager is missing. Dunno, if this is still needed.
systemd uses /lib/systemd/system/NetworkManager.service to start
NetworkManager; the init script isn't used by systemd.
> When I am running plasma, then nm-applet gets access to the network-manager
> service, but when I start LXDE, I get the message, that the network-manger-
> service is not running. So it looks for me, like a rights problem.
>
> When I do start nm-applet as root in LXDE, then I get access to the network-
> manager-service, but when I do the same as a normal user, access is forbidden
> (something dbus and so).
Hmm, I don't maintain network-manager and am not quite sure, but for
permission issues I would guess that PolicyKit is configured to allow
access only to logged in users, but the system thinks you are not
logged in. Maybe check with `loginctl` for an active session?
Do you use the same way to start Plasma and LXDE, i.e. the same display
manager (sddm, lightdm, gdm), or is there a difference?
> I would not have changed to nemtwork-manager, because I was happy with wicd,
> but as wicd was removed from the repo, I chose the alternative.
wicd was removed from testing/unstable as part of the Python2 removal,
but there is a version in experimental that uses Python 3. You could
try to install that or wait until it gets uploaded to unstable.
Ansgar
More information about the Pkg-utopia-maintainers
mailing list