Written by themacmeister the 10 Mar 09 at 09:36.

Code a new screen resolution app that reads DDC correctly from the monitor (or EDID?).

This is almost unacceptable for a window manager as mature as Gnome.

Code a new screen resolution app that reads DDC correctly from the monitor (or EDID?). This is almost unacceptable for a window manager as mature as Gnome.

Written by aysiu the 10 Mar 09 at 19:45.

If a user knows her monitor can and should handle 85Hz, she should be able to input 85Hz as a number directly instead of just picking from a list of guesses as to what refresh rates the monitor can support.

If a user knows her monitor can and should handle 85Hz, she should be able to input 85Hz as a number directly instead of just picking from a list of guesses as to what refresh rates the monitor can support.

Written by _uu_ the 15 Mar 09 at 13:41.

When running the application NVIDIA X Server Settings from the GNOME Applications menu (Applications >> System >> Administration >> NVIDIA X Server Settings), it is not run as root (as opposed to most other applications in that submenu). Therefore the settings won't "stick" as the changes cannot be "Saved to X Configuration File".

Changing that menu point to be run as root by default or with (gk)sudo and being asked for the password should at least solve the NVIDIA X Server Settings issue. It is equivalent to running 'sudo nvidia-settings' in a terminal.

Of course, additionally the Gnome app definitely needs some improvement as Solution #2 suggests.

When running the application NVIDIA X Server Settings from the GNOME Applications menu (Applications >> System >> Administration >> NVIDIA X Server Settings), it is not run as root (as opposed to most other applications in that submenu). Therefore the settings won't "stick" as the changes cannot be "Saved to X Configuration File". Changing that menu point to be run as root by default or with (gk)sudo and being asked for the password should at least solve the NVIDIA X Server Settings issue. It is equivalent to running 'sudo nvidia-settings' in a terminal. Of course, additionally the Gnome app definitely needs some improvement as Solution #2 suggests.

Written by cprise the 26 Mar 09 at 02:28.

...instead of putting the burden on outside projects to properly parse and write xorg.conf data in all its variations and under all circumstances.

It would work far more smoothly to have the settings logic moved into xorg itself, with a simple API for reading the config options for the given hardware and having the screen res app presenting those options to the user.

When the user wants to save the screen settings permanently, its a simple API call to have xorg write the xorg.conf file itself.

I know this is the most politically difficult (impossible?) of the solutions presented here, but there really is no hope of a first rate control app coming from any single distro. Complex system services that don't serialize their own config data to disk simply aren't going to work well for the end-users.

...instead of putting the burden on outside projects to properly parse and write xorg.conf data in all its variations and under all circumstances. It would work far more smoothly to have the settings logic moved into xorg itself, with a simple API for reading the config options for the given hardware and having the screen res app presenting those options to the user. When the user wants to save the screen settings permanently, its a simple API call to have xorg write the xorg.conf file itself. I know this is the most politically difficult (impossible?) of the solutions presented here, but there really is no hope of a first rate control app coming from any single distro. Complex system services that don't serialize their own config data to disk simply aren't going to work well for the end-users.