Red Hat Bugzilla – Bug 499563
xrandr -s 800x600 --dpi 96 fails on cirrus in kvm
Last modified: 2013-08-01 14:15:37 EDT
Created attachment 342794 [details] Example image with black boxes. Description of problem: When installing F11 in new qemu/kvm, there are blank (black) rectangles around. I think this has something with qemu's new feature, which can use bigger resolutions like 800x600. More about this new feature: http://fedoraproject.org/wiki/Features/VirtImprovedConsole Installer is now starting in 1024x768, but anaconda runs still at 800x600, so there are black boxes on my virtual screen. Even if I use virt-manager, virt-viewer or directly using vncviewer. Version-Release number of selected component (if applicable): Fedora 11-Preview qemu-0.10-16.fc11.i586 virt-viewer-0.0.3-4.fc11.i586 virt-manager-0.7.0-4.fc11.1.i386 How reproducible: always Steps to Reproduce: 1.try to install F11 in graphics mode in KVM or qemu. Actual results: see attachment Expected results: two choices: 1. anaconda running at 1024x768 and use whole screen 2. switch to 800x600 and run as up to now Additional info:
It seems pretty clear from this that the guest has a 1024x768 framebuffer but anaconda is occupying only 800x600. Very odd. Tentatively adding to the blocker list, since it may not be fixable after GA
*** Bug 499543 has been marked as a duplicate of this bug. ***
anaconda only ever runs at 800x600 as there are various things in our UI that rely on a fixed layout. This is on the always "will be looked at someday" list, but never actually gets there.
Could X on the install images be configured to only do 800x600?
We actually attempt to do an xrandr, but obviously don't fail if xrandr doesn't work for some reason. We don't want to run with a config file because that means we're hitting different code paths than the real system It seems that xrandr -s 800x600 --dpi 96 does not work with Cirrus, and so thus it stays at the 1024x768.
Ah, nice. Moving back to F11VirtTarget, then. Optimism ftw.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions). Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Same problem with F12-Beta installer. Please leave this bug open.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. 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 Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Same problem on f13 and f14. If nobody can fix this, please close this bug as wontfix.
Still an issue it seems. # xrandr -s 800x600 --dpi 96 xrandr: Failed to get size of gamma for output default That's inside an F17 guest on F17 host.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. 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 Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.