| Summary: | xdpyinfo returns wrong screen size | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Elmar Stellnberger <estellnb> | ||||||
| Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||
| Severity: | normal | ||||||||
| Priority: | medium | CC: | hramrach, mcepl, zaitcev | ||||||
| Version: | 7.4 (2008.09) | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Elmar Stellnberger
2009-12-13 02:08:31 UTC
Please fix this as soon as possible because otherwise many programs like koffice & kword will not run in Xinerama mode. This is handled in the Xserver. The driver just passes along the EDID. Why does it work then with the radeonhd driver? Created attachment 32080 [details]
Xorg.1.log
Created attachment 32225 [details]
/var/log/Xorg.0.log
*** Bug 20409 has been marked as a duplicate of this bug. *** *** Bug 20409 has been marked as a duplicate of this bug. *** (In reply to comment #3) > Why does it work then with the radeonhd driver? And Intel: https://bugzilla.redhat.com/show_bug.cgi?id=540783#c17 I have two Intel systems, they do the same thing: #1 built-in LCD: [ 47.044] (II) intel(0): EDID Version: 1.3 [ 47.044] (II) intel(0): Digital Display Input [ 47.044] (II) intel(0): Max Image Size [cm]: horiz.: 30 vert.: 19 [ 47.044] (II) intel(0): Gamma: 2.20 ...................... [ 47.044] (II) intel(0): Supported detailed timing: [ 47.044] (II) intel(0): clock: 101.6 MHz Image Size: 303 x 190 mm ...................... [ 47.980] (II) GLX: Initialized DRI2 GL provider for screen 0 [ 47.980] (II) intel(0): Setting screen physical size to 381 x 238 303x190 is correct size, 381x238 is wrong (but it is reported by dpyinfo). #2 monitor at DP: [ 77.031] (II) intel(0): EDID Version: 1.4 [ 77.031] (II) intel(0): Digital Display Input [ 77.031] (II) intel(0): 8 bits per channel [ 77.031] (II) intel(0): Digital interface is DisplayPort [ 77.031] (II) intel(0): Max Image Size [cm]: horiz.: 47 vert.: 30 ...................... [ 77.032] (II) intel(0): Supported detailed timing: [ 77.032] (II) intel(0): clock: 146.2 MHz Image Size: 470 x 300 mm ...................... [ 77.259] (II) GLX: Initialized DRI2 GL provider for screen 0 [ 77.260] (II) intel(0): Setting screen physical size to 444 x 277 470x300 is correct, 444x277 is wrong (but gets into dpyinfo). bug was not observed for long and is consequently closed. However pls. consider another issue for the future: the DPI value of different Xinerama screens may differ enormously though to my knowledge there is no function yet to return a DPI value on per xinerama-screen basis rather than for a whole 'screen' (I am talking about the default functions XDisplayWidth/Height[MM] and missing corresponding information for the xinerama extension: no such member in xcb_xinerama_screen_info_t). I will close this now as the issue described above is different from the initial issue. The problem has probably not been ever fixed. As has been pointed out the whole screen DPI is not immensely useful in non-uniform multi-display configurations. XRandr returns DPI for each display separately. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.