After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 761678 - Implement setting default or system wide resolution settings
Implement setting default or system wide resolution settings
Status: RESOLVED DUPLICATE of bug 697903
Product: gnome-control-center
Classification: Core
Component: Display
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Debarshi Ray
Control-Center Maintainers
Depends on:
Blocks: 748098
 
 
Reported: 2016-02-07 18:13 UTC by Jeremy Newton
Modified: 2016-10-17 17:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeremy Newton 2016-02-07 18:13:40 UTC
At the moment, there's not a way to set default resolution or monitor settings for GNOME.

I see two justifications for this:

1) An administrator should be able to set the default monitor setup for new users.
For example, a special multi-monitor setup, or a monitor/graphics card that detects the wrong resolution (I have a television that does this), or possibly defaulting to a lower resolution than the detected (maybe a weak graphics card on a native hi-resolution screen?).

2) Use this "default" monitor.xml/settings for GDM. This could fix issues where the login display is on the wrong monitor, or possibly a few reasons as stated in point number 1. Basically, this would be a way to override the default GDM settings. /var/lib/gdm/.config/monitors.xml currently does this but doesn't seem to work for Wayland, see bug 748098.

Rui Matos suggested a "system wide option", but I think this a bad name to use as I don't think it should overwrite any existing monitor.xml configurations of other users. I think it would make more sense for it to act as the resolution of GDM and default for new users. Hence calling it something like "Apply as default".
Comment 1 Alexandre Franke 2016-10-17 17:22:51 UTC

*** This bug has been marked as a duplicate of bug 697903 ***