Linuxguy123 wrote: > On Tue, 2009-02-10 at 20:38 -0800, Gerald B. Cox wrote: >> I apologize upfront if I missed something but - I noticed since >> applying the 4.2 updates from the test repository that knetworkmanager >> no longer works for me to connect to wireless. Wired networks appear >> to work fine. The only way I've seen to get around this is to install >> NetworkManager-gnome. When this is installed knetworkmanager works >> fine (but isn't really needed since NetworkManager-gnome is >> installed.... duh...). >> >> I did some searching and found: >> http://www.osnews.com/story/20758/KDE_4_2_Progress_New_NetworkManager_Plasmoid_Coming >> >> which looks like the old knetworkmanager is on the way out (or with >> 4.2 appears already gone... ;-) ) >> >> The new plasmoid isn't going to be distributed until 4.3 but >> apparently is available to test with now. >> >> What's the current direction on this? Use NetworkManager-gnome until >> 4.3, make the plasmoid available to use or fix the old >> knetworkmanager? > > This find makes me mad. > > Where does KDE get off breaking stuff that works ? Please re-read the thread. *KDE* didn't break anything, a NetworkManager update induced this. That said, knetworkmanager has always been fragile, with... let's say a less-than-responsive upstream. -- Rex
