On 22 February 2018 at 18:39, Michal Jaegermann <michal.jnn@xxxxxxxxx> wrote: > On Thu, Feb 22, 2018 at 04:00:44PM +0200, Ahmad Samir wrote: >> On 22 February 2018 at 14:58, Russel Winder <russel@xxxxxxxxxxxxx> wrote: >> > On Thu, 2018-02-22 at 04:04 -0800, Adam Williamson wrote: >> >> […] >> >> >> >> Anything settable in control-center is likely backed with a dconf key >> >> you could set. >> > >> > True. Finding the path to the key is not always obvious though. I am >> > guessing that in this case org.gnome.session-daemon may be the place. >> > >> >> $ gsettings list-keys org.gnome.settings-daemon.plugins.power >> >> (I usually find that grep'ing in '/usr/share/glib-2.0/schemas/' is >> sort of faster/easier). > > This still leaves a question how you are going to modify that for > gdm on a machine of a type "server - most of the time"? If I understood > Russel correctly such setup is hugely affected. > > Michal I missed that part, sorry. One (hackish) way would be to create a new user account, modify only those gsettings keys then copy ~/.config/dconf/user to (the gdm user home dir[1]) /var/lib/gdm/.config/ and of course make the file owned by gdm. I haven't tested that method though; but IIRC, one way to get gdm to use custom multiple monitor settings was to copy ~/.config/monitors.xml (created by the display module of gnome-control-center) from your regular user account to /var/lib/gdm/.config/ . I hope that helps. [1] which I could see/guess in /etc/passwd. -- Ahmad Samir _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
