plasma-widget-network-manager: can't create System Connections

So it looks like this bug was triaged a long time ago. It's still present in Lucid. Has there been any progress? This really should be fixed in time for Lucid. You need to stop treating KDE users as second class citizens.

I'm running Kubuntu 10.04 LTS Beta 2. Seriously... every install I've done since Jaunty has taken me literally HOURS to get network connectivity to behave - first because my wired network is configured in /etc/network/interfaces as "manual" so KNetworkManager can't see it, and then because wireless won't connect to my AP (128-bit WEP, shared key, using a string instead of hex), and last because I don't know how the heck to get it so that I have a network connection before anyone's logged in!

Eventually I remember to edit /etc/network/interfaces, and then eventually I remember that I need to enter the WEP key in hex (even though it claims string will work)... but I've never found a solution for this one.

Think of it like this: *ubuntu has become kinda synonymous with "desktop Linux" these days. Stuff like networking being broken "out of the box" is part of why people keep talking like "wait, no, *this* is the year of the Linux desktop...!" Until a clean install Just Works(tm) for the vast majority of people, it ain't that year yet.

(All that said, this is IMHO one of the only things left preventing that...)

...and now even entering the hex key doesn't work. :-S

Why hasn't this been fixed and why is the importance just wishlist? This is important functionality that is available on Gnome. Stop treating your KDE users so poorly.

IIRC it isn't implemented upstream, so if it is not a priority somehow for
the Ubuntu developers (which may or not be related to this piece of
software), there's so much they can do to solve this bug, but to wait that
upstream implements the feature and that the change is somehow easy to
backport.

We all want this feature (and that knetworkmanager becomes more
stable/robust), but I guess we'll have to wait for the developers to
implement the possibility to add network connections as system connections.

This error still occurs in Ubuntu 10.10 (Maverick Meerkat) Beta.

This issue is nearly a year old and still unresolved? This is vital functionality that exists in Gnome. Let's go!

This error is also in Ubuntu 11.04 Natty. Does it affect another distros? or is only something ubuntu specific? I can't believe the KDE guys have this kind of problems.

As usual, the developers are completely missing the point. If they don't want to consider fixing this BUG a priority, then they should get rid of the box that implies that we CAN make it a "System Connection".

If an item is in the UI and cannot be enabled, it's a bug, and imo a serious bug because it makes the program look amateurish.