Network Manager showing duplicate entries and cannot reconnect

On tumbleweed 20180915 Kde, Network Manager applet shows multiple entries for same access point,
connects just once per login, to change network have to logout and log back in.

Other erroneous behaviour I’m facing are:
Asking for passkey for known networks
connecting to ethernet even when no cable is plugged in :disapointed:.

Don’t see that here. Was ‘zypper dup’ used to upgrade ?

Yes I use zypper dup every time I update from the command line.
Current version on my pc is tumbleweed 20180915
I’ll dup again and report.

Updated to opensuse 20181004 with zypper dup
Issue persists.

Can you run the following command and post the contents?
Be sure to inspect to make sure no passwords are displayed before posting…

cat /etc/wpa_supplicant/wpa_supplicant.conf

TSU

Running


sudo cat /etc/wpa_supplicant/wpa_supplicant.conf

Gives just these two lines:


ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel

It seems that Network Manager stores its WiFi connections differently than when I last studied NM in depth.

WiFi connections are now stored in the following location, wired connections are stored here…

/etc/NetworkManager/system-connections/

Inspect the above location for duplicate files and each file for duplicate content.

TSU

It’s been that way for years.:wink:

…including other NM connection types (Ethernet, VPN,…)

Wired connections are stored there, too, if you change anything from the defaults.

My suggestion would be to delete all connection information, and then start over reconfiguring anew.

The best way to do this would be to boot to single user mode. At the grub prompt, hit ‘e’, and scroll down to fine the line beginning “linux” (or “linuxefi”). Hit the END key to get to the end of that boot command. Then enter " 1" at the end (without the quotes). Then use CTRL-X to confinue booting.

That should get you to a command line, where you can login as root (I hope you remember the root password).

The reason that I suggest single-user mode, is so that networking won’t be running.
Then, at the root command line:


cd /etc/NetworkManager/system-connections
rm -rf *
cd /var/lib/NetworkManager
rm -rf *

This should delete all connection information for all defined connections.

Then reboot to your normal desktop and reconfigure connections.

IMPORTANT NOTE: If those “cd” commands return an error, then skip the “rm” commands and start over.

You could also use the “ls” command just before the “rm” to see what you will be deleting. The first directory should have only a small number of files, typically one per connection. The second directory may have several files per connection, where the DHCP lease is recorded.

There are multiple files for each network in the form of network-name, network-name-uuid1, network-name-uuid2 etc.
Also running diff on them


< uuid=7ade3028-1b2a-4480-ac55-0a62c8c3d04e
---
> uuid=4f4c50f6-a361-47e9-bb31-7e72f9b651b3

Also some differ in user name, it is a user I once created and deleted.
Everything else like mac address etc is the same in duplicates.
Also it does not show duplicates when wifi settings are opened through the kde widget.

I did this and no longer see duplicates in available connections.
I rebooted and connected to 2 networks just fine. But for testing:
I went to airplane mode and back with the applet and then the kde applet crashed.
Restarted Network manager through yast
Now the applet had forgotten all networks and started connecting to some wired connection (I have no wired connection, not even usb tethering and nothing is connected to it)
After this clicking connect only refreshes the network list.
This behavior also happens sometimes after suspend or disconnecting.

The only way it returns back to normal is to log out and log back in.

screenshot:
https://paste.opensuse.org/30219350

I will admit that I have never switched to airplane mode. Maybe I’ll experiment with that tomorrow.

I have, but I’m using Leap and I haven’t experienced NetworkManager instability for years.

running:

sudo journalctl -u NetworkManager.service

This is log of the session in which this happened:
https://paste.opensuse.org/42614680

Network Manager does crash on tumbleweed installed on my pc.
From where can I get more information?.
This problem may be specific to my hardware / configuration.

Very strange.

This caught my attention…




  1. Oct  11 10:19:00 user NetworkManager[1445]: <info>  [1539233340.0789]  manager: (lo): new Generic device  (/org/freedesktop/NetworkManager/Devices/1)


  1. Oct  11 10:19:00 user NetworkManager[1445]: <info>  [1539233340.0798]  manager: (enp0s20f0u3c4i2): new Ethernet device  (/org/freedesktop/NetworkManager/Devices/2)

  1. Oct  11 10:19:00 user NetworkManager[1445]: <info>  [1539233340.0811]  keyfile: add connection in-memory  (d1da349c-b9c0-3a10-9c8e-feca02831ffd,"Wired connection 1")

  1. Oct  11 10:19:00 user NetworkManager[1445]: <info>  [1539233340.0815]  settings: (enp0s20f0u3c4i2): created default wired connection 'Wired  connection 1'

  1. Oct  11 10:19:00 user NetworkManager[1445]: <info>  [1539233340.0820]  device (enp0s20f0u3c4i2): state change: unmanaged -> unavailable  (reason 'managed', sys-iface-state: 'external')

  1. Oct  11 10:19:00 user NetworkManager[1445]: <info>  [1539233340.0850]  manager: (p4p2): new Ethernet device  (/org/freedesktop/NetworkManager/Devices/3)

  1. Oct  11 10:19:00 user NetworkManager[1445]: <info>  [1539233340.0861]  keyfile: add connection in-memory  (5b995c66-8542-3bb7-9f81-b65f97240c89,"Wired connection 2")

  1. Oct  11 10:19:00 user NetworkManager[1445]: <info>  [1539233340.0865]  settings: (p4p2): created default wired connection 'Wired connection 2'

  1. Oct  11 10:19:00 user NetworkManager[1445]: <info>  [1539233340.0871]  device (p4p2): state change: unmanaged -> unavailable (reason  'managed', sys-iface-state: 'external')




It likely has something to do with udev interface renaming, and apparently causing confusion with NetworkManager.

What do the following report?

nmcli d
ip link

running nmcli d:


DEVICE      TYPE      STATE        CONNECTION 
wlp2s0      wifi      connected    EACCESS    
virbr0      bridge    connected    virbr0     
p4p2        ethernet  unavailable  --         
lo          loopback  unmanaged    --         
virbr0-nic  tun       unmanaged    --         

runnning ip link:


1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: p4p2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether d4:81:d7:70:c5:f9 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether 70:1c:e7:dd:fc:ac brd ff:ff:ff:ff:ff:ff
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 52:54:00:83:b0:ca brd ff:ff:ff:ff:ff:ff
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN mode DEFAULT group default qlen 1000
    link/ether 52:54:00:83:b0:ca brd ff:ff:ff:ff:ff:ff

I know you said that your ethernet port is not connected…and yet an active ethernet carrier is detected…

Oct 11 10:25:01 user NetworkManager[4590]: <info>  [1539233701.7961] device (enp0s20f0u3c4i2): carrier: link connected
Oct  11 10:25:01 user NetworkManager[4590]: <info>  [1539233701.7975]  device (enp0s20f0u3c4i2): state change: unavailable -> disconnected  (reason 'carrier-changed', sys-iface-state: 'managed')

Curious - what is the network bridge for?