So I get all excited this morning and install 4.3.0 as the RC were doing so well. However, after I install and reboot my wireless does not work. None of my stored networks connect. So I click on the system tray icon and all it says is "Manage Connections" the tool tip does not offer any help as all it says is unavailable.

The click event looks like this

I am using OpenSUSE 11.1 on an HP TX2000 Notebook Computer. If this question has been answered please point me to the right place. At least you can't say I didn't do a Google search. Thanks for any help.

I have the very same problem. I'm running openSUSE 11.1, KDE 4.3 and I have a Intel 3945ABG adapter.
The description of my problem seems to be the same except that when I click the tray icon, it also shows my ethernet connection.

A network scan shows that my card is working, and in fact it just worked yesterday under 4.2.4. All that has changed is the network manager update.

Could this be a kwallet thing since it doesn't even ask for the usual password in order to access WLAN? I tried to deactivate the kwallet's handling networkmanager, but I'm just not sure if networkmanager realized I did (or if it matters) since the behavior hasn't changed and nwm still won't show networks or a password prompt.

I'd be more than glad to have this fixed!

After updating KDE to 4.3 on my openSUSE 11.1 I have the same situation. The only way to connect to my WLAN is to use KDE 3 version of network manager. I tried to delete all wlan connections and create new ones, but with no success.

If I delete the network from the Network Manager configuration area, then set it up again and check the auto connect feature it will connect. However, the system tray icon still does not detect it but it will at least connect. I would like it to work the way it did before.

My adapter is a Broadcom but it does not seem to matter much since it is also happening with an Intel. I wonder if this is just an OpenSUSE thing then?

Open Network Management (Connection settings), go to the rightmost tab, and move all connection types under "Icon 1", that will fix the problem.

THANK you for the instructions. It works!

Now I'm just wondering in general: Why is this not default, and why is it just so unclear how to set it up? But I guess knetworkmanager isn't completely polished for KDE4 still. Or is it something openSUSE-specific?

The Network Management Plasmoid has been disabled by its developers ( wstephenson and sebas ) because it is severely broken and is causing Plasma to crash. You may wish to try running "knetworkmanager".

If it does not work, I would recommend using an alternate network manager. If you wish to continue using Network Manager, you can use the GNOME applet ( nm-applet ) or alternately you can use Wicd instead ( which I recommend )

Can someone please give me a definitive answer to this. Using KDE3 networkmanager it was possible to disable Kwallet, and NM still stored various settings for different networks and would connect either automagically or on a specific network being selected. In the KDE4 version it seems that the Kwallet requirement is hard wired into the programme, so no Kwallet - no networkmanager. I hate Kwallet and refuse to use it. So, is it the case that you must use Kwallet with NM for K4? If so, can the developers please allow users to disable this as per the K3 version.

KWallet is a hard requirement because in KDE 4 other backends will be available, so the details need to be stored in a backend agnostic fashion. Other backends could include ConnMan or Wicd ( which I prefer myself ).

You may wish to request this, but it may not happen as the data needs to be not stored in a NM specific fashion.

Any reason why you hate KWallet in particular?

Mainly because I cannot see the point of it. Pretty much the only programme I use which needs it is (now) networkmanager. It is intrusive and a layer of software which I do not need. I am the only user of my laptop, when I turn it on it connects automatically to the network I have previously chosen, or, if I am elsewhere, to the network I choose. I do not need another layer of security, or another pop up badgering me to input another password.
Very Microsoft.
If I needed it then I would run it, I do not so I have disabled it. If the networkmanager in k3 did a good job without Kwallet, why can the 4 version not be as good. This should definitely be an option, not a requirement. To force the use of Kwallet on users (and I appreciate it is not just networkmanager, I understand that Kopete is the same though I do not use that programme) shows an arrogance, a poor understanding of users wishes or, just bad planning. I am not alone in this I am a member of many forums and this point comes up time and time again. I do (now) use WICD, but it has limitations, which do not concern me at present but, should my needs change, I will need to connect to networks which wicd (as I understand it) does not cover. I do not really think Connman is viable as it is a) a gnome programme and, b) has the same shortcomings as Wicd.
I reluctantly went over to K4 but have come to like it, certainly having just installed 4.3, but I have an uneasy, underlying feeling that more and more programmes are being forced upon us which, supposedly, run in the background, but in truth are an annoyance, suck up resources and are not needed, or wanted by many users, Nepomuk being another case in point. It is a sign of increased bloat in the system. It is a small effort to input another password into Kwallet to get networkmanger to work, but the point is not the time it takes but that my ability to set up the laptop the way I want it rather than how a developer thinks I want it is removed just that little bit more. All these things should be options not necessities. And, it has just occurred to me that WICD connects automagically, as per the KDE3 applet, under k4 so why can networkmanager not do the same. [Rant mode Off] Thank you for your reply.

einar wrote:Open Network Management (Connection settings), go to the rightmost tab, and move all connection types under "Icon 1", that will fix the problem.

Wait,where?



I can't use KnetworkManager, Wireless connections shows up but they can't be clicked.

As you can see in the screenshot I'm using nm-applet ATM.

It's disgusting that I have to do "killall knetworkmanager; nm-applet" on each reboot (I don't want to have that in autostart, I would prefer the native tool to work please

Hi,

I use revision 1001913 for knetworkmanager (monolithic) and it's work very well for me.

to use it:

Code: Select all

svn checkout svn://websvn.kde.org:443/home/kde/trunk/playground/base/plasma/
cd plasma/applets/networkmanager
svn up -r 1001913
cd ../..
mkdir build && cd build
cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` ../
cd applets/networkmanager
make
make install # perhaps sudo or su before


and run it

Code: Select all

knetworkmanager


network-manager-plasmoid working fine here

detect networks and connect using the plasmoid.

This new network manager is truly useless. I spent the better part of yesterday trying to get it to work, even setting up the wretched Kwallet to a null password to try and get it to work invisibly, but for all that NM still refused to connect to anything, much like the problems detailed in this thread. I deleted all of NM files I could, turned off Kwallet, and went back to WICD. I have resolved to not use Knetworkmanager until: it is fixed, or at least works a bit and, not to use ANY programme at all that requires Kwallet. What is really annoying is that under KDE3, or using the KDE3 widget under KDE4 it did absolutely everything I wanted of it. The KDE4 version is about as much good as a chocolate teapot. I think WICD should be upgraded to be THE net work manager for KDE, and developed as such.
Funnily enough, having written the last bit I see that Enlightenment have done just that and defaulted to WICD.

The choice of Network Manager is not under KDE's control, and unfortunately distributions seem to have the idea the Network Manager is an extremely good thing to use.

Part of the problem is that Network Manager's maintainers do not maintain any form of KDE frontend, while they maintain the GNOME frontend. As a result any problems it has, or any new features in Network Manager itself are fixed / added immediately. As a result the KDE frontend is always playing catchup.

I also find Wicd to be a far higher quality, no fuss, network manager. It is 100% reliable in my experience. Intel seem to agree that Network Manager has problems also, and are writing ConnMan.