Red Hat Bugzilla – Bug 995786
[xorg-x11-drv-ati] internal display not disabled when notebook booted in docking station with lid closed
Last modified: 2015-06-29 08:16:12 EDT
Description of problem:
After switching on and booting a Lenovo ThinkPad T400 connected to a docking station, the (external) monitor only shows a blank grey screen.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Switch on ThinkPad T400.
2. Boot Fedora 20-rawhide
No login panel after booting into graphical mode.
Login panel appears and allows users to log in.
1. The login panel is actually displayed on the internal display which becomes apparent after opening the notebook lid. X sets up the internal display as the primary one and the external one as the secondary one instead of disabling the internal display altogether.
2. Fedora 19 works as expected.
Created attachment 785330 [details]
Output of dmesg command.
Created attachment 785334 [details]
Created attachment 785335 [details]
Output of 'xrandr -q --verbose'
Created attachment 785490 [details]
Output of dmesg command for Fedora 19
Adding log files for Fedora 19 for which the monitor handling is correct.
Created attachment 785492 [details]
Xorg.0.log for Fedora 19
Created attachment 785493 [details]
Output of 'xrandr -q --verbose' for Fedora 19
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.
More information and reason for this action is here:
same issue reported at https://bugzilla.redhat.com/show_bug.cgi?id=1012122
[with intel GPU]
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version'
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.
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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.