xrandr reports slightly different (less accurate) output dimensions under XMir

Bug #1216228 reported by Daniel van Vugt on 2013-08-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Invalid
Low
Unassigned
libdrm (Ubuntu)
Undecided
Unassigned

Bug Description

XMIR-0 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 280mm x 160mm
vs
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 277mm x 156mm

The latter (native X) is more accurate. Is XMir/Mir rounding to centimetres?

tags: added: multimonitor
Changed in mir:
importance: Undecided → Low
Changed in xmir:
status: New → Confirmed
kevin gunn (kgunn72) on 2013-12-06
Changed in mir:
status: New → Invalid
Daniel van Vugt (vanvugt) wrote :

AFAIK, the numbers are copied directly from Mir structures. So it's Mir, not XMir.

Changed in mir:
status: Invalid → Triaged
Changed in xmir:
status: Confirmed → Invalid
Daniel van Vugt (vanvugt) wrote :

These seem to be the numbers coming straight out of libdrm.

Changed in mir:
status: Triaged → Invalid
Daniel van Vugt (vanvugt) wrote :

It seems both answers are correct, depending on where you look:

$ edid-decode /sys/class/drm/card0-HDMI-A-1/edid
...
Maximum image size: 52 cm x 33 cm
...
Detailed mode: Clock 154.000 MHz, 519 mm x 324 mm

Though I suggest we should be using the latter.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers