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 securit
@mincer
thanks for your suggestion, I deleted all the references to ath0 (my
wireless device) from /etc/network/interfaces and when I restarted it
turned out that knetworkmanager was running fine and showing the wifi
networks again.
--
doesn't show wireless networks anymore
https://bugs.launchpa
I think that the rogue line is added to the interfaces file if you use
the Manual Configuration option that Network Manager presents (more
specifically the window that opens when you hit "Configure Interface" in
the Manual Configuration application, and which lets you directly
specify an ESSID to c
My problem went away after I edited /etc/network/interfaces as
https://answers.launchpad.net/ubuntu/+source/knetworkmanager/+question/5327
specifies. (I commented out the lines pertaining to the WLAN interface,
leaving the rest alone.) Still, I don't know why it got changed.
--
doesn't show wirel
I think I have the same problem on Kubuntu Gutsy. My package versions:
network-manager 0.6.5-0ubuntu16.7.10.0
network-manager-kde 1:0.2ubuntu1-0ubuntu5
network-manager-gnome 0.6.5-0ubuntu10
Neither nm-applet nor knetworkmanager do list any wireless networks.
KNetworkManager doesn't even say
I have the same problem!
Knetworkmanager cant show me the Wifi network list anymore.
Before the last release, it can't connect me to a wifi network with WEP key,
but just the open Wifi networks.
But the last release (0.1-0ubuntu11) has a regression,I think
--
doesn't show wireless networks anym
I can confirm this on my MSI MegaBook S262 with ipw3945. Upon initial
setup of knetworkmanager, it does not detect my home wireless network
signal immediately (which, although I have configured to not currently
broadcast its SSID, should have been detected by knetworkmanager anyway
as a network);
