- cross-posted to:
- news
- linux@lemmy.ml
- cross-posted to:
- news
- linux@lemmy.ml
Welcome to a new issue of This Week in Plasma. And it’s going to be a big one, folks! This week, a familiar pattern played out: people upgraded to Plasma 6.8 and found all the bugs that nobody reported during the beta period, and the Plasma team worked incredibly hard to fix them! You’ll see the result below: tons of bug fixes.
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.
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.
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.