I like how none of the comments here are about the exploit, but all to do with the semantics of the title and the undertone of it. It’s pretty clear people that use Arch will not like Flatpak. I personally don’t care and find it a competent and perfectly able solution to the issue of shipping your software to just about all popular Linux distros without the developer wanting to pull their hair out in frustration. I hope that the KDE team and the Flatpak team can work together to fix this exploit.
Exactly! It doesn’t really matter!
I will say that it is annoying to see people dismiss a perfectly fine solution simply because “it adds bloat to the system”, but yeah, the point of the thread at hand isn’t Flatpak opinions.
I completely understand why @cactux is pointing out the issue with the title. This is not a flatpak, appimage, or snap issue but a Kwin issue. Kwin is not doing the right thing. Based on the details in the blog this is not even a KDE needs to work with the flatpak developers it is a KDE needs to fix it on its own. The flatpak is behaving as expected, Kwin is not handling things correctly and allowing it to escape containment.
Thank you!
at the end of the day another exploit is caught and dealt with (or being dealt with). Linux would be nothing without all the eyes ad ears it can get. So I see the upside.
I’ve renamed the topic as was initially suggested, forgive my intrusion @MyNameIsRichard, to hopefully better reflect the substance of the issue, and to let that point of contention rest.
Let’s permit one another a bit of clemency please.
(post deleted by @cactux TheOneAndOnly 
)
This thread has run its course.