Bug 1375608 - Unable to set a certain monitor setup under Wayland
Summary: Unable to set a certain monitor setup under Wayland
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-13 14:10 UTC by Martin Bříza
Modified: 2017-12-12 10:13 UTC (History)
3 users (show)

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


Attachments (Terms of Use)
Monitor layout (45.22 KB, image/png)
2016-09-13 14:12 UTC, Martin Bříza
no flags Details

Description Martin Bříza 2016-09-13 14:10:07 UTC
Description of problem:
I'm not able to set my monitor setup to correspond to their physical layout. See the attachment or the xrandr output below. The actual pixel location of the screens don't matter, just their relative position.

xrandr output:
Screen 0: minimum 320 x 200, current 3840 x 2130, maximum 8192 x 8192
XWAYLAND0 connected 1920x1080+1920+429 510mm x 290mm
   1920x1080     59.96*+
XWAYLAND1 connected 1680x1050+240+0 470mm x 300mm
   1680x1050     59.85*+
XWAYLAND2 connected 1920x1080+0+1050 340mm x 190mm
   1920x1080     60.05*+


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

How reproducible:
Always

Steps to Reproduce:
1. Start a fresh session of GNOME under Wayland
2. Set the monitor layout as mentioned in the description of the bug

Actual results:
One of the screens is turned off in the process

Expected results:
All screens are on.

Additional info:
After locking the screen, waiting for the monitors to turn off and then unlocking, all screens are on again.

Comment 1 Martin Bříza 2016-09-13 14:12:38 UTC
Created attachment 1200505 [details]
Monitor layout

Comment 2 Fedora End Of Life 2017-11-16 19:21:28 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 3 Fedora End Of Life 2017-12-12 10:13:15 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.