Gefunden! Muss in den Einstellungen #DConf Editor expliziert aktiviert werden. Sicherheit ja, aber Verblödung nein! //Edit: geht auch einfacher. Einstellungen von Nautilus
#GNOME #GNOME4 #GNOME49 #Nautilus #Dateimanager #Fail #Link #Verknüpfung
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 :)
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
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
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?
Hessenhelden
in ♥️ with PDA (and 🐧)
HoldMyType
josmit
maple
lj·rk
scy
Chris Oldwood
chfkch 
