Hi there - this is just a quick question:
Is there a “new” network manager for KDE 4.2 that fits the great style of KDE 4.2?
The old one looks ugly compared to the rest of the style… ^^ Oh and I almost forgot: Where to get it?
Have a good week, guys!
TheMask.***
There is a plasma widget avaialable still in development AFAIK. it doesn’t yet provide all the features required for wireless connectivity yet. Some links for you:
KDE NetworkManager interface gets a shiny plasma overhaul - Ars Technica
network manager for kde 4.2 - openSUSE Forums
Looks like you’re better off staying with knetworkmanager front-end for now until KDE 4.3 is released.
I’ve been using the plasmoid for weeks now, and i must say i’m impressed. It can not only manage wired and wireless connections, works perfectly with all kinds of encryptions, but also provide VNC access. Looks good, feels good, runs great, connects whenever I want.
I posted this in another thread.
I had to downgrade to kde3 networkmanager to get connected. However, even that didn’t work for me at first. I use WPA encryption. I read that you needed kwallet to manage the password for that.
Each time it tried to connect, both kwallet and networkmanager would ask for the password. I supplied it to both and the connection always failed. After a reboot today, I ignored the request from networkmanager and supplied the password only to kwallet. The plasmoid connected at once.
I may get brave and try kde4 networkmanager and try this trick again.
http://media.arstechnica.com/journals/linux.media/screenshot2-1.png
This thingy looks… AWESOME. rotfl!
I’d really LOVE to try trhe latest version. Are there precomiled binaries or what do I need to do in order to install it?
TheMask.
Thats running without kde3networkmanager in the system tray?
No, it’s a plasmoid/widget. Install NetworkManager-kde4, right click on panel, add widget, select NetworkManagement and it’s on the panel.
I know full well how to get it, how to put it in the panel or the desktop.
I am asking of it works without kde3networmanager.
I don’t need two items that do the same thing, I like the look of the new widget and would use it if I didn’t have to run two just to get one to work.
Lookin all purdy is nice and all, but if it won’t yet function by itself then I don’t see why a reason to use it yet.
I will drop the kde3 version in a heart beat as soon as the new one is functioning the way it should.
[quote=“brucecadieux’s Avatar
brucecadieux”]
I will drop the kde3 version in a heart beat as soon as the new one is functioning the way it should.
[/quote]
WORD. 
Sadly this awesome thingy is not yt fully completet and probably won´t until KDE 4.3.
To answer you question above: Why don´t you try it and report back? ^^
TheMask.
Once the k4 network manager is working fully in 4.3 (?) will it do so without having to use kwallet?
Well… lemme look into my magic crystal ball. Umm… too bad, i don’t get a wireless signal right now… 
As a matter of fact, developers really code hard to get all known issues get solved up to the point when 4.3 will be released. Just keep tuned as this app will push OpenSuse bigtime (once more).
As for me - I’m gonna install it NOW and hold it up to date. heheh… see ya, guys!
TheMask.
TESTED.
As I said before: I am impressed by its looks, but certainly there is no rela functionality right now. After installing the widged, it keeps asking fo kwallet - which I don’t like as many people do too. sigh
Well, I’m gonna keep the widget and I’ll try it from time to time to see how the team makes progress.
Hope the dream becomes true some day…
TheMask.
I’m running the widget successfully on a laptop without the kde3networkmanager. There are some quirks, but you can overcome them.
First, I can’t get the widget to work on the desktop. It seems to only work in the panel. I don’t care if that doesn’t make sense, I’m not fighting it.
Unfortunately, I do need kwallet. I left click on the widget icon in the panel to open it. When I click on the icon for my wireless network, a box pops up asking for the password. I leave it blank and set to no encryption (it really is running WPA) and click ok. Then kwallet pops up. I have already saved the key in kwallet. I have to give it the kwallet password, usually twice, and the wireless connects and the widget looks just like the example above.
Should be simpler, but at least it works.
You have to type a kwallet password two times?
I hate kwallet and don’t use it, I hope they don’t make this thing depend on kwallet.
Yeah. I wondering if its because I’m slow and don’t enter it before it gets called again. It usually is behind another window and I don’t notice it right away. Its a small annoyance, but it got me online.
I have sometimes had 4 or 5 kwallet windows one on top of the other. The whole kwallet need is a crock, k3 network manager did without it. I’m afraid that if the finished product does rely on wallet then i’ll be looking for something else.
About wallets: if you mix kde4 and kde3 apps, both wallet-versions will start.
And…dear people, kWallet asks you if you want it to do what it’s meant for. After that it asks you if you want to allow an app to access it. AFAIK you only get where you have gotten, if you answer Yes, Always to questions asked.
Now, to get rid of this behaviour (MIND that all stored passwords are gone afterwards:
rm ~/.kde/share/config/kwalletrc
rm -rf ~/.kde/share/apps/kwallet/
rm ~/.kde4/share/config/kwalletrc
rm -rf ~/.kde4/share/apps/kwallet/
The first time you start an app that uses passwords, kwallet will start. Tell it you don’t want to use it, and you’ll never see it again.
I always tell kwallet to go away I don’t want to use it.
That being done, kde4-network widget refuses to connect to my secured wireless lan, unless kde3-networkmanager is running in the background.
However just for the sake of trying it all over again, I will delete the kwallet junk as you suggest and try again.
Nope, it doesn’t work unless you use kwallet or have the kde3-networkmanager running.
So just to try it out, I tried it with kwallet, it works, but has the ill effect of killing system sounds.
The sound card works in applications but the infamous notification that sound device failed falling back to…
So it’s still a no go for me. I uninstalled it, and stick with the old networkmanager for now.
I do hope they throw the dependency of kwallet very, very far away, I find kwallet to be annoying, and one of those things that should never be a “requirement” for an application to run.
My experience is the same as the above either kwallet or k3 applet running the background.