Description of problem: I set the resolution of my screen to 1920x1080 (in the MCC) which is supported by my screen: http://www.iiyama.com/be_fr/produits/prolite-e2475hds-1/ The resolution seems to be correct in kdm but when the desktop is displayed, another resolution is used: 1680x1050 Then, xdpyinfo reports the wrong resolution: [gouessej@localhost ~]$ xdpyinfo | grep dimensions dimensions: 1920x1080 pixels (508x285 millimeters) I have to "set" the wrong resolution and to set the desired resolution to fix that: [gouessej@localhost ~]$ xrandr --size 1680x1050 [gouessej@localhost ~]$ xdpyinfo | grep dimensions dimensions: 1680x1050 pixels (508x285 millimeters) [gouessej@localhost ~]$ xrandr --size 1920x1080 When it is done, xdpyinfo still reports the wrong dimensions according to the specifications: [gouessej@localhost ~]$ xdpyinfo | grep dimensions dimensions: 1920x1080 pixels (508x285 millimeters) whereas xrand -q shows the expected dimensions: [gouessej@localhost ~]$ xrandr -q Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 32767 x 32767 VGA1 disconnected (normal left inverted right x axis y axis) DVI1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.0*+ 1600x1200 60.0 1680x1050 59.9 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1152x864 75.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 75.0 72.8 66.7 60.0 720x400 70.1 VIRTUAL1 disconnected (normal left inverted right x axis y axis) Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
CC: (none) => gouessej
Hardware: i586 => x86_64
>The resolution seems to be correct in kdm but when the desktop is displayed, > another resolution is used: 1680x1050 All desktop ? also same with other dm ?
I haven't tried with other dm yet. My DVI extension card was almost completely KO. When I removed it, this bug became no longer reproducible. xrandr still reports wrong physical screen size values in millimeters sometimes but the right resolution is used.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD