Søndag den 5. april 2009 19:49:40 skrev Oddball:
Knetworkmanager (kde3) is/was still default in kde4.2. But if one knows that somehow wpa settings do not get saved, so one has to configure these everytime one boots, one wants to try another version, like NetworkManager-kde4. Invoking it from the cmd as $, gives the location, and the hint to invoke it as #. Invoking it as root gives nothing. wpa_gui also is bugged as it states you have to use a minimum of eight symbols when you use 8, and will also not save anything...
I upgraded to 2.6.29.60 today to find that wifi is onboard again, so i end up with dead end streets again.
Is it usefull to file a bug against knetworkmanager, as it is gonna be dropped anyway?
I would like to be able to use my wireless without having to config it every startup..
Maybe you haven't enabled kwallet? .. knm3 remembered password and configuration fine for me. To switch to knm4 you can do this for example. 1) zypper in NetworkManager-kde4 2) zypper rm NetworkManager-kde 3) Add 'Network Management' plasma widget 4) reboot You probably shouldn't experiment with it, unless you have cabled network access nearby in case of problems. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org