Bug 1460782 - Dual-monitor arrangement and primary monitor change when undocking and docking laptop
Dual-monitor arrangement and primary monitor change when undocking and dockin...
Status: NEW
Product: Fedora
Classification: Fedora
Component: gnome-shell (Show other bugs)
25
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Owen Taylor
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-12 13:31 EDT by Gary Case
Modified: 2017-06-12 13:31 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gary Case 2017-06-12 13:31:35 EDT
Description of problem:
I'm running Fedora 25 on a Lenovo ThinkPad T460s. I have it docked in a ThinkPad Ultra Dock which is connected via DisplayPort to an HP Compaq LA2206x monitor. 

When I undock and then dock my laptop, the video layout may reset. I want to have an over/under setup with the external monitor appearing above my laptop, and the external monitor should be the primary. I can set that up and it functions just fine until I undock. When I dock, the layout may change and the primary monitor may also change. 

Version-Release number of selected component (if applicable):
gnome-shell 3.22.3-1.fc25

How reproducible:
Almost every time

Steps to Reproduce:
1. Set up desired monitor layout (external monitor above the laptop monitor, set external monitor as primary)
2. Undock the laptop and do some work away from the desk
3. Dock the laptop 

Actual results:
Screen layout changes to side-by-side and the primary may or may not switch back to the laptop screen.

Expected results:
Restore the previously set up docked configuration when docking the laptop.

Additional info:

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