#gsettings — Public Fediverse posts

Inconsistence dconf versus gsettings #dconf #gsettings

https://askubuntu.com/q/1565936/612

1. Since GNOME Settings seems to depend on #AuthSelect (at least on #fedora), ensure that it is running, using your preferred profile (e.g., in my case `local`) and fingerprint auth is generally enabled: `sudo authselect select local && sudo authselect enable-feature with-fingerprint`
2. Enroll your fingerprint in GNOME Settings -> System -> Users
3. Now, disable authselect since it cannot distinguish b/w loggin in and other types of authentication and otherwise #GDM #gSettings will complain that "the key is not writable" :( `sudo authselect opt-out`
4. Remove the line pertaining enable-fingerprint-authentication from the #dconf lock in `/etc/dconf/db/distro.d/locks/20-authselect`
5. Recompile dconf: `sudo dconf update`
6. Finally, configure GDM to not use fingerprint authentication for your user: `gsettings set org.gnome.login-screen enable-fingerprint-authentication false`
7. Optionally (untested): Ensure that `dbus-launch` is installed and run `sudo -u gdm dbus-launch gsettings set org.gnome.login-screen enable-fingerprint-authentication false` to disable this system-wide.

Unfortunately, not only does authselect not distinguish b/w anything GDM related and other auth types, GDM doesn't distinguish b/w log-in and unlocking the screen(?) So this breaks fingerprint screen-unlock.

2/3

1. Since GNOME Settings seems to depend on #AuthSelect (at least on #fedora), ensure that it is running, using your preferred profile (e.g., in my case `local`) and fingerprint auth is generally enabled: `sudo authselect select local && sudo authselect enable-feature with-fingerprint`
2. Enroll your fingerprint in GNOME Settings -> System -> Users
3. Now, disable authselect since it cannot distinguish b/w loggin in and other types of authentication and otherwise #GDM #gSettings will complain that "the key is not writable" :( `sudo authselect opt-out`
4. Remove the line pertaining enable-fingerprint-authentication from the #dconf lock in `/etc/dconf/db/distro.d/locks/20-authselect`
5. Recompile dconf: `sudo dconf update`
6. Finally, configure GDM to not use fingerprint authentication for your user: `gsettings set org.gnome.login-screen enable-fingerprint-authentication false`
7. Optionally (untested): Ensure that `dbus-launch` is installed and run `sudo -u gdm dbus-launch gsettings set org.gnome.login-screen enable-fingerprint-authentication false` to disable this system-wide.

Unfortunately, not only does authselect not distinguish b/w anything GDM related and other auth types, GDM doesn't distinguish b/w log-in and unlocking the screen(?) So this breaks fingerprint screen-unlock.

2/3

1. Since GNOME Settings seems to depend on #AuthSelect (at least on #fedora), ensure that it is running, using your preferred profile (e.g., in my case `local`) and fingerprint auth is generally enabled: `sudo authselect select local && sudo authselect enable-feature with-fingerprint`
2. Enroll your fingerprint in GNOME Settings -> System -> Users
3. Now, disable authselect since it cannot distinguish b/w loggin in and other types of authentication and otherwise #GDM #gSettings will complain that "the key is not writable" :( `sudo authselect opt-out`
4. Remove the line pertaining enable-fingerprint-authentication from the #dconf lock in `/etc/dconf/db/distro.d/locks/20-authselect`
5. Recompile dconf: `sudo dconf update`
6. Finally, configure GDM to not use fingerprint authentication for your user: `gsettings set org.gnome.login-screen enable-fingerprint-authentication false`
7. Optionally (untested): Ensure that `dbus-launch` is installed and run `sudo -u gdm dbus-launch gsettings set org.gnome.login-screen enable-fingerprint-authentication false` to disable this system-wide.

Unfortunately, not only does authselect not distinguish b/w anything GDM related and other auth types, GDM doesn't distinguish b/w log-in and unlocking the screen(?) So this breaks fingerprint screen-unlock.

2/3

1. Since GNOME Settings seems to depend on #AuthSelect (at least on #fedora), ensure that it is running, using your preferred profile (e.g., in my case `local`) and fingerprint auth is generally enabled: `sudo authselect select local && sudo authselect enable-feature with-fingerprint`
2. Enroll your fingerprint in GNOME Settings -> System -> Users
3. Now, disable authselect since it cannot distinguish b/w loggin in and other types of authentication and otherwise #GDM #gSettings will complain that "the key is not writable" :( `sudo authselect opt-out`
4. Remove the line pertaining enable-fingerprint-authentication from the #dconf lock in `/etc/dconf/db/distro.d/locks/20-authselect`
5. Recompile dconf: `sudo dconf update`
6. Finally, configure GDM to not use fingerprint authentication for your user: `gsettings set org.gnome.login-screen enable-fingerprint-authentication false`
7. Optionally (untested): Ensure that `dbus-launch` is installed and run `sudo -u gdm dbus-launch gsettings set org.gnome.login-screen enable-fingerprint-authentication false` to disable this system-wide.

Unfortunately, not only does authselect not distinguish b/w anything GDM related and other auth types, GDM doesn't distinguish b/w log-in and unlocking the screen(?) So this breaks fingerprint screen-unlock.

2/3

1. Since GNOME Settings seems to depend on #AuthSelect (at least on #fedora), ensure that it is running, using your preferred profile (e.g., in my case `local`) and fingerprint auth is generally enabled: `sudo authselect select local && sudo authselect enable-feature with-fingerprint`
2. Enroll your fingerprint in GNOME Settings -> System -> Users
3. Now, disable authselect since it cannot distinguish b/w loggin in and other types of authentication and otherwise #GDM #gSettings will complain that "the key is not writable" :( `sudo authselect opt-out`
4. Remove the line pertaining enable-fingerprint-authentication from the #dconf lock in `/etc/dconf/db/distro.d/locks/20-authselect`
5. Recompile dconf: `sudo dconf update`
6. Finally, configure GDM to not use fingerprint authentication for your user: `gsettings set org.gnome.login-screen enable-fingerprint-authentication false`
7. Optionally (untested): Ensure that `dbus-launch` is installed and run `sudo -u gdm dbus-launch gsettings set org.gnome.login-screen enable-fingerprint-authentication false` to disable this system-wide.

Unfortunately, not only does authselect not distinguish b/w anything GDM related and other auth types, GDM doesn't distinguish b/w log-in and unlocking the screen(?) So this breaks fingerprint screen-unlock.

2/3

Einblick in gsettings

Eine kleine Anregung, wie man GNOME schnell und effektiv auf den eigenen Workflow anpassen kann.

#Gnome #gsettings #Konfiguration #Terminal #Linux

https://gnulinux.ch/einblick-in-gsettings

Einstellungssache

Bei Computersystemen ist grundsätzlich alles einstellbar. Die Frage ist, wie einfach es ist, Konfigurationen zu ändern.

#gsettings #dconf #dconf_editor #Einstellungen #GNOME_Einstellungen #Linux

https://gnulinux.ch/einstellungssache

Einstellungssache

Bei Computersystemen ist grundsätzlich alles einstellbar. Die Frage ist, wie einfach es ist, Konfigurationen zu ändern.

#gsettings #dconf #dconf_editor #Einstellungen #GNOME_Einstellungen #Linux

https://gnulinux.ch/einstellungssache

Einstellungssache

Bei Computersystemen ist grundsätzlich alles einstellbar. Die Frage ist, wie einfach es ist, Konfigurationen zu ändern.

#gsettings #dconf #dconf_editor #Einstellungen #GNOME_Einstellungen #Linux

https://gnulinux.ch/einstellungssache

Einstellungssache

Bei Computersystemen ist grundsätzlich alles einstellbar. Die Frage ist, wie einfach es ist, Konfigurationen zu ändern.

#gsettings #dconf #dconf_editor #Einstellungen #GNOME_Einstellungen #Linux

https://gnulinux.ch/einstellungssache

Einstellungssache

Bei Computersystemen ist grundsätzlich alles einstellbar. Die Frage ist, wie einfach es ist, Konfigurationen zu ändern.

#gsettings #dconf #dconf_editor #Einstellungen #GNOME_Einstellungen #Linux

https://gnulinux.ch/einstellungssache

I got somewhat fed up with manually configuring machines, so here's a snapshot of my current #automation for a #fedora #desktop install (this does #flatpak, #copr, #gsettings, #git #builds, you name it--and yes, the name is a pun on #cloudinit):

https://github.com/rcarmo/ground-init

How To Configure Touchpad Settings Using gsettings Commandline Utility In Linux #Gsettings #Linux #Touchpad #LinuxTips
https://ostechnix.com/configure-touchpad-settings-using-gsettings-commandline-utility/

Just pushed a small blog entry on accessing #gnome user preferences from the command line with the #gsettings tool:

https://blog.lazy-evaluation.net/posts/linux/gsettings-diff.html

Configure Touchpad Settings Using gsettings Commandline Utility #GSettings #Laptop #Touchpad #Linux
https://ostechnix.com/configure-touchpad-settings-using-gsettings-commandline-utility/

Configure Touchpad Settings Using gsettings Commandline Utility #Touchpad #gsettings #Gnome #Linux #CLI
https://www.ostechnix.com/configure-touchpad-settings-using-gsettings-commandline-utility/

Setting multiple key bindings for the same action in GNOME

https://ar.al/2019/03/11/setting-multiple-key-bindings-for-the-same-action-in-gnome/

#gnome #gsettings #keybindings