Hi Mathieu, you can happily close this bug as there is probably nobody who is still affected with this bug after almost 3 years.
I know that this kind of support is free and based on willingness of people. But this is still a waste of your time. If there was nobody from april 2009 who could have a look at this problem, now it is really too late. I am sorry to say it. Anyway, thank you for your information. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/355833 Title: [Jaunty beta] KDE Connection Manager does not work for WEP Status in “network-manager” package in Ubuntu: Incomplete Bug description: I can not connect to my network with KDE Network manager. If I run following commands from command line, it works well: > sudo iwconfig eth1 essid VPLan > sudo iwconfig eth1 key restricted dead-beef-00 > sudo ifconfig eth1 192.168.1.99 up > sudo route add default gw 192.168.1.254 > echo nameserver 192.168.1.254 > /etc/resolv.conf I use WEP with hexadecimal key. In fact, I am filling this bug from system configured that way. "Network management" icon is anyway not aware that I have connection and says "eth1: Not connected". If KDE Network Manager is not able to set this network, where should I put it to have the configuration permanent after each boot of the system ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/355833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
