Description of problem: Installed any nightly build following April 9th, 2017 Logging in with Wayland results in the actions Welcome message is presented Error message is presented User is bounced off logon screen is presented. Version-Release number of selected component (if applicable): How reproducible: As above Steps to Reproduce: 1. 2. 3. Actual results: Expected results: To continue to setup and use Fedora nightly Additional info: Gnome.org version (gear wheel selected) works. I can log into Fedora 26Nightly A related issue (perhaps) I will file against X11. The X11 keyboards (I use US keyboard and CA (Canada French). The lower case space character (space bar) is a deadkey. Can only enter space characters while holding the shift key.
Problem has been present since alpha release + 1 day (april 7). Now 12 days later. Would like to continue to test F26 Wayland.
I just installed 26 on my Thinkpad T440, and see this consistently. Initial setup screen opens, I confirm first two (I believe) screens, and then it crashes. It has never not crashed.
Sorry; "it" as in the session/shell, per original report.
This is happening with the nightly build of Fedora26. My nightly build is dated MAY 15, 2017 as Fedora-Workstation-netinst-x86_64-26-20170515.n.0.iso
Isn't this a duplicate of #1443206?
It is a superset of 1443206. With Adam's bug report, he mentioned that the problem occurred once. With this report, the crash is in a loop. Log in Welcome screeen crash Login prompt The crash can be avoided if the Welcome screen is not responded to. I then can open firefox and continue as one would expect. Please check the Welcome screen exit status
(In reply to Leslie Satenstein from comment #6) > It is a superset of 1443206. With Adam's bug report, he mentioned that the > > Log in > Welcome screeen > crash > Login prompt Until initial setup is not completed, it will be presented again on next login. Try to login using "GNOME on Xorg" (click on the wheel on the login screen). Complete the initial setup. Logout. Login using GNOME.
*** This bug has been marked as a duplicate of bug 1443206 ***