Networkmanager does not connect to my WIFI after reboot

[linuxero]

Hi;

I know this must have been discussed somewhere before and it might have to do with policykit..but here is the problem.

I am trying to use Networkmanager instead of net_applet. I can connect to my WIFI, but after each reboot I have to click on connect and reenter the password!!

I tried to add the connection in nm-applet allowing all users to start the connection and making it a system one. Still after reboot, I have to click connect next to my netrwork and reenter the password.

Anybody knows about a solution?

Thanks

[doktor5000]

What desktop environment do you use? If it's gnome, might be a problem with the keyring as it does not load automatically in some cases: viewtopic.php?f=8&t=10074
Can you run seahorse and verfy whether your wireless password is listed there or not? If it's not, or if the keyring doesn't load and unlock automatically, that is why you need
to enter the password and then start the connection after every login.

And please post the output as root of

Code: Select all

journalctl -ab -u NetworkManager --no-pager
systemctl is-enabled NetworkManager.service
systemctl is-enabled NetworkManager-wait-online.service
ps -ef |grep -v grep|grep -i keyring
journalctl -ab | grep -i gnome-keyring-daemon

[linuxero]

Sorry forgot to mention that I am using KDE. I am out now. Later I'll post the commands' output

[linuxero]

Hi again;

Here's the output of the commands..

Code: Select all

# journalctl -ab -u NetworkManager --no-pager
-- Logs begin at Fri 2015-10-02 18:32:03 CEST, end at Wed 2015-10-07 13:20:36 CEST. --
Oct 07 13:19:13 localhost NetworkManager[1970]: <info>  NetworkManager (version 1.0.2) is starting...
Oct 07 13:19:13 localhost NetworkManager[1970]: <info>  Read config: /etc/NetworkManager/NetworkManager.conf
Oct 07 13:19:13 localhost NetworkManager[1970]: <info>  WEXT support is enabled
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  VPN: loaded org.freedesktop.NetworkManager.l2tp
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  VPN: loaded org.freedesktop.NetworkManager.pptp
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  VPN: loaded org.freedesktop.NetworkManager.openconnect
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  VPN: loaded org.freedesktop.NetworkManager.openvpn
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  VPN: loaded org.freedesktop.NetworkManager.vpnc
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  VPN: loaded org.freedesktop.NetworkManager.openswan
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  Loaded plugin ifcfg-rh: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  Loaded plugin keyfile: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Oct 07 13:19:14 localhost NetworkManager[1970]: (NetworkManager:1970): NetworkManager-ifcfg-rh-CRITICAL **: discover_mac_address: assertion 'device != NULL' failed
Oct 07 13:19:14 localhost NetworkManager[1970]: (NetworkManager:1970): NetworkManager-ifcfg-rh-CRITICAL **: discover_mac_address: assertion 'device != NULL' failed
Oct 07 13:19:14 localhost NetworkManager[1970]: (NetworkManager:1970): NetworkManager-ifcfg-rh-CRITICAL **: discover_mac_address: assertion 'error != NULL' failed
Oct 07 13:19:14 localhost NetworkManager[1970]: (NetworkManager:1970): NetworkManager-ifcfg-rh-CRITICAL **: discover_mac_address: assertion 'error != NULL' failed
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  monitoring kernel firmware directory '/lib/firmware'.
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  rfkill0: found WiFi radio killswitch (at /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/SNY5001:00/rfkill/rfkill0) (platform driver Sony Notebook Control Driver)
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  rfkill2: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill2) (driver iwlwifi)
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  WiFi hardware radio set enabled
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  WWAN hardware radio set enabled
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-adsl.so
Oct 07 13:19:14 localhost NetworkManager[1970]: <info>  Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-team.so
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wwan.so
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wifi.so
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  WiFi enabled by radio killswitch; enabled by state file
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  WWAN enabled by radio killswitch; enabled by state file
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  WiMAX enabled by radio killswitch; enabled by state file
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  Networking is enabled by state file
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (lo): link connected
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (lo): carrier is ON
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (lo): new Generic device (driver: 'unknown' ifindex: 1)
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (lo): exported as /org/freedesktop/NetworkManager/Devices/0
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (wlp3s0): using nl80211 for WiFi device control
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (wlp3s0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 2)
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (wlp3s0): exported as /org/freedesktop/NetworkManager/Devices/1
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (wlp3s0): preparing device
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (enp2s0): carrier is OFF
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (enp2s0): new Ethernet device (driver: 'sky2' ifindex: 3)
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (enp2s0): exported as /org/freedesktop/NetworkManager/Devices/2
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (enp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (enp2s0): preparing device
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  ifcfg-rh: add connection in-memory (2294f077-7e8e-4e79-87a4-0e6dd386980b,"Wired connection 1")
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  (enp2s0): created default wired connection 'Wired connection 1'
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  use BlueZ version 5
Oct 07 13:19:15 localhost NetworkManager[1970]: <info>  ModemManager available in the bus
Oct 07 13:19:17 localhost NetworkManager[1970]: <info>  wpa_supplicant started
Oct 07 13:19:18 localhost NetworkManager[1970]: <info>  (wlp3s0) supports 5 scan SSIDs
Oct 07 13:19:18 localhost NetworkManager[1970]: <info>  (wlp3s0): supplicant interface state: starting -> ready
Oct 07 13:19:18 localhost NetworkManager[1970]: <info>  (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Oct 07 13:19:18 localhost NetworkManager[1970]: <info>  (wlp3s0): supplicant interface state: ready -> disconnected
Oct 07 13:19:18 localhost NetworkManager[1970]: <info>  (wlp3s0) supports 5 scan SSIDs
Oct 07 13:19:20 localhost NetworkManager[1970]: <info>  startup complete
Oct 07 13:19:21 localhost NetworkManager[1970]: <info>  (wlp3s0): supplicant interface state: disconnected -> inactive


Code: Select all

# systemctl is-enabled NetworkManager.service
enabled

# systemctl is-enabled NetworkManager-wait-online.service
disabled

# ps -ef |grep -v grep|grep -i keyring
[root@localhost ~]#

# journalctl -ab | grep -i gnome-keyring-daemon
[root@localhost ~]#


[doktor5000]

And what networkmanager applet do you use? The KDE plasmoid "plasma-applet-nm" or the generic GTK applet nm-applet ?
Under KDE plasma-applet-nm saves the passwords into kwallet. If you run kwalletmanager as normal user do you see your wireless passwords in the category "Network Management"?

And please show the output of

Code: Select all

ps -ef |grep -v grep|grep wallet

[linuxero]

Hi;
I am using plasma-applet-nm

Code: Select all

# ps -ef |grep -v grep|grep wallet
nesrin    3605  2371  0 17:15 ?        00:00:00 [kwalletd] <defunct>
nesrin    4282     1  0 17:15 ?        00:00:00 /usr/bin/kwalletd --pam-login 5 11


[doktor5000]

Did you start kwalletd manually? Additionally there's a zombie kwalletd process (the one with <defunct>) - you should kill both, and then review the configuration in
system settings > Account Details > KDE Wallet

This is what the kwalletd process looks like here, started by kdeinit on startup:

Code: Select all

[doktor5000@Mageia5]─[18:28:15]─[~] ps -ef |grep -v grep|grep wallet
doktor5+  1736     1  0 Okt09 ?        00:00:00 kdeinit4: kwalletd [kdeinit]

[linuxero]

No, I have not started it manually. Besides it is deactivated in Systemsettings.!

[doktor5000]

Well, then enable it and reboot. Then please check again and post the output of

Code: Select all

ps -ef |grep -v grep|grep wallet

and see whether

If you run kwalletmanager as normal user do you see your wireless passwords in the category "Network Management"?

[linuxero]

Still having the same problem and the same result.

BTW; on another computer and with kdewallet disabled, I have no such problem. Weird enough, though, the zombie is there on both computers. I cannot kill the process any way.! Not even as root..

[doktor5000]

Not sure what same problem and same result you're talking about, you have to be more verbose.

And I've asked you twice for some information you didn't provide. Sorry can't help you further that way, good luck figuring it out yourself.

FWIW, you cannot kill a zombie, either send SIGCHILD to the parent process so that it can reap it's child processes or kill the parent process.

[linuxero]

I meant the result of ps:

Code: Select all

# ps -ef |grep -v grep|grep wallet
nesrin    4947  3339  0 16:53 ?        00:00:00 [kwalletd] <defunct>


I have tried to kill the process with kill command but it is never killed!

Aah! Sorry for the other information you asked for. It slipped me..anyways, kwalletmanager has nothing saved.

[doktor5000]

FWIW, you cannot kill a zombie, either send SIGCHILD to the parent process so that it can reap it's child processes or kill the parent process.

[linuxero]

That is exactly what I did doktor5000, but on one try the user session closed as if I asked for log out. I had to log in again..!

[doktor5000]

If you kill kdeinit or similar, you will kill the KDE session or maybe only the plasma desktop.
You should at least check with ps what you are trying to kill instead of blindly running any commands.

pstree -pas <pid> will show you the process tree for any given PID, parent and child processes.

[linuxero]

Sorry I don't have access to the computer all the time.

Code: Select all

# ps -ef |grep -v grep|grep wallet
nesrin    5128  3465  0 15:46 ?        00:00:00 [kwalletd] <defunct>
nesrin    5991     1  0 15:46 ?        00:00:00 /usr/bin/kwalletd --pam-login 5 11
[root@localhost ~]# pstree -pas 5128
systemd,1
  └─kdm,2272 -nodaemon
      └─kdm,3465                   
          └─(kwalletd,5128)


[doktor5000]

Sorry but I can't really help that way. You still have that zombie kwalletd process. In the example you showed you would need to send SIGCHLD signal to the parent process (kdm,3465) as root:

Code: Select all

kill -s SIGCHLD 3465

If it keeps running then you are out of luck and need to find out why it gets a zombie process.
Disable the autostart of kwalletd via system settings > Account Details > KDE Wallet and close kwallet if it is running, then reboot.

Then check that no kwallet or kwalletd process is running, and in a terminal as your normal user simply run

Code: Select all

kwalletd

and check the output and in another terminal if it has become a zombie process, and in case not check if kwalletmanager works.

FWIW, this bugreport sounds similar to your issue: https://bugs.launchpad.net/ubuntu/+sour ... ug/1309955
or maybe also https://bugs.launchpad.net/ubuntu/+sour ... ug/1335135

[linuxero]

Thank you doktor5000,

I've tried to kill the process, but it just won't die..!

I'll check it out and update when something possibly comes out..

Thanks for the reference

[doktor5000]

I've tried to kill the process, but it just won't die..!

I repeat a third time: you cannot kill a zombie. Either the parent process has a handler for SIGCHLD signal and is able to reap its children, or otherwise you need to kill the parent process or reboot.
In your case the parent is kdm, and KDE will probably restart if you kill it, and it will probably produce the same problem again.

[doktor5000]

If you didn't report this on bugzilla, you may want to have a look at https://bugs.mageia.org/show_bug.cgi?id=17513#c6
and https://bugs.mageia.org/show_bug.cgi?id=16143 for the actual issue.
Uninstall pam_kwallet should be sufficient to workaround the issue for you.