http://bugzilla.opensuse.org/show_bug.cgi?id=916394 --- Comment #1 from Freek de Kruijf --- Created attachment 622024 --> http://bugzilla.opensuse.org/attachment.cgi?id=622024&action=edit Attachment 2. Picture of popup window showing no wired connection. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916394 --- Comment #3 from Freek de Kruijf --- Yes. I checked that. At first I had the same icon on my laptop. I checked "ip a" and saw there was no wifi connection active. I restarted "systemctl restart NetworkManager.service", after that the icon became the familiar one. After the update from 20150201 to 20150203 I experience a lot of slowness in the system. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916394 --- Comment #5 from Freek de Kruijf --- Created attachment 622080 --> http://bugzilla.opensuse.org/attachment.cgi?id=622080&action=edit Attachment 3: Picture of popup of NM widget on laptop -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916394 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #7 from Wolfgang Bauer --- (In reply to Freek de Kruijf from comment #6)

This morning I started Tumbleweed and the icon shows OK as does the NM pop up window. It may have to do with a dbus service that did not start properly yesterday, due to a timeout, but does now (org.freedesktop.login1).

Definitely. Plasma-nm talks to NetworkManager via dbus (like any frontend), and logind (org.freedesktop.login1) is needed to grant your user the necessary permissions for certain things (you probably had audio problems as well, I suppose). Problems with dbus might also explain the "lot of slowness" you experienced. Many desktop things use dbus, and if dbus (or a particular service) is not working properly they are waiting for an answer (and hanging) until the ~30s timeout triggers. If it's working fine for you now, I suppose we can close this. If the dbus problems return, you probably should file a new bugreport about that. Btw, are you using autofs by chance? This sounds a bit like bug#905639 IMHO. -- You are receiving this mail because: You are on the CC list for the bug.