11 Mar
2009
11 Mar
'09
1:18 p.m.
Another vote here for giving up on knetworkmanager - it doesn't work properly in 4.2
either, or not for me anyway, so I don't think there's much change of a working
backport to 3.5!
I use wicd for jumping on and off wireless networks, but that is flaky too. At least it
works, and if it doesn't you can see what command lines it tried to use which helps
you troubleshoot.
regards
Zack
-----Original Message-----
From: B. Buchli [mailto:bbuchli@gmail.com]
Sent: Wed 3/11/2009 13:11
To: kubuntu-kde3.5-users(a)pearsoncomputing.net
Subject: Re: [kubuntu-kde3.5-users] knetworkmanager problem
Stefan Endrullis wrote:
Hello KDE3.5 users,
I'm very happy about the KDE3 PPA of Tim Pearson. All my KDE
programs work, except the knetworkmanager.
Therefore I wanted to ask you if you know a good solution for
the knetworkmanager problem?
My current workaround is to use knetworkmanager in combination
with a shell script. First I tell knetworkmanager to connect to
a specific WLAN, then I start my shell which does the same. By
this procedure knetworkmanager recognizes the connection and
all KDE programs are cheerful.
Do you know an easier solution?
Regards,
Stefan
Knetworkmanager has been buggy for quite a while and only has caused me
troubles. My workaround is using nm-applet which works like a charm...
Hope that helps.
Ben