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
Daniel:
I am experiencing this problem on Kubuntu 8.10. I often need several
tries to connect to my WPA2-PSK connection. Sometimes I just give up on
trying to get the connnection established.
I believe there are similar reports at
https://bugs.launchpad.net/bugs/259278
and its duplicates.
--
Is this symptom still reproducible in 8.10?
** Changed in: knetworkmanager (Ubuntu)
Status: New = Incomplete
--
knetworkmanager frequently fails WPA connect
https://bugs.launchpad.net/bugs/137808
You received this bug notification because you are a member of Kubuntu
Bugs, which is
I may be wrong about that previous comment, because this time it would
not connect even after killing the autoipd daemon, after a power cycle
it worked.
--
knetworkmanager frequently fails WPA connect
https://bugs.launchpad.net/bugs/137808
You received this bug notification because you are a
Does having a network widget (kweather) in the taskbar active on start
before the wi-fi is up cause problems?
--
knetworkmanager frequently fails WPA connect
https://bugs.launchpad.net/bugs/137808
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I'd also like to know where the 169... IP is coming from as a default.
** Attachment added: Output of daemon.log
http://launchpadlibrarian.net/9154911/daemon.log
--
knetworkmanager frequently fails WPA connect
https://bugs.launchpad.net/bugs/137808
You received this bug notification because
This may be the same as bug #119818, as what you see is knetworkmanager
stalling out at 57% (I think the DHCP step) and WEP seems to work fine
all the time. I think there is some state/permissions conflict
somewhere. Booting into XP and the connection works 100% of the time
(using the same router,
If I kill avahi-autoipd, then it will connect. For whatever reason, the
zeroconf daemon is conflicting. This is also what is getting the bizarre
169 address (my router is the only wi-fi network around, and it will
only provide 192.168.0.20 to this mac address). I couldn't stop it via
