On Fri, Jan 15, 2016 at 7:27 AM, <meino.cra...@gmx.de> wrote: > > But once touching the console, where X11 should still be > running and which is now occupied by the deep dark unholy > "nothing" ;) I got trapped -- no way out and a bindly > keyed login followed by a reboot has nothing as result. >
What is your kernel configuration around the console? Are you using any binary modules (cough...nvidia...)? KMS? Framebuffer? What hardware is this? In general this shouldn't happen, and I've mainly seen it on tainted kernels, or in the old days of X11 running as root. With mainline kernel drivers and KMS things have been pretty reliable for me. If you are using nvidia-drivers, you're probably at their mercy. If you are running an untainted kernel and KMS and can get enough info to the linux devs they would almost certainly consider this a valid bug. It shouldn't be possible for userspace to break the console in the new design. -- Rich
