GNOME Bugzilla – Bug 703493
Add "apply systemwide option"
Last modified: 2013-07-03 07:46:30 UTC
<drago01> halfline: is there any "sane" way to deicide on which monitor gdm will show the greeter? <drago01> halfline: it was on the "wrong" one here after updating to f19 <drago01> halfline: I "fixed" it by copying monitors.xml to /var/lib/gdm/.config <airlied> drago01: its always the "wrong" one for someone <airlied> other OSes used to at least clone the login box <airlied> but we've had designers say that is stupid, but fail to come up with an actual answer <drago01_> airlied: yeah I am asking for a non hack way to select the "right one" <drago01_> yeah cloning make sense <drago01_> aday: ^^ <adamw> airlied: it's a GNOME config issue - the GNOME Displays capplet does not have an 'apply systemwide' option <adamw> airlied: so there's no way beyond manual config file hackery to set up a systemwide display configuration via GNOME utils <airlied> adamw: yes that would hep I suppose <drago01_> adamw: yeah that's what I did by copying the file around <adamw> right <adamw> airlied: other GNOME config tools can do it, so Displays really ought to as well <airlied> yeah displays ought to do a lot of things :-P * drago01_ files a bug <adamw> drago01_: i think the model you guys came up with for the locale stuff would work nicely for Displays I see no reason why we don't do that ...
to expand on "<adamw> drago01_: i think the model you guys came up with for the locale stuff would work nicely for Displays" - the user's locale settings are simply automatically applied systemwide if there is only one user account and that user is an admin, otherwise (multiple users, or the single user is not an admin) there's a button marked 'Login Screen' which lets you configure systemwide settings. (I find the 'Login Screen means systemwide' association a bit obtuse for Region & Language, is my only criticism of that design, but it'd actually be perfect for Displays).
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 697903 ***