[Bug 270124] Re: knetworkmanager connects to untrusted networks

2009-09-03 Thread Jonathan Thomas
Thank you for taking the time to report this bug and helping to make Kubuntu better. The KDE3 version of KNetworkManager has been discontinued by its original authors. This unfortunately means that there will be no more bugfix releases, and updates in general will be limited to those fixing

Re: [Bug 270124] Re: knetworkmanager connects to untrusted networks

2008-11-14 Thread Francisco Borges
On Thu, Nov 13, 2008 at 10:43 PM, Henning Moll [EMAIL PROTECTED] wrote: *** This bug is a duplicate of bug 210459 *** https://bugs.launchpad.net/bugs/210459 I am not sure wheather this is really a duplicate of #210459 First of all, it affects two different applications: nm and

[Bug 270124] Re: knetworkmanager connects to untrusted networks

2008-11-14 Thread Francisco Borges
** This bug is no longer a duplicate of bug 210459 NM should not connect automaticly to unsecured network which was formerly a secure one -- knetworkmanager connects to untrusted networks https://bugs.launchpad.net/bugs/270124 You received this bug notification because you are a member of

[Bug 270124] Re: knetworkmanager connects to untrusted networks

2008-11-13 Thread Henning Moll
*** This bug is a duplicate of bug 210459 *** https://bugs.launchpad.net/bugs/210459 I am not sure wheather this is really a duplicate of #210459 First of all, it affects two different applications: nm and knetworkmanager. Secondly: 270124 describes the connection to a untrusted network,

[Bug 270124] Re: knetworkmanager connects to untrusted networks

2008-11-12 Thread Francisco Borges
*** This bug is a duplicate of bug 210459 *** https://bugs.launchpad.net/bugs/210459 Can't really comment if this still occurs on Intrepid. But on hardy it certainly did. However this seems to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/210459 In which NM

[Bug 270124] Re: knetworkmanager connects to untrusted networks

2008-11-07 Thread Magnus S
Hi, is this bug still affecting you? If so, could you please attach the output from the following commands? * Reproduce the bug, and then run cat /var/log/syslog complete- syslog-270124 in a terminal. There should now be a file called complete-syslog-270124 in your home folder. Please attach