Hide Forgot
Description of problem: The Generic video multihead test, as described in https://fedoraproject.org/wiki/QA:Testcase_generic_video_multihead failed at my place. Version-Release number of selected component (if applicable): Fedora 15 GNOME 3 Test Day x86_64 LiveCD http://adamwill.fedorapeople.org/gnome3-test-20110421/gnome-20110419-x86_64.iso How reproducible: always Steps to Reproduce: 1. Test #3: Disconnect and then re-connect one or more displays. Actual results: Automatic detection did'nt work at all. Neither on disconnect, nor on connect, neither on VGA, nor on HDMI. However, running 'xrandr' fixed the problem every time. Expected results: Both X and the graphical environment should cope smoothly with displays being disconnected and reconnected while the system is running. Additional info: Hardware: http://www.smolts.org/client/show/pub_f58d8d11-6314-4033-b17e-063ec6f6d414 HD 3200 (780G), Sony monitor 1280x1024 (VGA), Samsung monitor 1920x1200 (HDMI)
I have the same problem as described above. Running an uptodate patched Fedora 15 beta on my Lenovo Thinkpad X61s. Connecting my Samsung 1920x1080 through the VGA port always results in a flickering/distorted screen. xrandr output seems fine: Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 LVDS1 connected (normal left inverted right x axis y axis) 1024x768 50.0 + 60.0 40.0 800x600 60.3 56.2 640x480 60.0 59.9 VGA1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 1600x1200 60.0 1680x1050 60.0 1280x1024 75.0 60.0 1440x900 75.0 59.9 1280x960 60.0 1280x800 59.8 1152x864 75.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 720x400 70.1 running "xrandr" does NOT fix the problem running "xrandr -s 1920x1080" does NOT fix the problem running "xrandr -s 1680x1050; sleep 2 ; xrandr -s 1920x1080" fixes the problem Without the "sleep 2" the display seems fine but GNOME 3 still believes the resolution is set to 1680x1050 resulting in all kinds of graphical oddities. I will attach /var/log/Xorg.0.log of my latest test session in hope that this will be of some help. I will gladly provide more information if needed if this helps this bug to get fixed. IMHO, this is a showstopper bug for auf F15 release! Regards, Markus
Created attachment 494089 [details] X server logfile
Subject should probably read something like "display hot plugging not working"
As a first approximation, moving this to xorg-x11-server for further triage
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please, reporter, add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
> Please, reporter, add drm.debug=0x04 to the kernel command line, restart > computer, and attach OK, I did the following: * yum update --skip-broken * added the kernel parameter * rebootet maschine * logged in * attached samsung full hd display * ... screen is distorted ... * removed external display collected the requested information: > * your X server config file (/etc/X11/xorg.conf, if available), aang->ls -la /etc/X11/xorg.conf ls: cannot access /etc/X11/xorg.conf: No such file or directory > * X server log file (/var/log/Xorg.*.log) > * output of the dmesg command, and > * system log (/var/log/messages) see new attachments > to the bug report as individual uncompressed file attachments using the > bugzilla file attachment link above. > > We will review this issue again once you've had a chance to attach this > information. Please tell me, if I can provide any further information. Regards, Markus
Created attachment 495799 [details] new X server logfile
Created attachment 495800 [details] dmesg
Created attachment 495802 [details] /var/log/messages
Nicolas, could we get these information from you as well, please? Thank you in advance, Matěj
I have the same problem and I'm also running the Fedora 15 GNOME 3 Test Day x86_64 LiveCD: http://adamwill.fedorapeople.org/gnome3-test-20110421/gnome-20110419-x86_64.iso My computer is an HP EliteBook 8530p: http://www.smolts.org/client/show/pub_1428f23c-6b12-4f77-a570-c8d6e5a52748 The attached monitor is an 24" Dell LCD connected via DVI port of the docking station. I'll also attach the information you've requested.
Created attachment 496816 [details] Xorg.0.log
Created attachment 496817 [details] dmesg
Created attachment 496818 [details] /var/log/messages
I encountered the same bug during F-16 Radeon test day: http://fedoraproject.org/wiki/Test_Day:2011-09-07_Radeon This is really annoying if the panel is on the external screen and you disconnect the laptop from the docking station. It is almost impossible to open up a terminal to execute 'xrandr' and force the screen readjust.
The core multihead logic in the server is fine. This is properly an intel bug. Tadej, please file a new bug for your issue.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.