Hide Forgot
Created attachment 1223097 [details] 0. Photo of laptop on dock Description of problem: My setup: a Thinkpad T440s laptop, on a docking station (photo 0), on which 2 external screens are connected (one using VGA, one using DVI). Using GNOME control panel for screens, my Fedora desktop is extended to both monitors (photo 1). With wayland, I always observe an extremely strange behavior when I un-dock and re-dock my laptop: 1) I will always lose my session, and have to log in again (photo 2) 2) After logging in, I won't have an extended desktop on the dual screen configuration (as before un-docking), but instead have something that *looks like* a cloned screens configuration with the same content on both external displays (photo 3). However, when opening the GNOME Control panel for screens, it says that I am still using extended desktop, not cloned screens (photo 4). From there, the only way to reach again extended desktop is to disable one of the screens and re-enable it. This problem does not happen when using X11, with which I get my extended desktop back when re-docking, and without losing any session. My apologies for the very bad quality of the photos... Version-Release number of selected component (if applicable): Laptop: Thinkpad T440s $ uname -a Linux ebousse-isis-tuwien-ac-at 4.8.7-300.fc25.x86_64 #1 SMP Fri Nov 11 14:02:22 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux (problem also present when running 4.8.8) $ dnf list installed | grep wayland gnome-session-wayland-session.x86_64 3.22.1-2.fc25 @@commandline ibus-wayland.x86_64 1.5.14-3.fc25 @@commandline kf5-kwayland.x86_64 5.27.0-1.fc25 @@commandline libwayland-client.i686 1.12.0-1.fc25 @@commandline libwayland-client.x86_64 1.12.0-1.fc25 @@commandline libwayland-cursor.x86_64 1.12.0-1.fc25 @@commandline libwayland-server.i686 1.12.0-1.fc25 @@commandline libwayland-server.x86_64 1.12.0-1.fc25 @@commandline mesa-libwayland-egl.x86_64 12.0.3-3.fc25 @@commandline xorg-x11-server-Xwayland.x86_64 1.19.0-0.8.rc2.fc25 @updates $ lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) $ lscpu | grep modèle Nom de modèle : Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz $ dnf list installed | grep intel intel-graphics-update-tool.x86_64 2.0.2-24.intel20162 @@commandline libva-intel-driver.i686 1.7.2-1.fc25 @@commandline libva-intel-driver.x86_64 1.7.2-1.fc25 @@commandline xorg-x11-drv-intel.x86_64 2.99.917-26.20160929.fc25 @@commandline How reproducible: Always Steps to Reproduce: 1. Set up laptop on dock with 2 external displays 2. Open a GNOME Wayland session, 3. Set up an extended desktop on both monitors 4. Undock laptop 5. Re-dock laptop Actual results: - Session is lost - After logging in again, strange "cloned screens" state (see description) Expected results: - (as observed with X11) session not lost, extended desktop still present
Created attachment 1223098 [details] 1. Initial extended desktop configuration
Created attachment 1223100 [details] 2. Session lost after re-docking
Created attachment 1223101 [details] 3. Cloned screens after re-docking
Created attachment 1223102 [details] 4. Gnome control panel showing "extended desktop" and not cloned screens
Created attachment 1223103 [details] 4bis. Close up of previous picture
With an up-to-date system, I still lose my session when I re-dock my laptop, but the cloned screen behavior seems gone. My packages versions: $ dnf list installed | grep wayland gnome-session-wayland-session.x86_64 3.22.2-3.fc25 @updates ibus-wayland.x86_64 1.5.14-5.fc25 @updates kf5-kwayland.x86_64 5.29.0-1.fc25 @updates libwayland-client.i686 1.12.0-1.fc25 @@commandline libwayland-client.x86_64 1.12.0-1.fc25 @@commandline libwayland-cursor.x86_64 1.12.0-1.fc25 @@commandline libwayland-server.i686 1.12.0-1.fc25 @@commandline libwayland-server.x86_64 1.12.0-1.fc25 @@commandline mesa-libwayland-egl.x86_64 13.0.3-1.fc25 @updates qt5-qtwayland.x86_64 5.7.1-2.fc25 @updates xorg-x11-server-Xwayland.x86_64 1.19.1-2.fc25 @updates $ dnf list installed | grep intel libva-intel-driver.i686 1.7.3-1.fc25 @rpmfusion-free-updates libva-intel-driver.x86_64 1.7.3-1.fc25 @rpmfusion-free-updates xorg-x11-drv-intel.x86_64 2.99.917-26.20160929.fc25 @@commandline
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.
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.