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/

#goals

@kde@lemmy.kde.social

Avatar
Bro666@lemmy.kde.socialM
15 points
*

A gentle hint: If you suggest anything, you must be willing to put in the time to champion the task and carry out to completion.

Also, do your suggesting here by following the instructions laid out in the blog post linked above.

If you don’t do that, nobody is going to take up anything you suggest here.

permalink
report
reply
0 points
Removed by mod
permalink
report
parent
reply

@kde@floss.social
I know ✋I know ✋ there is already a lengthy list:

https://bugs.kde.org/describecomponents.cgi

@kde@lemmy.kde.social

permalink
report
reply
5 points

Those are bugs. Not community-wide projects.

permalink
report
parent
reply

@Bro666
Those are bugs reports and feature requests for all KDE applications including plasma and also including Kate, Yakuake, Konsole, Kmail, rkward …

Not complaining here, but none of the bugs I ever reported or I’m following were addressed. To me this sounds like a good place to focus on, because these are issues that the community have faced or the suggestions they have come up with.

permalink
report
parent
reply
6 points

Bugs are solved all the time. It is not a project for the community because the community already works on correcting bugs all the time. If the correction of bugs is not fast enough for you, we cordially and officially invite you to help out:

https://community.kde.org/Get_Involved

Remember: bugs are corrected by volunteers, many of which also have day jobs and other things going on. We are always understaffed. You can help.

permalink
report
parent
reply
6 points
*

Unifying a few codebases, and make Plasma more modular.

1. A minimal Plasma

I think Plasma is the best desktop and suited for minimal installs on machines with like 2GB of RAM. Reducing the needed dependencies (currently working on that in Fedora) to the bare minimum. Making all the fancy desktop effects, animations, blur, transparency, floating, … optional.

And yes, please also remove the default plasmoids from the needed install. Maybe keep the ones default in the panel. Maybe add a way to find them as “official plasmoids” which would help a lot.

2. Merge parallel works

Gwenview, Spectacle, Kolourpaint, digiKam all have image editing bars. The one of spectacle is pretty good, Gwenview and digiKam could be merged, Kolourpaint could maybe get an additional few things specific to the app.

permalink
report
reply
5 points

I just want to know why my calculator is dependent on a webcomic reader…

permalink
report
parent
reply
4 points

True, the default plasmoids being critical dependencies is insane.

Please make these plasmoids optional.

There are some where other plasmoids use their code, like the weather applet. But apart from that, a comic reader??

permalink
report
parent
reply
7 points

Merge parallel works

Oh this is such a good idea. I think an approach analogous to ktexteditor (or the embedded konsole terminal in apps like dolphin and kile, too) would be amazing. Having the same editing expertise across Kate, kwrite, kile and other text editing apps is fantastic.

permalink
report
parent
reply
15 points

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

permalink
report
reply
7 points

Cannot reproduce at all on Fedora Kinoite. I havent had any crashes since a long time. None on Plasma 6 since the beta is over.

permalink
report
parent
reply
2 points

I’d second Kinoite, it has been rock solid and really does feel next gen. Especially nice that Universal Blue extends its capacity, being just one rebase away.

permalink
report
parent
reply
5 points

@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

permalink
report
parent
reply
3 points
*

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; exit to 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.

permalink
report
parent
reply
-3 points

Maybe if you have to ask the community for a goal, you have nothing worth doing left.

permalink
report
reply

KDE

!kde@lemmy.kde.social

Create post

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.

If it hasn’t, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

Community stats

  • 1.2K

    Monthly active users

  • 772

    Posts

  • 6.1K

    Comments