When attempting to login to a Wayland session, I am either: (When booted with nomodeset): dumped back to the GDM login screen. (When booted without nomodeset): logged into an X session that experiences incredible lag. The repaint time is in the seconds when this happens. Also, perhaps related, the mouse graphic rendered on the screen is stuck in the top left corner. If I move my physical mouse, I see components highlight on the screen and I am able to click on things with this ghost mouse.
Created attachment 1211577 [details] journalctl output This journalctl output is from the system booted with nomodeset. A few minutes after booting I attempt to start a Wayland session and am booted back to the GDM login screen.
Created attachment 1211578 [details] lspci
Created attachment 1211579 [details] rpm -qa
The machine in question has an i5-6600k and a GTX 1080. I am booting the latest Fedora 25 beta image using nouveau and not the nvidia binary driver. I'm not sure how to capture meaningful logs during the gnome lag. I'll upload whatever output you'd like.
I tried to run the Fedora 25 beta live CD and faced similar issues. The refresh rate was more like one frame per second. I'm using two 144hz G-sync displays with 2560x1440 resolution each (couldn't verify if nouveau negotiated the 144hz or just 60hz) on an Geforce GTX 1070. The visual mouse cursor got stuck in the top left of the screen, too, but moving the invisible pointer between displays made the visible one switch displays, too, but still got stuck in the top left.
Since you mentioned it, I too am using a 144 Hz G-sync display.
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.