https://bugzilla.novell.com/show_bug.cgi?id=773487 https://bugzilla.novell.com/show_bug.cgi?id=773487#c3 --- Comment #3 from Olaf Hering <ohering@suse.com> 2012-07-31 19:23:31 CEST --- (In reply to comment #2)
Any reason this is filed against GNOME? :-)
Because the current issue is with GNOME and its settings.
(In reply to comment #0)
GNOME2: create /etc/gconf/gconf.xml.mandatory/%gconf-tree.xml, which sets the background color to black and enables the blank screensaver. Its not clear to me whether there can be a more specifc filename can be used. It handles gdm and a user session well in my testing.
Note that this file might exist already (that's how you lockdown a system), so you should be ready to update it if it exists.
Is there a tool where I can simple peek into an existing .xml file and see if the parts the runlevel script is about to modify are already there? I think the simplest approach is to just leave the file alone if its already there.
GNOME3: create /etc/dconf/db/gdm.d/99-nosplash, which sets the background color to black. During boot 'dconf update' is called so that the changes get applied. Its not clear to me how to temporary propagate the background setting into a user session. I see ~user/.config/dconf/user contains the background setting, but appearently a global file /etc/dconf/db/user has no effect. Here I need advise how to implement the feature.
See the lockdown part at https://live.gnome.org/dconf/SystemAdministrators
Thanks for that link. Meanwhile I found another similar blog post. However the link above states that GSettings have to be used, but fails to provide a link to an example. Do you happen to have an example?
This is the most reliable way to force the background for all users, but users won't be able to change the background.
Thats the point, because I'm the user once I connect to the VM graphical display. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.