@swags there's already a gsettings key; the change is from true to false: https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/merge_requests/119

@swags Chrome will start listening to the GTK setting in the next release, and Firefox also may disable it by default (but still listen to the GTK setting)

@swags it's being disabled by default in GTK applications and anything that listens to the GTK settings

@GerryT you didn't bother checking what we're actually doing, before launching yourself into a tirade?

https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/merge_requests/119

The setting exists already, and it can be toggled in the CLI and using apps like Tweaks and Refine. The discussion in the merge request is: 1. disable by default and 2. add the toggle somewhere that's easy to find

@uriel that, or even something inside the system settings themselves

@uriel it *is* configurable already: the whole thing is deciding whether to turn it off by default or not.

@danirabbit need to pick up the history of GNOME again…

@bugaevc I've have bug reports for gdk-pixbuf being broken after the switch to sandboxed loaders because people run gparted as root and modify the environment to set themes and cursors from their user's home directory. This is the kind of insanity we allow, while going around sandboxing and hardening the underlying OS.

@bugaevc that XKCD strip is fundamentally flawed: installing fake software running as an admin is how people get access to all those remote services without having to physically steal the laptop.

The problem is not running gparted (or whatever application): it's running everything, from settings to random (GTK) modules, as root without your knowledge or consent. You don't know what else has root access when you run a whole ass GUI application.

@whynothugo an OpenBSD and Alpine user coming here and arguing for ease of use with handrolled IPC sockets instead of the proper privilege escalation API that is well integrated with desktop environments used by millions of people…

@whynothugo sorry, but nothing of what you wrote is correct, or how things are supposed to work in 2025. I strongly recommend you stop hurting yourself.

@whynothugo in short: yes, there's some complexity, usually already dealt with by the people developing the applications and integrating your OS. The complexity is not there for shits and giggles, and it's only visible if you're taking over from those two roles above. Some computer touchers enjoy doing the integrator's job, but that's not something that actual users have to care about.

@whynothugo "depends on polkit" yeah, no shit. The privilege escalation flow is a solved problem if you use the tools that the OS provides you. "Something dead simple" is not a thing, unless you want to re-implement everything that already exists and is well integrated with the rest of the OS. In short: people don't want "dead simple" as in "I have to run two binaries"; they want something that works like everything else.

@whynothugo anything that uses udisks should be fine, like GNOME Disks; any missing feature that gparted needs should be added to udisks.

@douginamug use software that has proper separation of security domains, and uses authenticated escalation for privileged operations

@sheogorath why are you even using a computer if you want to go back to a prelapsarian rural golden age?

@simoncrowe do fdisk and mkfs.* come with a GUI and about a million lines of unaudited code?

@swags you don’t need a company, you just need a legal entity—and you can get away with a non-profit for that.

I was also not referring to just Mozilla with that sentence.

@jntesteves Yep, the existing settings portal is not exposing the "enable animations" toggle that GTK expects, and KDE has a setting for the animation duration (with zero meaning disable animations) instead. Ideally, once we have this shared setting, we can properly bridge it, and implement true reduced motion, instead of a janky "turn every animation into an immediate end state transition"