Internet-surfing gave me some results.
For me this bug doesn't reproduce if kded4 starts with networkstatus module (service) turned off. This idea was suggested here: https://bugs.kde.org/show_bug.cgi?id=220047#c28
But the module was loading always even when disabled in Service Manager or via qdbus. So to turn it off completely I had to edit /usr/share/kde4/services/kded/networkstatus.desktop
$ sudo nano /usr/share/kde4/services/kded/networkstatus.desktop
There I set autoload and load-on-demand options to false:
Internet-surfing gave me some results. /bugs.kde. org/show_ bug.cgi? id=220047# c28 kde4/services/ kded/networksta tus.desktop kde4/services/ kded/networksta tus.desktop
For me this bug doesn't reproduce if kded4 starts with networkstatus module (service) turned off. This idea was suggested here: https:/
But the module was loading always even when disabled in Service Manager or via qdbus. So to turn it off completely I had to edit /usr/share/
$ sudo nano /usr/share/
There I set autoload and load-on-demand options to false:
X-KDE-Kded- autoload= false load-on- demand= false
X-KDE-Kded-
Then - unloaded the module manually
$ qdbus org.kde.kded /kded unloadModule networkstatus
and restarted kded4
$ qdbus org.kde.kded /kded quit
$ kded4 &
Now I can trigger wlan connection without problems, but without networkstatus service.