Network Manager Applet Error after Suspend

Hi there. I cant find anyone else currently having this same issue so here goes..

After waking from suspend Network Manager seems to be blind to all networks and connections (empty wifi icon, nothing in lists...) but, lo and behold - I am still connected to my home network. If I were to take this machine to the cafe or something though, there would seem to be no way to connect to their network[easily] until I reboot.
I have found that using
systemctl restart NetworkManager.service
properly restarts network manager and normal behaviour returns. But, of course, I would like to find and fix the issue.

Below is some relevant information. What do y'all make of it ?

Kernel: 4.1.24-1-MANJARO x86_64 (64 bit gcc: 6.1.1)
           Desktop: Xfce 4.12.3 (Gtk 2.24.30) Distro: Manjaro Linux
Machine:   System: Dell (portable) product: Inspiron 3451 v: A04
           Mobo: Dell model: 0H4MK6 v: A00 Bios: Dell v: A04 date: 07/07/2015
Battery    BAT0: charge: 28.0 Wh 110.5% condition: 25.4/28.0 Wh (91%)
           model: LGC-LGC2.80 DELL 991XP57 status: Full
CPU:       Quad core Intel Pentium N3540 (-MCP-) cache: 1024 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 17314
           clock speeds: max: 2665 MHz 1: 1875 MHz 2: 692 MHz 3: 1762 MHz
           4: 660 MHz
Graphics:  Card: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display
           bus-ID: 00:02.0
           Display Server: X.Org 1.17.4 driver: intel
           Resolution: 1366x768@60.00hz
           GLX Renderer: Mesa DRI Intel Bay Trail
           GLX Version: 3.0 Mesa 11.2.2 Direct Rendering: Yes
Audio:     Card Intel Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k4.1.24-1-MANJARO
Network:   Card-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
           driver: ath9k bus-ID: 03:00.0
           IF: wlp3s0 state: up 
           Card-2: Atheros usb-ID: 001-004
           IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Info:
           Init: systemd Gcc sys: 6.1.1
           Client: Shell (bash 4.3.421) inxi: 2.3.0 
journalctl -b -u NetworkManager

May 16 15:09:45 Majix NetworkManager[477]: <info>  [1463436585.3538] dns-mgr: Writing DNS information to /usr/bin/resolvconf
May 16 15:09:45 Majix NetworkManager[477]: <info>  [1463436585.4857] device (wlp3s0): Activation: successful, device activated.
May 16 16:36:38 Majix NetworkManager[477]: <info>  [1463441798.6837] manager: sleep requested (sleeping: no  enabled: yes)
May 16 16:36:38 Majix NetworkManager[477]: <info>  [1463441798.6837] manager: sleeping...
May 16 16:36:38 Majix NetworkManager[477]: <info>  [1463441798.6837] device (wlp3s0): state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
May 16 16:36:38 Majix NetworkManager[477]: <info>  [1463441798.6839] dhcp4 (wlp3s0): canceled DHCP transaction
May 16 16:36:38 Majix NetworkManager[477]: <info>  [1463441798.6839] dhcp4 (wlp3s0): state changed bound -> done
May 16 16:36:38 Majix NetworkManager[477]: <info>  [1463441798.6972] dns-mgr: Removing DNS information from /usr/bin/resolvconf
May 16 16:36:38 Majix NetworkManager[477]: <info>  [1463441798.7708] manager: NetworkManager state is now ASLEEP
May 16 16:45:54 Majix NetworkManager[477]: <info>  [1463442354.3404] manager: wake requested (sleeping: yes  enabled: yes)
May 16 16:45:54 Majix NetworkManager[477]: <info>  [1463442354.3404] manager: waking up...
May 16 16:45:54 Majix NetworkManager[477]: <info>  [1463442354.3404] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 16 16:45:54 Majix NetworkManager[477]: <info>  [1463442354.3586] manager: NetworkManager state is now DISCONNECTED
May 16 16:45:54 Majix NetworkManager[477]: <info>  [1463442354.4033] sup-iface[0x1d70d90,wlp3s0]: supports 4 scan SSIDs
May 16 16:45:54 Majix NetworkManager[477]: <info>  [1463442354.4052] device (wlp3s0): supplicant interface state: starting -> ready
May 16 16:45:54 Majix NetworkManager[477]: <info>  [1463442354.4054] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3147] device (wlp3s0): supplicant interface state: ready -> inactive
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3467] policy: auto-activating connection 
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3484] device (wlp3s0): Activation: starting connection 
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3487] device (wlp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3489] manager: NetworkManager state is now CONNECTING
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3499] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3503] device (wlp3s0): Activation: (wifi) access point has security, but secrets are required.
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3503] device (wlp3s0): state change: config -> need-auth (reason 'none') [50 60 0]
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3565] device (wlp3s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3572] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3575] device (wlp3s0): Activation: (wifi) connection has security, and secrets exist.  No new secr
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3576] Config: added 'ssid' value 
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3576] Config: added 'scan_ssid' value '1'
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3576] Config: added 'key_mgmt' value 'WPA-PSK'
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3576] Config: added 'auth_alg' value 'OPEN'
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3577] Config: added 'psk' value '<omitted>'
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.3758] sup-iface[0x1d70d90,wlp3s0]: config: set interface ap_scan to 1
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.4019] device (wlp3s0): supplicant interface state: inactive -> authenticating
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.4091] device (wlp3s0): supplicant interface state: authenticating -> associating
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.4159] device (wlp3s0): supplicant interface state: associating -> associated
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.4295] device (wlp3s0): supplicant interface state: associated -> 4-way handshake
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.4505] device (wlp3s0): supplicant interface state: 4-way handshake -> completed
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.4506] device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wirele
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.4507] device (wlp3s0): state change: config -> ip-config (reason 'none') [50 70 0]
May 16 16:45:55 Majix NetworkManager[477]: <info>  [1463442355.4513] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
May 16 16:46:00 Majix NetworkManager[477]: <info>  [1463442360.9392]   expires in 86400 seconds
May 16 16:46:00 Majix NetworkManager[477]: <info>  [1463442360.9398] dhcp4 (wlp3s0): state changed unknown -> bound
May 16 16:46:00 Majix NetworkManager[477]: <info>  [1463442360.9428] device (wlp3s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
May 16 16:46:00 Majix NetworkManager[477]: <info>  [1463442360.9439] device (wlp3s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
May 16 16:46:00 Majix NetworkManager[477]: <info>  [1463442360.9445] device (wlp3s0): state change: secondaries -> activated (reason 'none') [90 100 0]
May 16 16:46:00 Majix NetworkManager[477]: <info>  [1463442360.9447] manager: NetworkManager state is now CONNECTED_LOCAL
May 16 16:46:01 Majix NetworkManager[477]: <info>  [1463442361.0116] manager: NetworkManager state is now CONNECTED_GLOBAL
May 16 16:46:01 Majix NetworkManager[477]: <info>  [1463442361.0118] policy: set (wlp3s0) as default for IPv4 routing and DNS
May 16 16:46:01 Majix NetworkManager[477]: <info>  [1463442361.0120] dns-mgr: Writing DNS information to /usr/bin/resolvconf
May 16 16:46:01 Majix NetworkManager[477]: <info>  [1463442361.1158] device (wlp3s0): Activation: successful, device activated.
May 16 16:48:17 Majix systemd[1]: Stopping Network Manager...
May 16 16:48:17 Majix NetworkManager[477]: <info>  [1463442497.1932] caught SIGTERM, shutting down normally.
May 16 16:48:17 Majix NetworkManager[477]: <info>  [1463442497.1933] device (wlp3s0): state change: activated -> deactivating (reason 'unmanaged') [100 110 3]
May 16 16:48:17 Majix NetworkManager[477]: <info>  [1463442497.1936] manager: NetworkManager state is now DISCONNECTING
May 16 16:48:17 Majix NetworkManager[477]: <info>  [1463442497.2390] device (wlp3s0): state change: deactivating -> unmanaged (reason 'removed') [110 10 36]
May 16 16:48:17 Majix NetworkManager[477]: <info>  [1463442497.2391] dhcp4 (wlp3s0): canceled DHCP transaction
May 16 16:48:17 Majix NetworkManager[477]: <info>  [1463442497.2391] dhcp4 (wlp3s0): state changed bound -> done
May 16 16:48:17 Majix NetworkManager[477]: <info>  [1463442497.2491] dns-mgr: Removing DNS information from /usr/bin/resolvconf
May 16 16:48:17 Majix NetworkManager[477]: <info>  [1463442497.3269] manager: NetworkManager state is now DISCONNECTED
May 16 16:48:17 Majix NetworkManager[477]: <info>  [1463442497.3390] exiting (success)
May 16 16:48:17 Majix systemd[1]: Stopped Network Manager.
May 16 16:48:17 Majix systemd[1]: Starting Network Manager...
May 16 16:48:17 Majix systemd[1]: Started Network Manager.
May 16 16:48:17 Majix NetworkManager[2325]: <info>  [1463442497.3769] NetworkManager (version 1.2.2) is starting...

Editted for temporary solution.

2 Likes

Screenshots:

1 Like

Hi,

I've finally created an account since i'm enjoying the distro very much and haven't got any major issues with xfce edition until THIS exact BUG.

Here are my observations - this is latest release /stable/ - tested this on many kernelss - no change, seems like a bug in nm 1.2.*.

To reproduce:

  • suspend laptop turn back on
  • turn of WIFI by hardware switch turn back on

Result

  • no networks visible in network manager, icon changes to one without wifi range
  • AP WIFI connection get re-established though and i'm able to use net without issues

Expected:

  • AP connection established after wake up from suspend, networks visible in nm

Workaround:

  • downgrading to nm 1.0.12-1 resolves the issue but .. you know :))
    Edit:
    Downgrading network-manager-applet resolves this issue
4 Likes

Hello, I had the same problem and fixed it. The problem was not in networkmanager, it was in network-manager-applet. I downgraded it to version: 1.0.10-1 and Wi-Fi status after suspend became normal state.
I wish it will usefull for you. With best regards.

3 Likes

Thanks for the tips :slight_smile: ... do you know what was up with network-manager-applet, @DmTi?

Sorry, I don't.

Sorry, for late reply, seems i haven't received any notifications after thread updates.

@DmTI yes i forgot to mention that i've also downgraded network-manager-applet together with networkmanager. Added correction to my original post.

Also noticed this in dmesg after suspend:

iwl4965 0000:02:00.0: RF_KILL bit toggled to enable radio.
iwl4965 0000:02:00.0: On demand firmware reload

Probably kernel module for wifi card is reloaded and the applet doesn't pick this up?
Just my guess.

Update since last stable release :

Issue still present with network-manager-applet-1.2.2-1 (Still using 1.0.10-1)

[Also, noticed using newer version on lower kernel [4.1] seem to break connections/stall, fixed with using 4.6 kernel .. but again suspend issue still]

1 Like

I have switched to Testing, but currently up to 1.2.4-1 still not working properly.

For those interested, here is the launchpad bug:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574347

*Edit - seems they have been merging and renaming different bugs and fixes ... so that was the original.

New bug here :

One post seems to have some useful information:

####Post 65
If I restart network-manager right after booting (before suspend) I can't reproduce.
So maybe make a script to delay network-mananger at boot with solve all problems?

I have this problem too. When I start my laptop after hibernation, NetworkManager applet is broken and I must restart it in terminal. Version 1.4.2-1.

I am fairly new to Linux. How is it possible for a bug like this to persist for such a long time. I would think that it would have been fixed by now.

This problem was fixed with an update, but has since regressed once more.
As for now you can use downgrade to find one that may work.
Version 1.4.0-1 is reported working.

downgrade network-manager-applet

EDIT - It did not work until I also downgraded networkmanager to 1.4.0-1 as well.

2 Likes

I can confirm that. Downgrading both network-manager-applet and networkmanager to 1.4.0-1 fixed it.

But I am having problems to connect after suspend if I choose to automatically connect to my VPN. Turned that off for now and connect manually to my VPN. Anyone else experiencing that issue as well?

I downgraded network-manager-applet to 1.4.0-1 and, as I'm running openrc, also networkmanager-consolekit to 1.4.0-1 but it didn't work out.

I also tried several version back, and also networkmanager-qt, several versions, without success.

It would be better to create a new post so you get Personalized Support. :innocent:
Not all issues are always same, even if they look alike.

Amazing, more than one month passed, and I still have the very same issue with my network-manager-applet in manjaro xfce. At least the workaround is functional.

I think it is related to manjaro kernel, I have manjaro and stock archlinux installed here, dual boot in the same box and this bug only happens in manjaro (both xfce)

I encountered this bug a few times, after the update, when I log out and in again.

I'm still encountering this bug from suspend and logout.

Version: 1.4.2-1

same here

Forum kindly sponsored by