This is an automatic notification regarding your Bug report which was filed against the open-infrastructure-system-config package:
#832741: support gconf/gsetting/dconf local-or-global toggle It has been closed by Debian FTP Masters <[email protected]>. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Debian FTP Masters <[email protected]> by replying to this email. -- 832741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832741 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Version: 20190301-lts1-5+rm Dear submitter, as the package open-infrastructure-system-tools has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1137258 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
--- Begin Message ---Package: live-config Severity: wishlist On 05/03/2013 07:18 AM, Trent W. Buck wrote: > 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. we should have an option in live-config that allows to toggle local (user-specific) gconf/gsettings or global (system-wide), thank for bringing that up, filling as a wishlist bug to be adressed somewhen in live-config 4. > 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. -- Address: Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: [email protected] Internet: http://people.progress-technologies.net/~daniel.baumann/
--- End Message ---
