Version: unspecified (using KDE 4.4.95) OS: Linux The "Add Network Connection" dialog almost always pops up pre-populated with the details corresponding to some already existing connection, unrelated to the one I am trying to add. Reproducible: Sometimes Steps to Reproduce: I often need to add a new wireless connection. I initiate this process either by clicking the "Add..." button in the "Network Connections" KDE control module, or by clicking on a network connection in the toolbar applet. Actual Results: The "Add Network Connection" dialog almost always pops up pre-populated with the details corresponding to some already existing connection, unrelated to the one I am trying to add. (e.g. it shows something like "Connection name: Washington Dulles WiFi"; and all of the other details also correspond to the old connection rather than to the one I want to add. The old connection which appears seems to be chosen more-or-less randomly from my list of wireless connections; it has nothing to do with what networks are actually available at that moment.) If I dismiss the dialog and re-open it, it typically appears populated with the details corresponding to some _other_ pre-existing connection. After roughly 5 tries or so, the dialog eventually appears with "New Wireless Connection" as desired. From that point on, everything works fine. Expected Results: If it was invoked from the "Add..." button in the "Network Connections" KDE control module, the dialog should pop up showing "Connection name: New Wireless Connection". If it was invoked by clicking on a network connection in the toolbar applet, it should show the details relevant to the connection being added. I also had this problem in KDE 4.4 (and perhaps earlier -- I cannot remember exactly when I first noticed it.)
Duplicate of bug 250615
*** Bug 250615 has been marked as a duplicate of this bug. ***
I guess you are using the monolithic knetworkmanager version, is so then please use the plasmoid version. The monolithic knetworkmanager is unmaintained. I am not able to reproduce this problem with the plasmoid version, can you?
When I filed the bug report I was using the plasmoid, so at least at one time this bug did exist there. Actually, I am still using the plasmoid, but I no longer experience this bug in KDE 4.6.2.
*** Bug 267779 has been marked as a duplicate of this bug. ***