Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#9023 - nvidia-settings freezes xorg when changing refresh rate
Attached to Project:
Arch Linux
Opened by Thiago A. Silva (thiagoaraujos) - Thursday, 27 December 2007, 18:44 GMT
Last edited by Greg (dolby) - Saturday, 17 May 2008, 16:58 GMT
Opened by Thiago A. Silva (thiagoaraujos) - Thursday, 27 December 2007, 18:44 GMT
Last edited by Greg (dolby) - Saturday, 17 May 2008, 16:58 GMT
|
DetailsDescription:
nvidia-settings app freezes xorg, and I can only move the mouse and do anything. Keys such as ctrl+alt+backspace or ctrl+alt+fX don't work and I'm obliged to manually reset my machine. GNOME's resolution app tells me my LCD monitor's refreshing rate runs at 50 hz... when I open up nvidia-settings to change this setting to 60 hz (the correct value) the above happens. I'm almost sure that it's already running at 60 hz, but GNOME insists to show 50 hz... or I would be blind right now. I used to do exactly the same in gentoo and it didn't freeze. Afterwards, looking at GNOME's resolution settings, refreshing would change to 55 hz (not 60hz...) monitor: LG L17660TQ card: GeForce FX 5200 Additional info: * package version(s) nvidia-settings version 1.0 * config and/or log files etc. Steps to reproduce: 1. open up nvidia-settings 2. go to X Server Display Configuration 3. change refresh from AUTO to 60 hz 4. click apply (screen gets black a second, then freezes in the previous screen) |
This task depends upon
But my KDE also displays 50Hz although I use 85Hz. It's a strange behaviour of the nvidia driver.
@Thomas: I guess this may be an upstream bug, anyway we cannot do much about it, so feel free to close it.