KDE Rolling Out New CLI Tools, Many Crash Fixes

[phoronix]

Phoronix: KDE Rolling Out New CLI Tools, Many Crash Fixes

KDE developers have been wrapping up February with a number of new command line tools being worked on for applying various cosmetic changes to the desktop. There have also been many crash fixes addressed in recent days...

http://www.phoronix.com/scan.php?pag...-New-CLI-Tools

[angrypie]

Just like all roads lead to Rome, all codepaths lead to KDE crashing.

[tildearrow]

Just like all roads lead to Rome, all codepaths lead to KDE crashing.

You seem to be full of hate.

(Even though it is true KDE feels like a minefield at times)

[aufkrawall]

Afair the Wayland session hasn't crashed for me with 5.21 (or git-master) so far, while plasmashell is still quite crashy.

[nist]

The latest releases of Plasma seem lighter on resources, also KWin. But KWin isn't neutral yet, compared to other WMs. For what reasons every input activity (I suppose and/or other reasons) should pass throu KWin?

[Charlie68]

Just like all roads lead to Rome, all codepaths lead to KDE crashing.

It may sound strange to you, but I have been using Plasma 5.21 since beta and have never crashed in the Xorg session. Indeed in this release I noticed that they have fixed some small bugs from the past. This does not mean that the bugs were not there, it just means that if you use Plasma without upsetting it, you will hardly run into serious bugs, but Plasma allows an avalanche of customizations and there you can find bugs especially as soon as the main version is released. It is humanly impossible to test every single sometimes imaginative customization that users make.
So what's the solution? The Gnome dictatorship that doesn't allow even the most mundane things? Sure that's easy to maintain, but then look at the extensions and their bugs. As for Wayland, it's still an experimental session.

[Guest]

The latest releases of Plasma seem lighter on resources, also KWin. But KWin isn't neutral yet, compared to other WMs. For what reasons every input activity (I suppose and/or other reasons) should pass throu KWin?

Because KWin is the compositor........in a Wayland session, it takes the place of X and all input and display events pass through it. It's the ultimate controller of your GUI.

[andreduartesp]

The latest releases of Plasma seem lighter on resources, also KWin. But KWin isn't neutral yet, compared to other WMs. For what reasons every input activity (I suppose and/or other reasons) should pass throu KWin?

On Wayland every input activity passes through the compositor, this is a security measure, Kwin is Plasma's compositor.

[bug77]

On Wayland every input activity passes through the compositor, this is a security measure, Kwin is Plasma's compositor.

Seems counterintuitive (to put it lightly). A compositor is a window manager, it has no business dealing with input. Or enforcing security. Its job is to present windows. I don't think the window managers in Windows or macOS need to deal with user input.

[aufkrawall]

Seems counterintuitive (to put it lightly). A compositor is a window manager, it has no business dealing with input. Or enforcing security. Its job is to present windows. I don't think the window managers in Windows or macOS need to deal with user input.

I don't notice any input blocking issues with Plasma Wayland.