Bugzilla – Bug 382436
KNetworkManager allows duplicated names of connections
Last modified: 2009-07-02 09:46:01 UTC
There are a few possible situations: 1) Someone uses a few different networks with the same name 2) Someone needs a few configurations for some network 3) Someone just used the same name twice by mistake First two situations happen when user won't change default name of connection. OK, so what happens in theses situation? KNetoworkManager just shows a list of few connection called exactly the same name. That makes it hard/impossible to tell apart these configurations. I think KNetworkManager should add some suffix for duplicated names. For example: my_network my_network_2 my_network_3 If this is not KNetworkManager bug, but NetworkManager bug and I should report this somewhere else, please let me know.
Created attachment 209674 [details] Tricky situation with a few configurations with the same name
Yeah, absolutely correct. I try to get that done for the next Beta.
> 3) Someone just used the same name twice by mistake In this regard I miss a possibility to delete/edit items. (Due to some problem with a previous Factory version I have now 5 same items, of which only some work.)
Tobias: yes, you are right. I let myself report this wish. For making reports clean I've made this in new report as bug 384126
Hello I would like to see a way to remove old or incorrect entries instead of manually having to delete the file : ~/.kde/share/config/knetworkmanagerrc
James: this report had only 3 comments. Is that so hard to read theses before posting? Check comment #3 and #comment 4
Not fixed in Beta3.
This bug report is inactive since 5 month. Please reopen if the problem still persists.
I can enter the same Essid on 11.1 B2 (I stopped at 3) Note : I am connect to this Essid at the time
11.1 B2 took some screen shots (same Essid 2x & 3x but I can't see how to upload the .odt - sorry # details linux:~ # uname -a Linux linux.site 2.6.27-rc7-12-pae #1 SMP 2008-09-29 23:39:54 +0200 i686 i686 i386 GNU/Linux linux:~ # rpm -qa | grep network yast2-network-2.17.32-1.6 kdenetwork3-3.5.10-2.9 kdenetwork3-InstantMessenger-3.5.10-2.9 Thinkpad T60
KNetworkManager for KDE3 is not maintained any longer. Therefore I resolve all bugs that are still open as WONTFIX without looking at each single bug report. If this bug deals already with KDE4 and is still in progress, then please apologize the mistake and feel free to reopen it.