New KDE Plasma NM Sees Its First Release

[Teho]

Fixed.

It's almost amusing how hard it's for you to accept being wrong.

Gnome is the only code and UX worth forking.

...or maybe it's the only one that's so inflexible that it's necessary? ...or it has so hostile community that people can't deal with it?

And as you probably have realized the forks are going nowhere, people get smarter.

According to who? Cinnamon seems to be doing fine. Just for your information, the fact that you equate people with same preferences as yours as being smart tells quite a bit about your lack of intelligence.

Maybe KDE could have been stupid enough to accept being a Canonical CLA project? Just like KDE loooves its CLAed tool kit.

I like how it always comes down to the CLA when you run out of arguments. It's too hard for you to accept that Qt is more actively developed toolkit than glib/GTK+? You can't stand the fact that Ubuntu is much more popular than Gnome?

[Vim_User]

Riiiight. Martin makes a living from blogging, just like the 1000 teenagers. Nobody cares about kwin, it is a stale, old mess. Im happy for the blog-go-hacker that he can make a living from live-blogging as he pulls the worst crap out kwin. But at the end of the day nobody cares about kwin.

This guy works full-time on software used by millions of users. When can we see your contributions to the open source community, especially one that is as much successful as KWin?

[Teho]

Martin makes a living from blogging, just like the 1000 teenagers.

Just how fucking clueless can you be? Martin works for Blue Systems as a full time developer working on KWin.

A much much better UX.

So good in fact that it spawned two forks, one for Gnome 2 (Mate) and other for Gnome Shell (Cinnamon) and an additional Classic Mode because the default interface is not something you could put in an enterprise distribution... At the same time Ubuntu abandoned the Gnome as default shell. Spectacular job indeed. That being said, I have nothing against it, it's just not something I would ever use.

[Awesomeness]

Plasma-NM is great. Installed it last night.
The Connection Editor is a bit unpolished (something to be expected in the first pre-1.0 release) but overall I find it better than the old applet.

[Awesomeness]

Dear KDE developers

This is not a KDE feedback forum.

KDE 4 was released five years ago and the original NetworkManager applet is so broken that I always just disabled it and used the GNOME nm-applet instead.

This can't be true. The original release did not contain any NetworkManager applet at all.

Instead of just fixing the old stuff now we have a reimplementation atop of bleeding-edge technology and it just looks even more horrible than the old applet.

It's just a new UI on top of the existing libraries.

they reimplemented the Task Manager applet (I have NO idea why this was even necessary)

Non-QML UIs are deprecated in Qt5, that's why.

yesterday I got so fed up that I took the time to ditch KDE for XFCE on all my machines.

What are you doing here then?
Be happy with your new DE and take some time to learn how Xfce is spelled.

[Awesomeness]

To the people who don't believe that the "current" kde networkmanager applet is broken: Add a bluetooth tethering connection to the networkmanger. Open the knetwormanager administration/settings. Notice the tab "mobile broadband". It has a nice button "add connection" where you can add a cdma or gsm connection. Now remove the tethering connection. Now the "mobile broadband" tab is disabled and you have no way of reaching the "add connection" button anymore and your only chance is to add the bluetooth tethering profile with bluedevil.

Sounds like a good bug report. I hope you filed it.

[ChrisXY]

Ignore him, he trolls-- a lot. Bluetooth is working just fine here on Fedora 19

It seems that in upstream bluez4 has been broken for a long time. Patches have been known since over a year. On Archlinux I still had to apply these patches https://bugs.archlinux.org/task/35695 to get tethering working. Only works when adding the profile with bluedevil to networkmanager and then connecting with the "current" kde networkmanager applet. The gnome control center bluetooth thing has a button to connect, but the button is disabled. On blueman I get a timeout when trying to connect.

Does nobody find it sad that on desktop linux bluetooth tethering has been broken for a few years now and nobody cares? No really, install a default ubuntu 12.04 LTS, get a standard android smartphone and try if you can even pair it. Last time I tried it both the default ubuntu bluetooth thingy and blueman failed...

Your best bet is really, on the command line, pairing with hcitool, then sudo pand -n --role PANU -persist 30 -c bluetooth-id; sudo ifconfig bnep0 up; sudo dhcpcd bnep0
Just in case someone needs it.

To the people who don't believe that the "current" kde networkmanager applet is broken: Add a bluetooth tethering connection to the networkmanger. Open the knetwormanager administration/settings. Notice the tab "mobile broadband". It has a nice button "add connection" where you can add a cdma or gsm connection. Now remove the tethering connection. Now the "mobile broadband" tab is disabled and you have no way of reaching the "add connection" button anymore and your only chance is to add the bluetooth tethering profile with bluedevil.

[Ericg]

I hope this don't applys to Bluez5

Ignore him, he trolls-- a lot. Bluetooth is working just fine here on Fedora 19, Fedora 20 implements bluez5 (which ill be install the fedora 20 alpha test candidate tonight so ill report back on that)

[Ericg]

KDE's bigger brother

KDE existed first. You're a really BAD fanboy when you can't even get history right

Say thanks to Gnome just like you need to say thanks for doing Wayland first.

Gnome had a head start, but Martin's been doing more SERIOUS and more low level work in Kwin for YEARS, long before Gnome started to get serious about porting over. You can think him for being the testbed for porting from Xlib to XCB, as well as replacing X-dependent work with X-independent code in window managers.

[Ericg]

For KDE 4.11 they reimplemented the Task Manager applet (I have NO idea why this was even necessary)

Because its part of the push to QML / Qt5 / KF5? The entire thing is being ported over to QML for efficient usage of resources. It also had the added side effect of fixing one bug that no one could figure out related to overlapping items.