There is not a single day without a bug report.There is not a single week without hundreds of bug reports.Some helpfull links:>Get Involved/Issue Reporting:https://community.kde.org/Get_Involved/Issue_Reporting>Search/Fill for bugs:https://bugs.kde.org/index.cgi>Crash handler for KDE software, Dr. Konqi:https://github.com/KDE/drkonqi
ok but i cant into gnome and gtk3 des have no thumbnails in file picker no i will not tinker to get them working when i can just use kde
Bugs reported in the last 24h:
Bugs reported in the last week (300+):https://bugs.kde.org/buglist.cgi?chfield=%5BBug%20creation%5D&chfieldfrom=7d&f1=product&o1=notequals&v1=Spam
Better to have bugs than something where working isn't considered a metric.
>>107553415I reported a bug four weeks ago, then I submitted a merge request (MR) a week later, but nobody has replied to me yet.
I love KDE for being modern and flashy, but it’s buggy as hellPlasmashell try not to crash for the 15th time today challenge (IMPOSSIBLE)
>>107554769KDE only seems to krash for me when I fuck with the panels and desktop plasmoids. Or when Brave gets a bad update.
>>107553415No use case for bug reports.
>>107554769I occasionally receive a notification in the system tray saying "Application X has crashed. Do you want to submit a bug report?" or something like that. I'm not sure if it's KDE's fault but this also happens with some flatpaks. Their crash obssession needs to stop.>>107555691This too, but some months ago it crashed on the lockscreen, got me scared for a moment.
>>107553431lxqt and trinity exist
>>107553415bug reports would be good if they were actually solvedbut I test kde every 3-4 years and it's always a buggy, glitchy and crashy mess, which tells me that the bug reports gets ignored
>>107553436Mom I got in TV!
>>107553835Welcome to open source.>"if u have a problem fix it urself chud :)))">okay *fixes problem*>*MR languishes for the next 3 years, eventually the fix becomes irrelevant or is closed as WONTFIX*
How do kde users manage their dotfiles? I find that a lot of kde config files keep not just configuration but also state, so they keep changing all the time, and may contain stuff I don't want to have on github. Similarly, sometimes the *current* defaults of a certain setting are stored there, when I don't want them to - if I've not changed the setting, I want the setting to be able to change with future changes to the defaults.Right now I keep a few handcrafted kde dotfiles that I copy manually into the user's config dir, where kde can clobber them to its will. Managing this is a pain, however, so I'd love to know what other people do.Do people use a script with kwriteconfig6? That'd be more like my windows settings script, which is somewhat manageable but hard to make sure I've not forgotten to record some setting I changed. Does home-manager help with this?
>>107553415my dwm never crashed and it never really had any issues. It just works, same for i3 and xfce4. Why do people use kde?
>>107553415The only good thing about KDE is its fuckable mascot. That's all.
>>107553415*taps sign*
>>107553436That is literally me
Wayland has the most crashes I never had this many issues before Wayland
>>107553835what was your bug? maybe they have fixed it and forget to merge, search for it on the search/fill category.>>107557009if that was true kde would be unusable, most reported bugs get fixed, but more bugs appear. its an ongoing war against crashes and bugs, if windows accepted bug reports, how bad do you think it'd be?
>>107558119>most reported bugs get fixedlmao this is ludicrously untrue. have you ever filed a single bug report for KDE? most get automatically closed due to inactivity.
>>107558464no i havent, but theres no way they arent fixing them right? theres a lot of dev activity in discuss and the bug tracker.
>>107558662>but theres no way they arent fixing them right?nta butlollmaojust look up "KDE year old bug" and you'll find>8 year old bug finally fixed>15 year old bug finally fixed>4 year old bug finally fixed>9 year old bug finally fixedhell I just saw one that was 18 years old
>>107559105>there's no way they aren't fixing them>literally lists a bunch of bugfixeslmao what a brainlet
>>107559200>t-they're fixing it, see? l-l-like this one from... 18 years ago!!
>>107559224>they aren't real bugfixes because... they just aren't ok!!
>>107553415>SAAARSSS
Works on my machine.
>>107559271>>107559224take cirno virginity, loud mating press, big overflowing deep nkdshis, impregnate, keep mating pressing and nkdashing
>>107559391I wish the plasmoids were less buggy and inflexible but eh, I'll just not use them. The rest of KDE just works in my experience.
>>107559271got him good >>107559391wayland's fault
>>107559907It's a rhetorical win. His actual point that he failed to assert is that KDE bugfixes are slow. That's probably true but the problem is developer numbers/incentive vs user population. Idk, works for me.
>>107559271fuck she's smug as hell
>>107559907if your shit doesn't work on Wayland? why ship it? are they Microsoft.
KDE seems to just work on my machine. There are crash reports logged, but I've never actually seen a crash, and there has never been any problem with functionality. I'm genuinely confused. What are you guys doing when you have problems with it?
>>107561210Sometimes it gets confused when I move plasmoids between the desktop and a panel, or when I adjust panel settings, or when I switch between configuring a plasmoid app and going to the "Edit desktop" screen. Especially third-party plasmoids are prone to krashing.The "Edit desktop" screen is a dumpster fire of shit that shifts around and behaves unpredictably. Burn it to the ground and rewrite the fucking thing. Do some actual goddamn UI research. Keep it fucking simple.
>>107561210>There are crash reports logged, but I've never actually seen a crashPlasma krashes so much it has a sophisticated seamless krash recovery system. And you don't think this is a problem? NIGGER!!!!!!!!!
>>107561210well if you use as it is, youll be alright, but from the moment you start exploring its customizability and features youll come across many sharp edges, said crashes and what not.
>>107558119>what was your bug?https://bugs.kde.org/show_bug.cgi?id=512321
>>107561210Going into edit mode for the panels and dragging around stuff used to be a consistent way to get kwin to crash.
We need to genocide the entire KDE and GNOME dev teams so that XFCE becomes the Ubermensch's desktop environment of choice. It's the final solution to the desktop war menace.
>>107561934
>>107561934>the final solution is to go back to 2003grim
>the final solution is to go back to 2003
>>107553415BOIINNGGGGGGGGGGG
>>107562628dude 2003 was unironically peak tech>Apple wasn't spooky>Microsoft still made good shit>people weren't as terminally online brained>surveillance tech hadn't advanced to the point continuous surveillance>lenovo still made good thinkpads>javascript was still young>php was king
>>107562738You didn't even need to write all that, everyone with a functioning brain can see he got self-owned on that one.
>You didn't even need to write all that, everyone with a functioning brain can see he got self-owned on that one.
*krashes*
Windows LTSC won, lmao