Version: 0.9.svn1028043 (using KDE 4.3.1) OS: Linux Installed from: SuSE RPMs I created some connection entries during testing and edited them during the test process. I sadly had to realize that every time I changed something in a connection (at least for wireless WPA-Enterprise connections), I had to kill and restart knetworkmanager for the changes to take effect. For example I configured a connection with DHCP address, but then changed it to manually, and in spite of this, next time NetworkManager obtained a DHCP address again. Then I created a connection with certificate validation required (which doesn't work: https://bugs.kde.org/show_bug.cgi?id=209673), and later I turned off certificate validation, but NetworkManager tried to validate the server certificate (as seen in /var/log/NetworkManager) until I restarted knetworkmanager (NetworkManager doesn't have to be restarted). Interestingly, the data shown by 'qdbus --system --literal ...' changes immediately after data edition in knetworkmanager, but the actual behaviour of NetworkManagers remains unchanged until restarting knetworkmanager. BTW, I'm using NetworkManager 0.7.0.r4359 of openSUSE 11.1.
Created attachment 37553 [details] knetworkmanager in ambiguous state
Fixed by r1047763
*** Bug 210601 has been marked as a duplicate of this bug. ***
During testing for https://bugs.kde.org/show_bug.cgi?id=209673 I still had to kill and restart knetworkmanager 0.9.svn1057339 after changing the certificate file name in the dialog box (which appears automatically after some unsuccessful connection attempts) of knetworkmanager. Probably not entirely solved?