in the kde center, they have a module for setting network… it work fine when i connect my laptop with a wire…
when i use the wireless, it alway say my wlan is disconnected
i added the plasma widget for the network…
i checked in the kde service, user setting service for networkmanager is not started…
to get it to work, i need to start knetworkmanager (kde 3.x)… after the plasma widget said my wlan is connected… also in the service section the user setting service for networkmanager is started…
so i don’t understand when i need an old application to get network under kde 4…
Because it’s not yet finished. In fact most of the backend is maybe beta quality, since they delayed it from shipping with KDE 4.2/Opensuse 11.1. The frontend is even worse (plasma app) at a very early alpha quality. In summary it’s not ready for use yet. I know wireless doesn’t work, and wired connections are jumpy. The official plan is to have an “official version” ready later this spring for those distro’s that are launching then, and include the final and finished product in KDE 4.3.
don’t use this plasma, because you can’t connect to a WEP/WPA secured network and you can’t turn it off.
The only way to get rid of it is to delete it in Yast.
My laptop had some kind of blended kde. I had lots of 4.2 files and lots of 4.1.3 mixed in. I tried doing zypper up with the new repos but that didn’t work. I tried filtering on the factory repos to get to 4.2 but that only partially worked. Next I went back to zypper did a zypper up and finally a zypper dup. That last brought in a lot of stuff I didn’t expect since I thought I was already fully 11.1.
The reason I did this was a problem with the panel. Icons were stacking and I couldn’t unstack them. I thought the upgrade to 4.2 would fix that. But what happened was it killed NetworkManager. I couldn’t get it to start even though zypper said it was installed. Neither the menu or the terminal would start it. So, I searched for the plasmoid and got it installed.
As mentioned earlier, it won’t connect to WPA. Actually, it won’t stay connected. It kept asking for my password and throwing kwallet at me. I hate kwallet, so after it come up about 15 times, I told it not to come up. But, nothing I could do would make the plasmoid keep the password and after about 5 seconds, it would disconnect, reconnect and ask for a password but not take it.
At this point I gave up on the password and tried to use kwallet. Now, kwallet won’t start at all! Not from the menu or from terminal… just like the issue that started this whole fiasco. Am I doomed to ifup?
The new plasmoid networkmanager-kde4 has been working perfectly for me for almost 3 weeks now. It could be due to the fact that I’m running kde4.2 from the factory repositories.
Under what conditions is it working for you? People have had it working with unencrypted Wifi for a while now, it’s just some of the other possibilities - say static IP wired connections or WPA2-secured wifi connections that have been problematic.
If its progressed enough for those other situations I’d like to move to it permanently just to keep on top of the KDE3->KDE4 transition.
I just upgraded from the KDE3 version to the KDE4 version today (I’m using KDE 4.2 on OpenSuse 11). For the most part, it works well, I just have a few issues that maybe someone could help me with?
1). I can’t get the plasmoid to show on the desktop, but if I add it to the system tray, it works fine.
2). The vpnc plugin doesn’t work for me at all. When I try to configure a new VPN connection, I can enter in the gateway and the group name, but I can’t change anything in “optional information” (checking any box leaves the input field greyed out). Also, entering anything in the first tab, then saving, then re-opening — everything is blank again. Work-around is just to use vpnc from the command line.
3). I have a mobile broadband card, inserting it doesn’t seem to do anything with networkmanager (the mobile broadband tab is greyed out).
Will keep working through all of this, but in the meantime, does anyone have any ideas (and are the above working for you … if so, how)?
Has anyone been able to get this working for non-DHCP wired connections? I can create the connection easily enough, but when I click the plasmoid and select it I get a message that it’s connecting but my connection never changes to it from the DHCP provided info.
kde4-networkmanager is working fine. To everybody in this thread: if you are in a “kind of mixed” KDE, take care of that first. Most of your problems are caused by uncontrolled updating and upgrading. You cannot complain about anything if you remove the ground it’s built on. openSUSE is completely clear about this: packages from the Factory repos are not to be considered as stable. Yet we hear from them, and got to have them. File bugreports, that’s improving by interacting.
Hence why this is a beta forum. But when people want to rid themselves of KDE3 and the one thing stopping it is network manager. And it seems to make huge jumps towards completions, instead of simple day to day growth. But since it is not going to be released until 4.3, most distro’s are asking that we push for some sort of completion in time for spring releases.
I was going to start a separate thread on this but I’ll just add my comments.
I had been running Suse 11.0 with KDE4.2 Factory Repos. Seemed like every day I had 500 mb upgrades.
So I installed Suse 11.1 with KDE4.1.3 and did not enable the factory repos. The ride is much less bumpy, but much of KDE4.1.3 is still dependent upon KDE3 - ESPECIALLY knetwork manager.
I have the old knetwork applet in my systray and the network plasma widget in the bottom panel. They seem to co-exist and work fine. However, connections have to be setup with KDE3 network manager. Also, I just did an update (not too long, 50 mb or so) and when I rebooted I have 5 instances of the network plasma widget in my bottom panel. All showed the plug though KDE3 network manager in systray connected me to my wireless without a problem. (except it doesn’t connect automatically on login)
So I deleted the network plasma widget and then restarted. Again, there were 5 instances of the plasma widget running. I turned them all off and then added the widget back to the panel. It now shows the wireless connection instead of just the plug. (which I assume switches back and forth depending upon whether you are using ethernet or wireless.)
Anyway, this is definitely buggy stuff, but I don’t have factory repos installed/enabled so I’m a bit surprised at the number of bugs. In a stable release it would seem to me they would hold off on something this buggy.
Stable = Suse 11.1 with KDE4.1.3
Unstable = Suse 11.1 with KDE4.2 (beta) using factory repos.
How did this slip through?
Is there a workaround so I don’t get multiple incidences of the widget every time I restart?
11.1 with 4.2. I’m using the k3 applet with 4.2 and it works fine. I tried the k4 plasmoid thingo and finished up with a connection but with multiple instances on the desktop and an inability to control connections. I’ll stick to the k3 version until 4.3 when the network manager is supposed to be fixed. Really it the only thing stopping me from getting rid of k3 completely.
