Description of problem: When trying to to switch from gnome-shell or gdm (login window) to a console (tty2), nothing happens and then the display is no longer responsive and system appears to be completely frozen. Remote access is still functional, but even a reboot -f will fail. Version-Release number of selected component (if applicable): 4.0.0-0.rc4.git2.1.fc22.x86_64 This has been happening with 3.19 kernels as well, it could be related to gdm+Wayland. Reboot at first instance of login window, there's a lot of display flicker. How reproducible: Always Steps to Reproduce: 1. Boot, login, then either logout and switch to console or just switch to console from gnome-shell. Actual results: Crash/hang. Expected results: No crash or hang. Additional info:
Created attachment 1005079 [details] dmesg Includes drm.debug=0x06
Created attachment 1005080 [details] journal journalctl -b -l -o short-monotonic
re: comment 1, Fn+F2+ctrl+alt was pressed somewhere around 200-203s. I have no idea what this is because nothing on the local computer was working... [ 205.190928] f22m.localdomain gdm-password][2718]: pam_unix(gdm-password:auth): conversation failed [ 205.191832] f22m.localdomain gdm-password][2718]: pam_unix(gdm-password:auth): auth could not identify password for [chris] [ 205.192653] f22m.localdomain gdm-password][2718]: gkr-pam: no password is available for user [ 205.192861] f22m.localdomain unknown[2718]: <audit-1100> pid=2718 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=? acct="chris" exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=? res=failed' [ 205.193100] f22m.localdomain unknown[2718]: <audit-1112> pid=2718 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='uid=1000 exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=? res=failed'
This problem doesn't happen with 3.18.9 kernel. I also get this back trace with normal reboot attempts, which then makes the system unrecoverable and I have to force power off.
*** This bug has been marked as a duplicate of bug 1203852 ***