No entries can be created/saved in Network Manager

queequeg · December 8, 2014, 5:43am

I did a clean install of 13.2 a few days ago, and everything seemed to be working fine. My Network Manager widget showed my default wired connection, and I was able to create a VPN connection that I need for work. Today, the network manager widget shows no entries, and I’m unable to create any entries. I checked the network settings in Yast, and it is still set to have Network Manager manage everything.

Any ideas as to what may have changed, or how to fix would be greatly appreciated. I should mention that my default connection to the internet still seems to be working (as that is what I’m using to type this right now).

A few screenshots:
Blank Network Manager Widget
http://i.imgur.com/2HmK5Y2.png
Blank Connection Editor. I can go through the motions to create new connections, but they don’t save.
http://i.imgur.com/bg2Rnqy.png
Yast network settings showing NetworkManager is indeed managing things.
http://i.imgur.com/5NPotXg.png

queequeg · December 10, 2014, 2:28pm

More Info: If I log out and then back in again, the network manager widget (plasma-nm) correctly displays all the saved connections, and lets me create/edit again. When I reboot, they go missing again like in my original post. It appears it’s not starting correctly at boot, or maybe it’s starting twice? Is there any way to check?

Pic after logging out/in. (See op for how it looks after reboot)
http://i.imgur.com/0I9xiiw.png
http://i.imgur.com/puxqjxj.png

keellambert · December 11, 2014, 12:55am

suggestion

select ‘Wicked Service’ in Yast and setup the connections required
then do a cold reboot

then run through the cmds in the Release Notes for NetworkManager,
‘1.2. Network After an Update With YaST’
(available from within Yast)

hth

queequeg · December 11, 2014, 5:33am

Thank you for responding!
I went through the procedure as you suggested (below). Unfortunately, after the reboot the problem persists. Could it be a problem with the plasma-nm widget? It appears NetworkManager is running properly, I just can’t access it through the widget until after logging out/in…
[FONT=inherit][FONT=inherit][FONT=inherit]1.2 Network After an Update With YaST #](https://doc.opensuse.org/release-notes/x86_64/openSUSE/13.2/#idm140406408653728)[/FONT]
[/FONT]
[/FONT]
After updating from 13.1 to 13.2 using YaST, there are good chances that the new Wicked network method is running together with the old NetworkManager, if you are using a laptop with a wifi connection.
To solve this, first disable Wicked and enable again NetworkManager:
systemctl is-active network.service && systemctl stop network.service
systemctl is-active wickedd.service && systemctl stop wickedd.service
systemctl disable wicked.service
systemctl --force enable NetworkManager.service
systemctl start network.service
Then check whether the currently selected service is actually NetworkManager:
systemctl -p Id show network.service
And update /etc/resolv.conf:
netconfig update
Or reboot after the systemctl commands to restart also wpa_suplicant.

keellambert · December 11, 2014, 11:44am

try changing the names of (or moving to another directory) all files in
/etc/NetworkManager/system-connections/

then repeat the procedure in post #3 above
(remember to correctly setup your i/f in ‘Wicked Service’ (as thought it was
going to be used) in all tabs before rebooting)

queequeg · December 12, 2014, 5:04am

Thank you again. Did as you said, and the problem persists. (It works fine after logging out/in, but after a reboot everything is missing again until I log in/out again).

keellambert · December 12, 2014, 11:39am

does the cmd
sudo systemctl restart network.service
change anything?

queequeg · December 13, 2014, 5:01am

Thank you again for responding! Unfortunately, the command doesn’t appear to have any effect.

deano_ferrari · December 13, 2014, 6:12am

A strange problem indeed. It makes me wonder if your wired interface is being affected by power management perhaps? When you boot up and the NM shows no connection, what is reported by

/sbin/ifconfig

nmcli d

Maybe check the output of the following too

cat /var/lib/NetworkManager/NetworkManager.state

Also, anything unusual noticed in /var/log/NetworkManager?

deano_ferrari · December 13, 2014, 6:29am

Instead of logging out and back in, it would be useful to note what is logged when the ethernet connection is unplugged and plugged back in.

One of the following should help with that

sudo tail -f /var/log/messages

sudo journalctl -f

sudo tail -f /var/log/NetworkManager

and when that is done, does the connection then show in NM?

queequeg · December 13, 2014, 6:47am

deano_ferrari:

A strange problem indeed. It makes me wonder if your wired interface is being affected by power management perhaps? When you boot up and the NM shows no connection, what is reported by
/sbin/ifconfig
nmcli d
Maybe check the output of the following too
cat /var/lib/NetworkManager/NetworkManager.state
Also, anything unusual noticed in /var/log/NetworkManager?

Agreed, very strange.
Here are the results:

queequeg@ODIN:~> /sbin/ifconfig 
enp5s0    Link encap:Ethernet  HWaddr D8:CB:8A:15:94:48  
          inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::dacb:8aff:fe15:9448/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:126082 errors:0 dropped:0 overruns:0 frame:0
          TX packets:102014 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:129724047 (123.7 Mb)  TX bytes:15136697 (14.4 Mb)


lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:276 errors:0 dropped:0 overruns:0 frame:0
          TX packets:276 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:193410 (188.8 Kb)  TX bytes:193410 (188.8 Kb)

queequeg@ODIN:~> nmcli d
DEVICE  TYPE      STATE      CONNECTION 
enp5s0  ethernet  connected  --         
lo      loopback  unmanaged  --

queequeg@ODIN:~> sudo cat /var/lib/NetworkManager/NetworkManager.state
root's password:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
WiMAXEnabled=true

queequeg · December 13, 2014, 6:57am

deano_ferrari:

Instead of logging out and back in, it would be useful to note what is logged when the ethernet connection is unplugged and plugged back in.

One of the following should help with that
sudo tail -f /var/log/messages
sudo journalctl -f
sudo tail -f /var/log/NetworkManager
and when that is done, does the connection then show in NM?

These files don’t seem to exist?:


queequeg@ODIN:~> sudo tail -f /var/log/messages
tail: cannot open ‘/var/log/messages’ for reading: No such file or directory
tail: no files remaining


queequeg@ODIN:~> sudo tail -f /var/log/NetworkManager
tail: cannot open ‘/var/log/NetworkManager’ for reading: No such file or directory
tail: no files remaining

The journalctl command gives me a million of these in a row:

Dec 12 22:48:32 ODIN.site kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0014 address=0x0000000000001000 flags=0x0000]

I have no ides what that error is (and am pretty sure it’s unrelated) but it persists after logging off/on or unplugging/replugging

deano_ferrari · December 13, 2014, 7:02am

Well the wired device is present and you are connected


enp5s0    Link encap:Ethernet  HWaddr D8:CB:8A:15:94:48  
          inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::dacb:8aff:fe15:9448/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:126082 errors:0 dropped:0 overruns:0 frame:0
          TX packets:102014 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:129724047 (123.7 Mb)  TX bytes:15136697 (14.4 Mb)

queequeg@ODIN:~> nmcli d
DEVICE  TYPE      STATE      CONNECTION 
enp5s0  ethernet  connected  --         
lo      loopback  unmanaged  --

So, if I understand you correctly, it is just the GUI which does not reflect this? (BTW, I think I may be experiencing the same with KDE 4.14.3)

deano_ferrari · December 13, 2014, 7:15am

queequeg:

These files don’t seem to exist?:
queequeg@ODIN:~> sudo tail -f /var/log/messages
tail: cannot open ‘/var/log/messages’ for reading: No such file or directory
tail: no files remaining
This just means you’re not logging via syslog. (I am.)
queequeg@ODIN:~> sudo tail -f /var/log/NetworkManager
tail: cannot open ‘/var/log/NetworkManager’ for reading: No such file or directory
tail: no files remaining
I’m perplexed about that, but someone else may be able to answer this.

The journalctl command gives me a million of these in a row:
Dec 12 22:48:32 ODIN.site kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=01:00.0 domain=0x0014 address=0x0000000000001000 flags=0x0000]
I have no ides what that error is (and am pretty sure it’s unrelated) but it persists after logging off/on or unplugging/replugging

I expected to see you capture the ethernet status events eg when I unlplug and plug in the ethernet cable I get

Dec 13 19:14:26 linux-bbgi.site kernel: tg3 0000:18:00.0 ens1: Link is down
Dec 13 19:14:26 linux-bbgi.site NetworkManager[648]: <info> (ens1): carrier now OFF (device state 100, ...ds)
Dec 13 19:14:29 linux-bbgi.site kernel: tg3 0000:18:00.0 ens1: Link is up at 100 Mbps, full duplex
Dec 13 19:14:29 linux-bbgi.site kernel: tg3 0000:18:00.0 ens1: Flow control is on for TX and on for RX
Dec 13 19:14:29 linux-bbgi.site NetworkManager[648]: <info> (ens1): carrier now ON (device state 100)

queequeg · December 13, 2014, 7:18am

deano_ferrari:

Well the wired device is present and you are connected


enp5s0    Link encap:Ethernet  HWaddr D8:CB:8A:15:94:48  
          inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::dacb:8aff:fe15:9448/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:126082 errors:0 dropped:0 overruns:0 frame:0
          TX packets:102014 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:129724047 (123.7 Mb)  TX bytes:15136697 (14.4 Mb)

queequeg@ODIN:~> nmcli d
DEVICE  TYPE      STATE      CONNECTION 
enp5s0  ethernet  connected  --         
lo      loopback  unmanaged  --

So, if I understand you correctly, it is just the GUI which does not reflect this? (BTW, I think I may be experiencing the same with KDE 4.14.3)

Correct, the network seems to be functioning correctly, it just seems to be the plasma-nm widget that isn’t displaying things properly. Unfortunately, I need to use a VPN connection for work that is set up through the widget.

queequeg · December 13, 2014, 7:21am

deano_ferrari:

I expected to see you capture the ethernet status events eg when I unlplug and plug in the ethernet cable I get

Dec 13 19:14:26 linux-bbgi.site kernel: tg3 0000:18:00.0 ens1: Link is down
Dec 13 19:14:26 linux-bbgi.site NetworkManager[648]: <info> (ens1): carrier now OFF (device state 100, ...ds)
Dec 13 19:14:29 linux-bbgi.site kernel: tg3 0000:18:00.0 ens1: Link is up at 100 Mbps, full duplex
Dec 13 19:14:29 linux-bbgi.site kernel: tg3 0000:18:00.0 ens1: Flow control is on for TX and on for RX
Dec 13 19:14:29 linux-bbgi.site NetworkManager[648]: <info> (ens1): carrier now ON (device state 100)

Sorry about that, it looks like I had another issue. (I had to add iommu=soft to my kernel parameters to get rid of the weird AMD-VI error posted earlier.)

Here’s the results when I unplug/plug with journalctl -f (pretty long):

Dec 12 23:15:21 ODIN.site kernel: r8169 0000:05:00.0 enp5s0: link down
Dec 12 23:15:21 ODIN.site NetworkManager[979]: <info> (enp5s0): link disconnected (deferring action for 4 seconds)
Dec 12 23:15:25 ODIN.site NetworkManager[979]: <info> (enp5s0): link disconnected (calling deferred action)
Dec 12 23:15:25 ODIN.site NetworkManager[979]: <info> (enp5s0): device state change: activated -> unavailable (reason 'carrier-changed') [100 20 40]
Dec 12 23:15:25 ODIN.site NetworkManager[979]: <info> (enp5s0): deactivating device (reason 'carrier-changed') [40]
Dec 12 23:15:25 ODIN.site dhclient[1853]: Received signal 15, initiating shutdown.
Dec 12 23:15:25 ODIN.site NetworkManager[979]: Received signal 15, initiating shutdown.
Dec 12 23:15:25 ODIN.site dhclient[1853]: DHCPRELEASE on enp5s0 to 192.168.2.1 port 67 (xid=0x1873d4a5)                                                                           
Dec 12 23:15:25 ODIN.site NetworkManager[979]: DHCPRELEASE on enp5s0 to 192.168.2.1 port 67 (xid=0x1873d4a5)                                                                      
Dec 12 23:15:26 ODIN.site NetworkManager[979]: <warn> (enp5s0): DHCP client pid 1853 didn't exit, will kill it.                                                                   
Dec 12 23:15:26 ODIN.site NetworkManager[979]: <info> (enp5s0): canceled DHCP transaction, DHCP client pid 1853                                                                   
Dec 12 23:15:26 ODIN.site avahi-daemon[871]: Withdrawing address record for fe80::dacb:8aff:fe15:9448 on enp5s0.                                                                  
Dec 12 23:15:26 ODIN.site avahi-daemon[871]: Leaving mDNS multicast group on interface enp5s0.IPv6 with address fe80::dacb:8aff:fe15:9448.                                        
Dec 12 23:15:26 ODIN.site avahi-daemon[871]: Interface enp5s0.IPv6 no longer relevant for mDNS.                                                                                   
Dec 12 23:15:26 ODIN.site avahi-daemon[871]: Withdrawing address record for 192.168.2.2 on enp5s0.                                                                                
Dec 12 23:15:26 ODIN.site avahi-daemon[871]: Leaving mDNS multicast group on interface enp5s0.IPv4 with address 192.168.2.2.                                                      
Dec 12 23:15:26 ODIN.site avahi-daemon[871]: Interface enp5s0.IPv4 no longer relevant for mDNS.                                                                                   
Dec 12 23:15:26 ODIN.site NetworkManager[979]: <info> NetworkManager state is now CONNECTED_LOCAL                                                                                 
Dec 12 23:15:26 ODIN.site NetworkManager[979]: <info> NetworkManager state is now DISCONNECTED                                                                                    
Dec 12 23:15:26 ODIN.site dbus[880]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'              
Dec 12 23:15:26 ODIN.site dbus[880]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'                                                                      
Dec 12 23:15:26 ODIN.site nm-dispatcher[2770]: Dispatching action 'down' for enp5s0                                                                                               
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> (enp5s0): link connected                                                                                                    
Dec 12 23:15:34 ODIN.site kernel: r8169 0000:05:00.0 enp5s0: link up                                                                                                              
Dec 12 23:15:34 ODIN.site kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready                                                                                       
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> (enp5s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]                            
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Auto-activating connection 'Wired connection 1'.                                                                            
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) starting connection 'Wired connection 1'                                                                
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 1 of 5 (Device Prepare) scheduled...                                                              
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 1 of 5 (Device Prepare) started...                                                                
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> (enp5s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> NetworkManager state is now CONNECTING
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 2 of 5 (Device Configure) scheduled...
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 1 of 5 (Device Prepare) complete.
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 2 of 5 (Device Configure) starting...
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> (enp5s0): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 2 of 5 (Device Configure) successful.
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 2 of 5 (Device Configure) complete.
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 3 of 5 (IP Configure Start) started...
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> (enp5s0): device state change: config -> ip-config (reason 'none') [50 70 0]
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> dhclient started with pid 2884
Dec 12 23:15:34 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 3 of 5 (IP Configure Start) complete.
Dec 12 23:15:35 ODIN.site dhclient[2884]: Internet Systems Consortium DHCP Client 4.2.6
Dec 12 23:15:35 ODIN.site dhclient[2884]: Copyright 2004-2014 Internet Systems Consortium.
Dec 12 23:15:35 ODIN.site dhclient[2884]: All rights reserved.
Dec 12 23:15:35 ODIN.site dhclient[2884]: For info, please visit https://www.isc.org/software/dhcp/
Dec 12 23:15:35 ODIN.site dhclient[2884]: 
Dec 12 23:15:35 ODIN.site NetworkManager[979]: Internet Systems Consortium DHCP Client 4.2.6
Dec 12 23:15:35 ODIN.site NetworkManager[979]: Copyright 2004-2014 Internet Systems Consortium.
Dec 12 23:15:35 ODIN.site NetworkManager[979]: All rights reserved.
Dec 12 23:15:35 ODIN.site NetworkManager[979]: For info, please visit https://www.isc.org/software/dhcp/
Dec 12 23:15:35 ODIN.site NetworkManager[979]: <info> (enp5s0): DHCPv4 state changed nbi -> preinit
Dec 12 23:15:35 ODIN.site dhclient[2884]: Listening on LPF/enp5s0/d8:cb:8a:15:94:48
Dec 12 23:15:35 ODIN.site dhclient[2884]: Sending on   LPF/enp5s0/d8:cb:8a:15:94:48
Dec 12 23:15:35 ODIN.site dhclient[2884]: Sending on   Socket/fallback
Dec 12 23:15:35 ODIN.site dhclient[2884]: DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 3 (xid=0x38671db4)
Dec 12 23:15:35 ODIN.site NetworkManager[979]: Listening on LPF/enp5s0/d8:cb:8a:15:94:48
Dec 12 23:15:35 ODIN.site NetworkManager[979]: Sending on   LPF/enp5s0/d8:cb:8a:15:94:48
Dec 12 23:15:35 ODIN.site NetworkManager[979]: Sending on   Socket/fallback
Dec 12 23:15:35 ODIN.site NetworkManager[979]: DHCPDISCOVER on enp5s0 to 255.255.255.255 port 67 interval 3 (xid=0x38671db4)
Dec 12 23:15:35 ODIN.site dhclient[2884]: DHCPOFFER from 192.168.2.1
Dec 12 23:15:35 ODIN.site NetworkManager[979]: DHCPOFFER from 192.168.2.1
Dec 12 23:15:36 ODIN.site avahi-daemon[871]: Joining mDNS multicast group on interface enp5s0.IPv6 with address fe80::dacb:8aff:fe15:9448.
Dec 12 23:15:36 ODIN.site avahi-daemon[871]: New relevant interface enp5s0.IPv6 for mDNS.
Dec 12 23:15:36 ODIN.site avahi-daemon[871]: Registering new address record for fe80::dacb:8aff:fe15:9448 on enp5s0.*.
Dec 12 23:15:36 ODIN.site kernel: SFW2-INext-DROP-DEFLT IN=enp5s0 OUT= MAC= SRC=fe80:0000:0000:0000:dacb:8aff:fe15:9448 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=84 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=44 
Dec 12 23:15:36 ODIN.site kernel: SFW2-INext-DROP-DEFLT IN=enp5s0 OUT= MAC= SRC=fe80:0000:0000:0000:dacb:8aff:fe15:9448 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=406 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=366 
Dec 12 23:15:36 ODIN.site kernel: SFW2-INext-DROP-DEFLT IN=enp5s0 OUT= MAC= SRC=fe80:0000:0000:0000:dacb:8aff:fe15:9448 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=240 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=200 
Dec 12 23:15:36 ODIN.site kernel: SFW2-INext-DROP-DEFLT IN=enp5s0 OUT= MAC= SRC=fe80:0000:0000:0000:dacb:8aff:fe15:9448 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=406 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=366 
Dec 12 23:15:36 ODIN.site kernel: SFW2-INext-DROP-DEFLT IN=enp5s0 OUT= MAC= SRC=fe80:0000:0000:0000:dacb:8aff:fe15:9448 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=406 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=366 
Dec 12 23:15:40 ODIN.site dhclient[2884]: DHCPREQUEST on enp5s0 to 255.255.255.255 port 67 (xid=0x38671db4)
Dec 12 23:15:40 ODIN.site NetworkManager[979]: DHCPREQUEST on enp5s0 to 255.255.255.255 port 67 (xid=0x38671db4)
Dec 12 23:15:40 ODIN.site dhclient[2884]: DHCPACK from 192.168.2.1 (xid=0x38671db4)
Dec 12 23:15:40 ODIN.site NetworkManager[979]: DHCPACK from 192.168.2.1 (xid=0x38671db4)
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info> (enp5s0): DHCPv4 state changed preinit -> bound
Dec 12 23:15:40 ODIN.site dhclient[2884]: bound to 192.168.2.2 -- renewal in 2147483648 seconds.
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info>   address 192.168.2.2
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info>   plen 24 (255.255.255.0)
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info>   gateway 192.168.2.1
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info>   server identifier 192.168.2.1
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info>   lease time -1
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info>   nameserver '208.67.222.222'
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info>   nameserver '208.67.220.220'
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 5 of 5 (IPv4 Commit) started...
Dec 12 23:15:40 ODIN.site avahi-daemon[871]: Joining mDNS multicast group on interface enp5s0.IPv4 with address 192.168.2.2.
Dec 12 23:15:40 ODIN.site avahi-daemon[871]: New relevant interface enp5s0.IPv4 for mDNS.
Dec 12 23:15:40 ODIN.site avahi-daemon[871]: Registering new address record for 192.168.2.2 on enp5s0.IPv4.
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info> (enp5s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) Stage 5 of 5 (IPv4 Commit) complete.
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info> (enp5s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info> (enp5s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info> NetworkManager state is now CONNECTED_LOCAL
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info> NetworkManager state is now CONNECTED_GLOBAL
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info> Policy set 'Wired connection 1' (enp5s0) as default for IPv4 routing and DNS.
Dec 12 23:15:40 ODIN.site NetworkManager[979]: <info> Activation (enp5s0) successful, device activated.
Dec 12 23:15:40 ODIN.site dbus[880]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Dec 12 23:15:40 ODIN.site NetworkManager[979]: bound to 192.168.2.2 -- renewal in 2147483648 seconds.
Dec 12 23:15:40 ODIN.site dbus[880]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 12 23:15:40 ODIN.site nm-dispatcher[2891]: Dispatching action 'up' for enp5s0

deano_ferrari · December 13, 2014, 7:28am

Well, it appears NM is handling the deivce as expected despite what the front-end shows or not.

queequeg · December 13, 2014, 7:37am

Yes, that’s the one good thing. You mentioned you may be able to reproduce on KDE 4.14.3. I’m running that version (4.14.3-4.9). Is there a different version I should switch to?

Thanks again for all your help!

deano_ferrari · December 13, 2014, 7:46am

No, but I think that we’ve hit a bug. It may have been reported already. We should search for existing bug reports first. It hasn’t really come to my attention previously, since I mostly connect via wireless with my laptop, but in the course of my work with ocnfiguring wireless equipment, switches, and routers, I think I may have experienced this on occaision recently while changing wireed connections frequently.

queequeg · December 13, 2014, 8:13am

I searched bugzilla and couldn’t find anything that matched. The applet is “plasma-nm”, correct?