I’m turning GNOME animations off via the following command in the terminal:
gsettings set "org.gnome.desktop.interface" "enable-animations" "false"
This works the very first time. After that, after every fresh boot, the effect is gone. I have to repeat changing the setting. And that’s not even enough:
Just repeating the same command is not sufficient. I first have to invert the setting, then put in the setting that I actually want again:
gsettings set "org.gnome.desktop.interface" "enable-animations" "true"
gsettings set "org.gnome.desktop.interface" "enable-animations" "false"
The above is what I need after every boot. Why is that?
How I see the results? In the “gedit” text editor, smooth scrolling depends on animations being enabled.
Edit 1: Where can I see the (lack of) effect from this option after a reboot? In gedit (long text document) and Nautilus (longer list of folders and files in default view), smooth scrolling is disabled immediately after setting the option, but is enabled again after a reboot. On the contrary, in the “Applications” list opened from the dock, the open/close animation for the list remains disabled after a reboot, and smooth scrolling in the list remains disabled as well.
gsettings
on the machine (earlier), I had unintentionally usedsudo
, which caused problems because of theDBUS_SESSION_BUS_ADDRESS
env variable and I think the error message was “failed to commit changes to dconf”. I guessed that could have caused permission problems, but I can’t find any problems in my home folder. Apart from that, the temporary second account, which you suggested, has the same problem as my first account: Applying the setting works immediately, but after a reboot, the effect is gone. – caw Jun 25 '21 at 03:45sudo
one time too much, so likely some xml files have the wrong permissions. You changes cannot be written and thus are not remembered. – vanadium Jun 25 '21 at 08:43sudo gsettings set
call fails due to the missingDBUS_SESSION_BUS_ADDRESS
env variable, so it probably does not even reach a stage where wrong permissions or files would be written. Finally, the value that I set is actually preserved, it’s just that its effect is gone. So the value is certainly properly stored by gsettings. – caw Jun 25 '21 at 17:31gsettings
values are properly preserved across reboots. – caw Jun 27 '21 at 03:26desktop-icons@csoriano
,ubuntu-appindicators@ubuntu.com
,ubuntu-dock@ubuntu.com
. – caw Jun 27 '21 at 19:19~/.config/dconf/user
is owned by my user and has the permissions0664
. The directories~/.config/dconf/
and~/.config/
are owned by my user and have the permissions0700
. – caw Jun 27 '21 at 19:39gnome-tweak-tool
is not installed on my machine. In addition, when I query the value viagsettings get
after a reboot, it’s still correct. It’s just that the effect is gone. That’s why I have to change it and then revert it back to restore the effect. – caw Jun 29 '21 at 00:33gsettings set
, since simply repeating the value is not enough. Doesgsettings set
have side effects (for specific keys)? Or can applications listen togsettings
changing values in the database? One of the two most be true, I guess, otherwise the effect could not immediately be seen in gedit while a later reading of the (correct) value after a reboot is not sufficient for the effect. – caw Jun 29 '21 at 00:55ALT + F2
andr
lets the system fall back to the correct set gsettings? – starkus Jul 01 '21 at 14:38gsettings set
call must thus either have side effects or active listeners, as I said before. Right? – caw Jul 01 '21 at 23:25