Bug 340568

Do you use KWallet? There is a problem when you had previously secrets stored in plain text files instead of in KWallet. Solution for this is to re-save your connection or check "All users ... " checkbox.

I do use KWallet, and it shows my wallet as currently open with both 'KNetworkManager' and 'Network Management' granted access.

Can you show me your NetworkManager log? The log file should be in /var/log/syslog.

Yes, here's what happened as the laptop woke:

Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> wake requested (sleeping: yes  enabled: yes)
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> waking up and re-enabling...
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (wlan0): bringing up device.
Nov  4 15:06:30 soyuz kernel: [96887.162804] iwlwifi 0000:05:00.0: L1 Enabled; Disabling L0S
Nov  4 15:06:30 soyuz kernel: [96887.165843] iwlwifi 0000:05:00.0: Radio type=0x0-0x2-0x0
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (wlan0): preparing device.
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (wlan0): deactivating device (reason 'managed') [2]
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> NetworkManager state is now CONNECTED_GLOBAL
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (eth0): bringing up device.
Nov  4 15:06:30 soyuz kernel: [96887.196678] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (eth0): preparing device.
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (eth0): deactivating device (reason 'managed') [2]
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> NetworkManager state is now DISCONNECTED
Nov  4 15:06:30 soyuz kernel: [96887.258067] r8169 0000:0b:00.0 eth0: link down
Nov  4 15:06:30 soyuz kernel: [96887.258136] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (wlan0) supports 5 scan SSIDs
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (wlan0): supplicant interface state: starting -> ready
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Nov  4 15:06:30 soyuz NetworkManager[1262]: <warn> Trying to remove a non-existant call id.
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (wlan0): supplicant interface state: ready -> disconnected
Nov  4 15:06:30 soyuz NetworkManager[1262]: <info> (wlan0) supports 5 scan SSIDs
Nov  4 15:06:30 soyuz wpa_supplicant[1419]: wlan0: Reject scan trigger since one is already pending
Nov  4 15:06:30 soyuz wpa_supplicant[1419]: wlan0: CTRL-EVENT-SCAN-STARTED 
Nov  4 15:06:33 soyuz NetworkManager[1262]: <info> (wlan0): supplicant interface state: disconnected -> inactive

Hmm, it looks that your wireless device is not managed by NetworkManager. Could you also post here output from "nmcli device show", but do not post it to a comment and attach it instead.

Created attachment 89464 [details]
output from `nmcli device list`

output from `nmcli device list`

Created attachment 89465 [details]
nmcli output after resume

Hmm, that looks correct. Could you try to check "All users ... " checkbox? But it's weird I don't see any attempt to activate your connection in NM log.

Yep, checking 'all users' fixes it!

It fixes it, but it's not a proper solution. Now your secrets are stored in NetworkManager instead of KWallet. There must be some problem with initialization of our kded module. Do you use regular Plasma desktop and not Plasma netbook for example? Are you sure you have KWallet enabled and that plasma-nm has access to it?

*** Bug 340747 has been marked as a duplicate of this bug. ***

Could someone of you try to update to 0.9.3.5 version and check whether this issue is solved here or not? 

Link for the new version is here http://download.kde.org/stable/plasma-nm/plasma-nm-0.9.3.5.tar.xz.mirrorlist

*** Bug 339674 has been marked as a duplicate of this bug. ***

*** Bug 340839 has been marked as a duplicate of this bug. ***

When you edit your wireless network in our editor, is your password filled here or is it missing?

I have tried to install Kubuntu 14.04 and upgrade it to 14.10 and I can confirm this problem, but it doesn't look like a problem in plasma-nm. I'm almost sure that this problem is in NetworkManager. I'll try to confirm it on another desktop.

Confirmed that it doesn't work even in Unity so the problem is not on our side. Please report a bug in Ubuntu bugzilla.

(In reply to Jan Grulich from comment #1)
> Do you use KWallet? There is a problem when you had previously secrets
> stored in plain text files instead of in KWallet. Solution for this is to
> re-save your connection or check "All users ... " checkbox.

Checking "All Users" fixed the problem for me.

It fixes it, but it's just a workaround. I just checked NM logs and there is no attempt to auto-activate any connection. When I mark this connection as available for all users then NM tries to auto-activate it, which means that there is something broken in NM internally.

*** Bug 340953 has been marked as a duplicate of this bug. ***

I came across a very similar issue when upgrading from Ubuntu 14.04 to 14.10.

I believe I tracked it down, there are 2 issues in ubuntu (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203 and https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1400205). If people care to test those patches, I'd love to confirm that that was the the root cause.

sounds like this bug
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924

which is apparently ubuntu-related, so not strictly KDE. Can anyone confirm this by running KDE on another distro?

Everything works on Debian Unstable