Re: nm-applet: "NetworkManager is not running..."

[poma <pomidorabelisima gmail com>]

On 17.11.2016 12:40, poma wrote:
> On 16.11.2016 09:51, poma wrote:
> > On 15.11.2016 08:59, poma wrote:
> > > Cold Boot from Soft Off aka S5, promptly Logged In to X session
> > > nm-applet: "NetworkManager is not running..."
> > >
> > > $ nmcli general status 
> > > STATE      CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN    
> > > connected  full          enabled  enabled  enabled  enabled 
> > > $ systemctl is-active NetworkManager
> > > active
> > > $ systemd-analyze blame | grep Net
> > >            427ms NetworkManager.service
> > >
> > >
> > > Subsequently after Reboot aka Warm Boot, likewise
> > > nm-applet: "NetworkManager is not running..."
> > >
> > >
> > > To fix this, Re-Log In is required,
> > > or wait for a minute before Log In.
> > [...]
> >
> > If firewalld isn't involved:
> >
> > $ systemctl is-enabled firewalld.service 
> > disabled
> > $ systemctl is-active firewalld.service 
> > inactive
> >
> > the problem disappears,
> > however,
> > if firewalld -is- involved
> >
> > $ systemd-analyze blame | egrep Net\|firewall
> >          33.083s firewalld.service
> >            340ms NetworkManager.service
> >
> > the problem appears.
> [...]
>
> NetworkManager-1.5.2-0.5.20161116gitcb61dd1.fc24.x86_64
> network-manager-applet-1.4.3-0.12.20161115git137ec04.fc24.x86_64
> &
> firewalld-0.4.4.1-3.fc24.noarch
> - incl. firewall.core.fw_nm: create NMClient lazily
>   https://github.com/t-woerner/firewalld/commit/52620dd.patch
>
> $ systemd-analyze blame | egrep two\|ewa
>           9.313s firewalld.service
>            745ms NetworkManager.service
>
>
> Resolved thanks to Lubo.

Although, there is one side effect;

firewall-config Warning:
"Failed to get connections from NetworkManager"

Attachment: firewall-config-Warning.png
Description: PNG image