Created attachment 130047 [details] pacman_q output, ignore kernel 3.9 here! Hello! Since Kernel >= 4.10.1 I cannot switch from Wayland based GNOME-Shell to a FBDEV based TTY with Ctrl+Alt+Function-Key. This worked till Kernel <= 4.9. The screen freezes and shows the GNOME-Shell as it was exactly during the key-press. I cannot see any error or warning in 'dmesg' nor 'journalctl -rb' but hitting Ctrl+Alt+F2 (in most cases GNOME should be running on TTY2, GDM on TTY1) will bring back the running GNOME-Shell. Looking at the output of 'journalctl -rb' I noticed that systemd actually does launch getty on the selected TTY, so I tried a blind login and it worked. So it is only a graphical issue. While using the GNOME-Shell on X11 everything still works as usual, returning back to Kernel 4.9.11 and everything works as usual also with Wayland. I noticed some changes to FBDEV and Intel ('fbdev helper ops') in 4.10, but they sound not massive or Wayland related. I'm using a ThinkPad X220 with a Sandy-Bridge i7, therefore it is using a Intel HD3000. Distribution is Archlinux and I'm currently running a self compiled '4.10.1'. Historicall background: For long times switching from Wayland to an TTY wasn't possible if the FBDEV in the TTY was activley used i.e. by fbi(da) to show a png/jpeg/whatever. But I didn't cared much, because initally nobody opens fbi(da) and I was able first to switch to an other TTY without a running fbi(da) and then to the TTY with a running fbi(da). Same for mplayer and so on. Side notes: I initally opend this bug on bugzilla.kernel.org, which is the wrong place? https://bugzilla.kernel.org/show_bug.cgi?id=194737 Furthermore I noticed this one: https://bugs.freedesktop.org/show_bug.cgi?id=99841 But it is about X11, not Wayland. X11 works fine with kernel >= 4.10.1 here. Thank you
Created attachment 130048 [details] .config of kernel 4.10.1
Created attachment 130049 [details] dmesg output
Created attachment 130050 [details] journalctl -rb output
I also have the same problem. I am using the i915 driver and couldn't switch to a terminal TTY (due to screen freeze) after upgrading to Linux 4.10.1. I've since downgraded to 4.9.11 and I'm able to switch again.
(In reply to Peter Weber from comment #2) > Created attachment 130049 [details] > dmesg output Please add drm.debug=14 module parameter for debug output in the dmesg.
Created attachment 130132 [details] boot with drm.debug=14 in a dockingstation, with a secondary display Hello! This is a boot in a docking-station, with and attached secondary display. The describe issues occurs. Steps to reproduce: 1.) Boot and login on GDM into GNOME, with Wayland 2.) Shortcut: Ctrl+Alt+F3, screen freezes // this should open TTY2 3.) Shortcut: Ctrl+Alt+F4, screen still freezed // this should open TT3 4.) Shortcut: Ctrl+Alt+F2, back in GNOME and screen is unfrozen
Created attachment 130133 [details] boot with drm.debug=14 without a dockingstation, switching VTs works! Hello! I figured this only out during creating the dmesg with "drm.debug=14". When the laptop is not docked in, it is possible to switch between the different TTYs! Steps to reproduce: 1.) Boot and login on GDM into GNOME, with Wayland 2.) Shortcut: Ctrl+Alt+F3, successfull switch to TTY2 3.) Shortcut: Ctrl+Alt+F4 or Alt+F4, successfull switch to TTY4 4.) Open an image with $ fbi somenicepicture.png // shows image on screen 5.) Shortcut: Ctrl+Alt+F3 or Alt+F3, successfull switch to TTY3 6.) Shortcut: Ctrl+Alt+F2 or Alt+F2, screen freezes // yep, it also freezes 7.) Shortcut: Ctrl+Alt+F4, successfull switch to TTY4 8.) Quit fbi 9.) Shortcut: Ctrl+Alt+F2 or Alt+F2, back in GNOME So the bug is possibly releated to the docking-station and/or the second monitor. What is new here, is, that since kernel 4.10 switching back to Wayland while an image is open in 'fbi' is not possible. --------------------------------------------------------------------------------- I'm aware of an older issue, which wasn't important till now. I'm familiar with the situation, that switching from a running session in X11 (!) to an VT with a running 'fbi' wasn't possible. --------------------------------------------------------------------------------- Thank you
Hello! At work I'm using a T420 (also SandyBridge) and it shows the same behaviour.
This is fixed either by LINUX "4.10.13" or GNOME "3.24". I can' tell which one or both, but it is gone :)
It happens for me on intel HD 4000 with external monitor after upgrade to Ubuntu 17.04 (kernel 4.10.x, gdm/gnome-shell 3.24). And it usually happens for me on X11 session too, it's not just wayland. I will try newer kenel version.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.