Version: (using KDE KDE 4.0.0) Installed from: Ubuntu Packages the hz is wrongly detected in monitor settings , see picture : http://img85.imageshack.us/my.php?image=bildschirmphoto1fc2.png
Can you still reproduce this bug with a recent KDE (4.1.3 / 4.2beta2 / 4.2svn) ? Thanks :)
hi i compiled from svn today and rechecked :) the bug is still there, "system-settings->Display->Size and Orientation" shows 50hz, while the nvidia-settings tools shows "60hz" , the resolution comes corectly (1920x1080). Question: the DPI (55x55) is also detected by nvidia-settings , could you set the DPI too in this Dialog ?
About the whish of having a new settings you should report it separately. Thanks for confirming the bug anyway :-)
Can you please paste here the output of running xrandr in the command line? Thanks in advance
k4@chris-desktop:~$ xrandr Screen 0: minimum 320 x 240, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 50.0* 51.0 1680x1050 52.0 53.0 1440x900 54.0 1400x1050 55.0 1360x768 56.0 57.0 58.0 1280x1024 59.0 60.0 1280x960 61.0 62.0 1280x720 63.0 1152x864 64.0 65.0 1024x768 66.0 67.0 68.0 69.0 960x600 70.0 960x540 71.0 840x525 72.0 73.0 800x600 74.0 75.0 76.0 77.0 78.0 720x450 79.0 700x525 80.0 680x384 81.0 82.0 640x480 83.0 84.0 85.0 86.0 640x400 87.0 512x384 88.0 320x240 89.0 k4@chris-desktop:~$ so, this wont be fixed ?
what are these silly hz numbers (50hz,51hz,53hz,...) if you want to forward this to xorg - close this bug
just saw the hz numbers just count from 50 to 89 - in 1hz steps !!
As can be seen in this line: 1920x1080 50.0* 51.0 the video driver is reporting the wrong active refresh rate. The KDE interface is just reporting the numbers that the X server gave it. There is nothing really we can do to solve your problem. It a problem in the video driver you are using, so I would recommend reporting this to X developers or in the nvidia website (as I can see you are using the proprietary nvidia video driver). I'm closing this bug as INVALID, as from the interface point-of-view it is not a bug. Thanks for your report.