[nvidia] Wrong dpi in hardy when second monitor is disabled using twinview

Bug #206984 reported by Matti Laakso
4
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.24 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xorg

Xorg in Hardy beta seems to use wrong resolution (DPI) when two monitors are connected, but one of them is disabled. This results in e.g. wrong aspect ratio of videos in totem (see https://bugs.launchpad.net/ubuntu/+source/totem/+bug/198054). I think this bug is the same as here (status invalid): https://bugs.launchpad.net/ubuntu/+source/totem/+bug/38946.

When one monitor is disabled, xdpyinfo shows

screen #0:
  dimensions: 1920x1200 pixels (1049x331 millimeters)
  resolution: 46x92 dots per inch

which is obviously wrong. With both monitors enabled

screen #0:
  dimensions: 3840x1200 pixels (1049x331 millimeters)
  resolution: 93x92 dots per inch

and everything works correctly.

Also, Xorg.0.log has a line

(--) NVIDIA(0): DPI set to (93, 92); computed from "UseEdidDpi" X config

Note that I'm using NVidia drivers (171.06 beta) with twinview enabled. Prior to upgrading to hardy this issue did not exist, so I don't think that this is an NVidia bug.

Revision history for this message
Matti Laakso (matti-laakso) wrote :
Revision history for this message
Matti Laakso (matti-laakso) wrote :
Revision history for this message
Bryce Harrington (bryce) wrote :

Sounds a lot like a twinview bug. Does it still occur when you're not using twinview?

Changed in xorg-server:
status: New → Incomplete
Revision history for this message
Matti Laakso (matti-laakso) wrote :

Same thing happens without TwinView. I removed the MetaModes and TwinView lines and added line

Virtual 3840 1200

in the SubSection "Display" of Section "Screen". Again, with only first monitor enabled the DPI is incorrect and with both monitors enabled it is correct.

Revision history for this message
Matti Laakso (matti-laakso) wrote :
Revision history for this message
Duane Hinnen (duanedesign) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Revision history for this message
Matti Laakso (matti-laakso) wrote :

The above patch is included in Intrepid, i.e., it is fixed.

Changed in linux-restricted-modules-2.6.24:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.