this post was submitted on 07 Jan 2026
33 points (97.1% liked)
Linux
11002 readers
770 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments

Even if sandboxed, why would it need su permissions?
Good question and without looking closer or verifying I'd guess it actually doesn't.
Usually such things happen because at some point someone had an issue with accessing a hardware device or something and this became the "fix" perhaps because udev was confusing.
If someone cares enough about it, tidying up loose flatpak packaging ends like that is often appreciated and a great way to contribute.
I wonder where it was installed from (flathub?) and whether it has something to do with the linux version. Since at least two of us don't see a superuser notification (turdas and me) but we are both on Fedora.
Yes I installed it from Flathub. IanTwenty's comment says it is a longstanding bug with the MATE environment I am using, where flatpak's running as a sandboxes process user ID show up as SU in the title bar when they actually aren't.
Thanks, that makes sense. All good I guess.
Well, but Flatpak also has the rule to not break anything by default.
And they call things like changing filesystem=host to the specific directories (home, run, mnt) "security theatre" and prefer waiting forever for legacy apps to magically fix it