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.
After extended testing, KWin’s support for the Wayland picture-in-picture (PiP) protocol has been deemed stable enough, and turned on by default! (Vlad Zahorodnii, kwin MR #10175)
Yeeeeeeessssssssss
Edit:
In-progress downloads in Firefox that produce a nice native Plasma notification via Plasma Browser Integration can now be paused and resumed from that notification. (Simon Hürlimann, plasma-browser-integration MR #207)
Yeeeeeeeeeeeeeeeessssssssssss
This release of plasma (6.8 and 6.8.1) has been buggy for me. I hope it’s not because they went hard on vibe-coding. Use AI, guys, but please not blindly. I’m having random freezing, issues with suspending the pc, memory issues and many others that for the first time in like 5 years, I’ve considered moving to gnome or something. This is how bad it has gotten.
I’m in the process of constructing several bug reports for them. They’re going to hate me. lol
This release of plasma (6.8 and 6.8.1) has been buggy for me.
dot-0 and dot-1 releases have always been on the more buggy side, simply because several bigger distributions tend to aim for dot-2 or dot-3 releases and rolling release users are the early adopters who do the bug reporting.
I’m having random freezing, issues with suspending the pc, memory issues and many others that for the first time in like 5 years
I suspect you’re on a rolling release distribution and something broke in general. How would a DE cause memory issues?
I AM on a rolling release, Cachy OS, but a desktop is not immune to memory leaks. Plasma can absolutely cause memory issues. Not vetting CachyOS because I haven’t tested personally to know for a fact it’s the distro, not the DE, but DEs can absolutely cause memory issues.
This might sound strange but have you run fs-trim lately? My pc was lagging a lot in normal use and games, that was because I hadn’t ran an fs-trim in 3 years.
Thank you for suggesting this. I haven’t run it in probably a year. I’ll do that actually anyway.
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.
These are literally not even a month old memory sticks
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.
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.
I said “I hope”
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.
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.
Does the Wayland PiP work with any application window? Oh the linked issue https://invent.kde.org/plasma/kwin/-/merge_requests/10175 talks about Firefox. Is this only about Firefox? I’m confused.
Firefox has a PiP mode for videos, not any generic window
I know. My question was, is this new PiP mode in Plasma a generic Wayland feature, or is it about the Firefox’s own PiP mode.
is this new PiP mode in Plasma a generic Wayland feature
“the Wayland picture-in-picture (PiP) protocol” So yes, of course.
That’s what I assumed too. But the linked issue talks just about Firefox.
I understood it as blacklisting support for the protocol because Firefox’s implementation was too buggy.
Oh now I understand! Firefox was the blocker to finally release a generic Wayland implementation! Man sometimes I have the feeling I can’t think. Thanks for your patience.
Disclaimer: I could be wrong.
