NetworkManager requires me to "forget" a saved network to connect

chrisp1090 · 2013-10-01 23:38:16

I've been having issues connecting to my university's wifi, which uses WPA2 Enterprise with PEAP and MSCHAPv2. Every time I boot or wake up my computer, it won't even attempt to connect to the network. The only way I'm able to connect is if I have NetworkManager "forget" the network and then reenter the credentials entirely.

I only recently started having this issue. I have had this laptop for about a month and this has only been a problem in the past week or so. I don't have this problem at home, where I use WPA2 Personal security.

[144274.077453] pcieport 0000:00:1c.0: System wakeup enabled by ACPI
[144274.090812] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[144274.130666] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[144274.144024] PM: noirq suspend of devices complete after 79.551 msecs
[144274.144505] ACPI: Preparing to enter system sleep state S3
[144274.144951] PM: Saving platform NVS memory
[144274.146552] Disabling non-boot CPUs ...
[144274.148517] smpboot: CPU 1 is now offline
[144274.250528] smpboot: CPU 2 is now offline
[144274.353849] smpboot: CPU 3 is now offline
[144274.361127] ACPI: Low-level resume complete
[144274.361174] PM: Restoring platform NVS memory
[144274.361719] Enabling non-boot CPUs ...
[144274.361763] smpboot: Booting Node 0 Processor 1 APIC 0x1
[144274.376262] Intel pstate controlling: cpu 1
[144274.376358] CPU1 is up
[144274.376381] smpboot: Booting Node 0 Processor 2 APIC 0x2
[144274.390159] Intel pstate controlling: cpu 2
[144274.390226] CPU2 is up
[144274.390246] smpboot: Booting Node 0 Processor 3 APIC 0x3
[144274.404036] Intel pstate controlling: cpu 3
[144274.404102] CPU3 is up
[144274.408368] ACPI: Waking up from system sleep state S3
[144274.437832] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
[144274.491125] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
[144274.531377] PM: noirq resume of devices complete after 120.267 msecs
[144274.531691] PM: early resume of devices complete after 0.276 msecs
[144274.531749] i915 0000:00:02.0: setting latency timer to 64
[144274.531761] xhci_hcd 0000:00:14.0: setting latency timer to 64
[144274.531912] ehci-pci 0000:00:1a.0: setting latency timer to 64
[144274.531956] ahci 0000:00:1f.2: setting latency timer to 64
[144274.531993] ath: phy0: ASPM enabled: 0x43
[144274.532020] mei_me 0000:00:16.0: irq 44 for MSI/MSI-X
[144274.532033] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
[144274.532238] ehci-pci 0000:00:1d.0: setting latency timer to 64
[144274.532320] pcieport 0000:00:1c.0: System wakeup disabled by ACPI
[144274.731275] dpm_run_callback(): pnp_bus_resume+0x0/0x80 returns -19
[144274.731277] PM: Device 00:07 failed to resume: error -19
[144274.871002] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[144274.873181] ata3.00: configured for UDMA/100
[144275.897663] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[144276.157329] usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
[144276.683754] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[144276.916967] ata1.00: configured for UDMA/133
[144276.930487] sd 0:0:0:0: [sda] Starting disk
[144277.057004] usb 1-1.4: reset high-speed USB device number 5 using ehci-pci
[144277.956750] usb 1-1.1: reset full-speed USB device number 66 using ehci-pci
[144278.556538] usb 1-1.1: device firmware changed
[144279.556472] PM: resume of devices complete after 5026.352 msecs
[144279.557121] PM: Finishing wakeup.
[144279.557124] Restarting tasks ... done.
[144279.639582] video LNXVIDEO:00: Restoring backlight state
[144279.656089] usb 1-1.1: USB disconnect, device number 66
[144279.838984] r8169 0000:01:00.0 enp1s0: link down
[144279.839024] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[144279.877166] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[144279.955980] usb 1-1.1: new full-speed USB device number 67 using ehci-pci
[144283.155064] usb 1-1.1: USB disconnect, device number 67
[144283.954840] usb 1-1.1: new full-speed USB device number 68 using ehci-pci
[144348.878425] wlp2s0: authenticate with MAC
[144348.890140] wlp2s0: send auth to MAC (try 1/3)
[144348.891947] wlp2s0: authenticated
[144348.892069] ath9k 0000:02:00.0 wlp2s0: disabling HT as WMM/QoS is not supported by the AP
[144348.892074] ath9k 0000:02:00.0 wlp2s0: disabling VHT as WMM/QoS is not supported by the AP
[144348.894137] wlp2s0: associate with MAC (try 1/3)
[144348.897781] wlp2s0: RX AssocResp from MAC (capab=0x431 status=0 aid=8)
[144348.897945] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[144348.898057] wlp2s0: associated

Strike0 · 2013-10-04 01:32:40

This reads related: https://bugs.archlinux.org/task/34396
There is a work around mentioned in comment 2.

chrisp1090 · 2013-10-04 01:34:11

I don't think this solution would help me because the network requires a CA certificate.

Strike0 · 2013-10-04 01:48:29

True. It's odd though no cert appears in the log you provide.
Maybe you want to add a log of a failed connect anyway. The one in post #1 looks like it connected fine.
Have you searched on the NM bugtracker?

chrisp1090 · 2013-10-04 15:04:36

It connects properly if I remove the connection profile from NM and completely reenter the information. If I try to connect without doing that it doesn't even attempt to connect. It doesn't even show up in the logs.

Strike0 · 2013-10-04 19:24:38

You mean, if you do a

# journalctl -f

and then try to let it connect, nothing happens in the log?

chrisp1090 · 2013-10-04 19:37:05

I was actually able to connect after launching nm-applet from the terminal. It prompted me for my password because somehow the credentials haven't been saving to my keyring. I'm not sure why nm-applet doesn't automatically launch and prompt for a password.

[user@host ~]$ nm-applet 

** (nm-applet:11606): WARNING **: Error connecting to ModemManager: Error calling StartServiceByName for org.freedesktop.ModemManager1: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
** Message: No keyring secrets found for network/802-1x; asking user.

** (nm-applet:11606): CRITICAL **: write_one_secret_to_keyring: assertion `type == G_TYPE_STRING' failed

chrisp1090 · 2013-10-07 19:05:35

Somehow this issue fixed itself after the recent nm-applet upgrade.

Arch Linux

#1 2013-10-01 23:38:16

NetworkManager requires me to "forget" a saved network to connect

#2 2013-10-04 01:32:40

Re: NetworkManager requires me to "forget" a saved network to connect

#3 2013-10-04 01:34:11

Re: NetworkManager requires me to "forget" a saved network to connect

#4 2013-10-04 01:48:29

Re: NetworkManager requires me to "forget" a saved network to connect

#5 2013-10-04 15:04:36

Re: NetworkManager requires me to "forget" a saved network to connect

#6 2013-10-04 19:24:38

Re: NetworkManager requires me to "forget" a saved network to connect

#7 2013-10-04 19:37:05

Re: NetworkManager requires me to "forget" a saved network to connect

#8 2013-10-07 19:05:35

Re: NetworkManager requires me to "forget" a saved network to connect

Board footer