But Ctrl+ Alt+ F3 did switch to a text term, Ctrl+ Alt+ F1 brought back the X windows session. Not even moving the cursor onto another window, when I have focus-follows-mouse, changes the window frame highlighting. The PrtScn made a popup saying I could drag a rectangle (but not) or hit ESC (works). In my case, just minutes ago, everything was hung except the mouse moved the cursor, but the mouse did no more. Now everything's back to normal, no reboot or loss of anything involved. I could then switch back to the first workspace, kill Chromium, which I had by then figured had crashed and was hogging all keyboard and mouse events. This did switch workspaces, and doing so somehow unhitched whatever was blocking mouse and keyboard actions. Not yet mentioned but might work in some cases - try CTRL+ ALT+ RIGHTARROW or LEFTARROW. "Call oom_kill, which kills a process to alleviate an O ut O f M emory condition", which (at least for me) often kills the program that is causing the issue, as it is the largest RAM consuming process running at the time. then assuming MagicSysRq support is compiled into the kernel (From ), on a QWERTY keyboard (alternatives for the below f are provided in the aforementioned article), one can try: Switch to another virtual console ( Ctrl+ Alt+any one of F1-6), to initiate a pkill (or similar, as detailed above).Use keyboard/mouse to A) Run the Ctrl+ Alt+ * option above, B) Navigate to a utility that can be used to terminate the offending program, C) Launch a terminal to initiate a pkill (or similar, as detailed above).Adding one more possible solution to the mix, and (apart from the accepted answer) one of the least destructive of the answers so far.
0 kommentar(er)
