119
We are looking for a new set of Community KDE Goals to work on.
(cdn.masto.host)
We are looking for a new set of Community KDE Goals to work on.
What should KDE focus on over the next two years? Are you ready to share your vision, time and stamina to push KDE to the next level?
Let's evolve KDE together! Find out more here: https://blog.lydiapintscher.de/2024/06/05/what-should-kde-focus-on-for-the-next-2-years-you-can-propose-a-goal/
Make the plasmashell especially kwin stable, as its crashing a lot, and with wayland it's taking whole session down...
To the point I went back to Xorg
@kolorafa
I havent had any issues in the several months, outside of one really wierd one I had just not to long ago. https://bugs.kde.org/show_bug.cgi?id=486757
One craah in nearly 6 months I would consider excellent. Are you filing bug repports?
@kde
Whenever i get the Crash report window I fill it as much as possible and send, I stopped manually going into bugs.kde.org and manually create bug after the response I got was "it's probably nvidia issue", but for last months I'm on new AMD gpu and those issues still persist and I already learned to just periodically run
kwin_x11 --replace& disown; exitto fix them and go with my life.And yes, the issues is probably not easy to track, as it only happen after at least few days or running it.
Just recently the switch from plasma 5 to plasma 6 introduced another bug with the windows - every few hours/days i get a window that is visible but all mouse clicks go thru it and actually the window behind it receive those clicks, to fix it I (once again) do kwin replace.
And yes, I'm heavy user with 2 workspaces * 2 desktops * a lot of open apps/windows running 24h/day, to the point just few days ago I got and error in console "maximum number of clients reached" when on X11 when trying to open any new window... (And I didn't run out off RAM (48GB) or VRAM (16GB))
So as much as I'm full time on Linux desktop for 8 years, the experience did improve a lot, but the stability of long running KDE Plasma slowly degraded over last years, hence my response.
And I did have the same issues on my 8 year installation of Arch and on KDE Plasma.
I had only few crashes and only on plasma 6, yes I did switch to 6.0.1 which is very quite new, so few crashes could be expected, but I'm on 6.0.4 (will update to 6.0.5) and kwin is still buggy with window ordering, and compared to xorg, on wayland I can't do kwin_wayland --replace because it closes all my open windows/apps which is annoying. Heck, even killing/restarting plasmashell also shutdown all apps that was started from menu...
Why did I switch? Because of hoping that issues from 5.x was fixed in 6.x but that was not the case :(
Same that not many issues will crash whole kwin so they will never trigger "crash report". It would be nice to have some some way to easy "trigger" state dump and open issue. That I would like the 'stability' and those last 0.001% of stability polish to be the focus for KDE.
So as much as I love <3 KDE Plasma, and I yearly donate to KDE, I still can't with clear mind suggest anyone to switch from MS Win to Linux (KDE) especially now with Wayland that made me lose all my unsaved work 3 weeks ago due to kwin crash.