Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1354148 - Can only display on monitor attached to Thinkpad dock if present at boot.
Summary: Can only display on monitor attached to Thinkpad dock if present at boot.
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 23
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2016-07-10 04:08 UTC by Josh Berkus
Modified: 2016-12-20 21:09 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-12-20 21:09:45 UTC

Attachments (Terms of Use)

Description Josh Berkus 2016-07-10 04:08:56 UTC
Description of problem:

Fedora 23 on Thinkpad X1 can only recognize a monitor attached to the dock if the monitor was present at boot time.  This may present an opportunity for analysis of dock-monitor issues because of its reproduceability.

Version-Release number of selected component (if applicable):


How reproducible:



- Thinkpad X1 Carbon, 2nd generation
- OneLink Pro Dock
- ASUS external monitor attached via DVI


Exhibiting the issue:

1. Boot Thinkpad while not attached to the dock.
2. Plug Thinkpad into the dock
3. Fedora will not see the monitor.  xrandr displays only the built-in laptop monitor.  There is no way to get it to acknowledge the monitor except by restarting X.

Good behavior:

1. Boot Thinkpad while attached to the dock.
2. Fedora sees monitor.
3. Detach Thinkpad from the dock.
4. Use it for a while.
5. Re-attach it to the dock
6. Select system configuration
7. Fedora notices the monitor and adds the display

Note that there are no issues with attaching/detaching an external HDMI monitor; this appears to be an issue exclusively with the dock.

I'm posting this issue for the following reasons:

* So other Thinkpad users will see it and see the workaround;
* Since the behavior is so consistent, there maybe data I can collect to troubleshoot it.

Comment 1 Fedora End Of Life 2016-11-25 09:24:53 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
of '23'.

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 23 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.

Comment 2 Fedora End Of Life 2016-12-20 21:09:45 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.

Note You need to log in before you can comment on or make changes to this bug.