#dconf — Public Fediverse posts

Inconsistence dconf versus gsettings #dconf #gsettings

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

Gefunden! Muss in den Einstellungen #DConf Editor expliziert aktiviert werden. Sicherheit ja, aber Verblödung nein! //Edit: geht auch einfacher. Einstellungen von Nautilus

@gnome

#GNOME #GNOME4 #GNOME49 #Nautilus #Dateimanager #Fail #Link #Verknüpfung

the #dconf editor is my best friend at the moment :)

The #AI created for my #dconf sync tool (over git). I upload it to #codeberg. Would be great if a real brain could have a look at it and maybe improve it :)

https://codeberg.org/Nasendackel/SyncDconf

Today I learned that if in #Ubuntu #Linux if you mess up your #dconf settings, maybe by clicking on the wrong thing in a #Gnome Extension (such as "Just Perfection", which really isn't perfect because it doesn't prompt you before making changes that can't easily be reversed), AND if you have a very recent backup of your home directory (because you use BackInTime or similar backup software), you can try restoring a very recent version of the file

/home/*username*/.config/dconf/user

(Replace *username* with your actual user name). Works in Ubuntu 24.04. Use at your own risk, and remember any changes you have made since that file was backed up will be lost. Just to be safe you make want to copy the existing file somewhere before restoring from the backup, in case restoring it makes things worse.

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

What's the recommended way of pre-provisioning system-wide #GNOME #dconf default settings (that differ from the application's defaults)?

I don't want to apply them for every new user I create.

Here's an additional problem though: I'd like to _remove_ something from a default list/array¹. For example:

$ gsettings get org.x.pix.general active-extensions
['resize_images', 'image_print', 'webalbums', 'burn_disc', …

Can I remove specific items from there?

¹ sorry if not using correct lingo

I’ve been sat watching talks at #dconf wondering: who is this DR untime ? And are they even a real doctor?

Guess i need to write a tool (in #RustLang] that disables the on screen keyboard on my #StarLiteMkIV when a physical one is connected and enables it, if i unplug all keyboards. It should work on #GNOME for me, so i might use #dconf.

For it to work for more people, can you post the diff of `lsusb` before and after you plug in your keyboard case?
Mine shows an entry without description. @starlabssystems can you confirm this?

Linux Desktop Migration Tool 1.4

After many months, I finally found the time to finish the GNOME desktop/application settings migration in the Linux Desktop Migration Tool and did another release.

#dconf #gnome #linux #migration

https://enblog.eischmann.cz/2024/08/19/linux-desktop-migration-tool-1-4/

Any #DConf experts here?
How can I tell which keys are writable and which aren't?

To avoid "error: The operation attempted to modify one or more non-writable keys" when doing "dconf dump /" & "dconf load /".

/etc/dconf/db/local.d/locks is empty BTW.

Variable refresh rate.

#GNOME #VRR #dconf #Mutter #Wayland

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

Looks like somebody accidentally left the video recorder on during my #dconf lightning talk, so now there is a public record of one of my five minute "routines" 😱.

(I clearly picked up on more laughter than the microphone... 😏)

https://www.youtube.com/live/CMrb6ZWhqXs?si=m7CG8NabZ_UN-Hyi&t=19320

@edgren @joel
Ehmmm nope, it's not...no mentioning of the DE.
Anyways, I tried a "dconf watch /" and apparently the majority is indeed stored in $config/xfce
Other stuff, like mouse cursor theme is dconf as I thought. You can save these configurations via:
dconf dump /
("dconf help" for all options)

Unfortunately also #dconf does not store everything. And now more clues would be needed for the remaining setting... but it's cluttered imho 🤷😄

Fighting with #dconf to write an install script for my bottom info panel 😕
But either dconf as such is cluttered, or the #mate DE muddles it up so much. Stuff that in my understanding belongs together, is stored in so many different places.....aaarghh

Reset Linux Desktop To Default Settings With A Single Command #Dconf #Linux #Linuxhowto #Linuxtips
https://ostechnix.com/reset-linux-desktop-default-settings-single-command/

@onlytina
Ich hab da nen Ansatz, aber da ich KDE nicht benutze, frage in die Runde: verwendet KDE auch #dconf?
Das verwende ich (unter Mate) um so Setups zu sichern und gegebenfalls wieder her zu stellen.

How To Reset Gnome Desktop Settings To Default In Linux #Gnome #Dconf #GnomeTweaks #Linux #Linuxhowto #Linuxtips
https://ostechnix.com/reset-gnome-desktop-settings-to-default-in-linux/

Backup And Restore Linux Desktop System Settings With Dconf #SystemSettings #Dconf #Linux #Linuxhowto #Linuxtips
https://ostechnix.com/backup-and-restore-linux-desktop-system-settings-with-dconf/

Reset Linux Desktop To Default Settings With A Single Command #Dconf #Linux #Linuxtips
https://ostechnix.com/reset-linux-desktop-default-settings-single-command/

Easily And Quickly Backup And Restore Linux Desktop System Settings With Dconf #Linux #dconf #SystemSettings #CLI
https://www.ostechnix.com/backup-and-restore-linux-desktop-system-settings-with-dconf/

Reset Linux Desktop To Default Settings With A Single Command #Dconf #LinuxTips #ResetLinux #Troubleshooting #Linux #Ubuntu
https://www.ostechnix.com/reset-linux-desktop-default-settings-single-command/