Hi,
I am using KDE 3.5.10 on Yoper Linux. First off, the system tray icon would change to show my connection type (it would change from a dim globe to a signal bar if wireless, or some kind of spoon or fork or something for ethernet). Now, it just change from a dim globe to a glowing globe upon connection.

Next problem is, when I right click the icon, the menu doesn't work the way it should. When I right click to view the menu, there's no wireless submenu; in addition, none of the wireless networks that I have setup in KNetworkManager show up on the menu when they are available. Also, the New Connection item does not work, forcing me to use the Edit Connections item whenever I need to setup a new network.

If anyone can help, I'd much appreciate it. Thank in advance.

Have you recently upgraded or changed the configuration of your system?

Normally a glowing ( green ) icon normally means that your system has already connected itself to a network, independant of Network Manager.

I haven't upgraded anything related to KDE recently (except for cmake, but I always thought that was used to compile KDE 4, but not to use KDE 3 or 4?).

I don't keep the Ethernet cable connected, so even at boot when it's starting the network service, there's no way for it to determine an IP address because there's no Ethernet there and no wireless network being specified at boot. The only other thing (network related) besides the network service starting is NetworkManager being loaded. And I had always thought that, when I used KNetworkManager to connect to a network (whether it be Ethernet or wireless), it always used NetworkManager. However, since it's connecting to my network independently of NetworkManager, the only other possibility is that I am launching a terminal, su ing to root, and connecting via iwconfig and dhclient, or using a startup script to connect to my network. But this is not the case. This system is for a friend who knows very little about Linux, so I'd like to make things as easy to do without a command line as possible until he feels comfortable enough in Linux to use one. Also, he might decide to change the default ESSID on the router I'm giving him, so a startup script is impractical since I don't yet know enough about scripting to specify multiple possibilities in a startup script.

It apparently always used NetworkManager until the other day because it never used the glowing globe.

Oh, and also, the only configuration that I've changed are the Appearance & Themes settings in the Control Settings, and I doubt that would have anything to do with it.

As root, I did a userdel on my main user, then did a rm -rf on his home directory, then did a rm -rf /tmp/* and recreated the user, and this problem fixed itself. I don't know how, but it works.