Bug 342007

Could you enable plasma-nm in kdebugdialog and start plasma-desktop from console, do all the steps you mentioned and send me the output? Also output from "nmcli -f all -p device show" after you do all mentioned steps could be useful.

Created attachment 90042 [details]
Debug output from plasma-nm

Attached is the debug output per your request. Also, "nmcli -f all -p device show" yields an error, but

~> nmcli -f all -p device 
=======================================================================================
                                   Status of devices
=======================================================================================
DEVICE     TYPE              STATE         DBUS-PATH                                  
---------------------------------------------------------------------------------------
eth_s4_0   802-3-ethernet    connected     /org/freedesktop/NetworkManager/Devices/2  
br0        bridge            connected     /org/freedesktop/NetworkManager/Devices/1  
enp2s0     802-3-ethernet    unavailable   /org/freedesktop/NetworkManager/Devices/0

Send please complete output, I don't see plasma-nm initialization. You probably need to open the applet after you restart plasma-desktop to initialize it (or this is necessary only in Plasma 5, I'm not sure right now). Try just "nmcli -p device show", in older versions it prints automatically all details. What version of NetworkManager do you have?

Created attachment 90045 [details]
Full debug output

Hopefully this is enough, with long output from irrelevant plasmoids deleted. Also,

> nmcli -p device show
Usage: nmcli device { COMMAND | help }

  COMMAND := { status | list | disconnect | wifi }

  status
  list [iface <iface>]
  disconnect iface <iface> [--nowait] [--timeout <timeout>]
  wifi [list [iface <iface>] [bssid <BSSID>]]
  wifi connect <(B)SSID> [password <password>] [wep-key-type key|phrase] [iface <iface>] [bssid <BSSID>] [name <name>]
               [--private] [--nowait] [--timeout <timeout>]

Error: 'dev' command 'show' is not valid.
> rpm -q NetworkManager
NetworkManager-0.9.8.8-10.1.x86_64

Just upgraded to openSUSE 13.2 with NetworkManager-0.9.10.0. The plasmoid still has problems with the active connections: when I restart Networkmanager, no active connections appear under certain circumstances. Also, NetworkManager appears to be buggy, because when I disconnect the bridge while the VPN connection is active, often the bridge loses its interfaces and no connection is possible unless I restart NM.

Is the situation different with Plasma 5?

With Plasma 5.5.1 and NetworkManager 1.0.6, it is impossible to reconnect to the bridge after disconnection without restarting NetworkManager, therefore I'm unable to test for this problem.

Does it work using nmcli? Anyway, we just filtered out "interprise" devices like bridge, bond etc. which are not that common on desktops so those connection types won't be shown in the applet anymore (for Plasma 5.6). You should be still able to configure them in our editor, however preferred way is to use nmcli as I'm not sure they have ever worked perfectly in plasma-nm.

This must be a bug in NetworkManager: if I disconnect the bridge, even with nmcli, it loses its interfaces (brctl showstp br0 is empty) and NetworkManager cannot connect to the network. Sometimes even restarting NetworkManager does not fix this and I must delete br0 first, then restart NM.

Ok, thanks for the information. I'm going to close this bug now as there is nothing we can fix in plasma-nm and support for bridge connections was dropped in the upcoming major version of plasma-nm.

Bulk transfer as requested in T17796