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 167976 - resolution should be X-server specific, not host specific
resolution should be X-server specific, not host specific
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: Display
2.12.x
Other Linux
: Normal major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks: randr-tracker
 
 
Reported: 2005-02-20 19:46 UTC by Stanislav Brabec
Modified: 2009-02-26 01:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Stanislav Brabec 2005-02-20 19:46:07 UTC 
Screen resolution preferences allows to set resolution per-host, which seems to
be nosense. For remote logins, screen resolution does not depend on machine, to
which you are logging, but on X-server machine, from which you are logging (i.
e. machine, where you are actually sitting).

Also option "Reset to server default" is missing.

Fix: Use DISPLAY machine, not HOSTNAME machine.
Comment 1 Stanislav Brabec 2005-09-19 13:34:07 UTC 
Confirming bug in GNOME 2.12.

There os another scenario, which makes GNOME unusable:

1. Start gnome-display-properties on big display. Check in "Make default for this
computer (hammer) only."
2. Swap displays (use display, which cannot use default frequency of previous
monitor), reconfigure X.
3. GNOME starts, display is switched to unusable mode.

So fix should be even stricter and should check X configuration anyhow (either
check display type or default values provided by X).
Comment 2 Stanislav Brabec 2005-09-19 13:45:39 UTC 
Increasing bug to major, because user needs advanced knownedge to work-around
this bug.

This bug also affects data projector users.
Comment 3 Jean-François Fortin Tam 2005-12-07 14:39:36 UTC 
confirm, PLEASE make it read the xorg.conf or make it disappear

My rationale: I have tons of users moaning that they are stuck to 1024x768 60Hz,
while they have explicitely set higher resolutions in their xorg.conf. And it
happens to me too. This is so bad that I have set only one possible resolution
in my xorg.conf so that GNOME does not have a choice at all. That was done
before actually installing GNOME.
Comment 4 Federico Mena Quintero 2009-02-26 01:58:27 UTC 
This bug is obsolete now that gnome-display-properties uses RANDR.