47
This Week in Plasma: Fixing All the Bugs, PiP, and Performance
(blogs.kde.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Oct 2026
47 points (100.0% liked)
Linux
19959 readers
70 users here now
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
founded 3 years ago
MODERATORS
When was the last time you ran https://memtest.org/ ? I’ve had several instances when what seemed like a buggy update was as a hardware issue that showed up because memory layouts changed.
Please don’t tell me this. These are literally not even a month old memory sticks 😭. I’ve just built this whole pc after a power surge fucked the old one up.
Ah yes, you swapped RAM sticks and now have RAM problems but the cause has to be vibecoded KDE…🙄
Brother. I swapped a whole fucking pc.
So it must be vibecoding! New components can't be faulty, drivers for new hardware can't be less mature,... No! It must be vibecoding at KDE!
I said “I hope”. Didn’t know you own KDE plasma.
You said you hope it's not because "they went hard on vibe-coding" which is an lunatic claim to make in the first place, just because some dude from KDE opened a discussion thread.
And you said that your broken ass PC with immature drivers will be the cause of you opening to many KDE bug reports that they'll hate you. That is what you said.
Do not use ableist slurs on Lemmy.World.
Tip of the day: When an admin of an instance adivses you not to break the Terms of Service… consider refraining from doing so.
Good-bye.
I always run a few things after a new build to test for hardware issues:
I ran one from a distro iso when I first got the pc and I got no issues. I’ll run it again just to be safe. Thank you.
It can also happen if you moved the PC recently. RAM and socket sometimes make a bad connection after vibrations.
I've had a CPU temperature probe fail after a 1 hour car ride. Had to remove it and socket it again for it to work again.