Bug 2406896 - Can't easily change settings in dconf-editor
Summary: Can't easily change settings in dconf-editor
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: dconf-editor
Version: 43
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-28 19:24 UTC by Andre Robatino
Modified: 2025-10-29 04:52 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Andre Robatino 2025-10-28 19:24:12 UTC
I noticed that the instructions for changing dconf settings at https://discussion.fedoraproject.org/t/gnome-suspends-after-15-minutes-of-user-inactivity-even-on-ac-power/79801 no longer work. I tried to make the changes using dconf-editor but it doesn't work there either. For example if I go to org.gnome.settings-daemon.plugins.power and try to change the setting for sleep-inactive-ac-timeout, each character entered causes a popup "The change will be applied on such request or if you quit this view." which prevents completing the entire change. The default value was "900" and I wanted it to be "0", and was only able to set this to 0 by getting clever and deleting the "9" (which won't work for a general value). Even then, the command

sudo -u gdm dbus-run-session gsettings list-recursively org.gnome.settings-daemon.plugins.power | grep sleep

claims that the value is still 900, even though dconf-editor says it's 0, so I don't know what the actual value is.

Reproducible: Always

Comment 1 Andre Robatino 2025-10-29 04:52:35 UTC
Also noticed that the value shown by the gsettings command is not necessarily the same as that shown by dconf-editor, see my post https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/thread/3YTW5J4SRS6Z2UXW2TS4VBCRRFO6WRJG/ .


Note You need to log in before you can comment on or make changes to this bug.