Bug 1372995 - System freezing when arranging integrated display below external monitors
Summary: System freezing when arranging integrated display below external monitors
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-modesetting
Version: 24
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-04 15:09 UTC by Patrick Lesky
Modified: 2017-08-08 17:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 17:00:12 UTC
Type: Bug


Attachments (Terms of Use)

Description Patrick Lesky 2016-09-04 15:09:24 UTC
Description of problem:

I'm running Fedora 24 (Kernel 4.7.2-201.fc24.x86_64) on my new ThinkPad T460p (Intel Core i7-6700HQ CPU, Intel HD Graphics 530 (Skylake GT2)) in a multi monitor setup with two external monitors (both 2560x1440@60Hz, DP 1.2 via UltraDock) and the integrated display (2560x1440@60Hz). Problems arise when arranging the monitors via Settings App in a way that they are not all in one horizontal line, e.g. the integrated display set a little below the others. For instance:

------------- ------------- 
|   Ext1    | |   Ext2    |
|           | |           | ---------
|           | |           | |  Int  |
------------- ------------- |       |
                            ---------

This setting causes the system to freeze on the next login. The only option left is to hard reboot by pressing the power button for a few seconds.


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


How reproducible:
Arrange the displays as discribed and reboot. Right after the next login the system will freeze.

Steps to Reproduce:
1. Arange the displays as described
2. Reboot
3. Login to Gnome

Actual results:
System freezing

Expected results:
Everything working fine

Additional info:
If edit ~/.config/monitors.xml and set the y-axis value of the integrated display to 0 I can login to the Gnome session again without any issues.

This is my first bug report. So please tell me if you need further information.

Comment 1 Fedora End Of Life 2017-07-25 22:49:21 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 2017-08-08 17:00:12 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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
bug.

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.