I noticed in live-config (3.0.23-1) several cases where gconf2 settings
are set for the user just created:
0040-sudo: sudo -u "${LIVE_USERNAME}" gconftool-2 -s -t bool
/apps/gksu/sudo-mode true
0040-sudo: sudo -u "${LIVE_USERNAME}" gconftool-2 -s -t bool
/apps/gksu/display-no-pass-info false
1020-gnome-panel-data: sudo -u "${LIVE_USERNAME}" gconftool-2 -s -t bool
/apps/panel/global/disable_lock_screen true
1030-gnome-power-manager: sudo -u "${LIVE_USERNAME}" gconftool-2 -s -t bool
/apps/gnome-power-manager/general/can_hibernate false
1040-gnome-screensaver: sudo -u "${LIVE_USERNAME}" gconftool-2 -t bool -s
/apps/gnome-screensaver/lock_enabled false
It is possible to set these properties for all users at build time
instead of boot time. I use this because my live users have persistent
accounts in LDAP and homes in NFS; there's no "guest" account.
I don't know if this is useful for normal live users; since GNOME3
replaces gconf2 with dconf, I suppose it's a moot point.
Anyway, you do it like this:
gconftool-2 --direct --config-source
xml:readwrite:/etc/gconf/gconf.xml.default -s -t <type> <key> <value>
You can also lock down arbitrary properties this way, by changing .default to
.mandatory.
I use this, for example, to stop my netboot users from changing their wallpaper.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
