Bug 209675

Summary: knetworkmanager has to be killed and restarted for connection property changes to to take effect
Product: [Unmaintained] knetworkmanager Reporter: Tamás Németh <nt1277>
Component: generalAssignee: Will Stephenson <wstephenson>
Status: RESOLVED FIXED    
Severity: normal CC: sven.burmeister
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: knetworkmanager in ambiguous state

Description Tamás Németh 2009-10-06 21:49:24 UTC 
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.
Comment 1 Tamás Németh 2009-10-13 13:59:20 UTC 
Created attachment 37553 [details]
knetworkmanager in ambiguous state
Comment 2 Will Stephenson 2009-11-17 19:13:37 UTC 
Fixed by r1047763
Comment 3 Will Stephenson 2009-11-17 19:16:40 UTC 
*** Bug 210601 has been marked as a duplicate of this bug. ***
Comment 4 Tamás Németh 2010-05-25 20:24:41 UTC 
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?