On Mon, 25 Jan 2016 12:55:48 -0500
John Maheu <maheujm1(a)gmail.com> wrote:
ALT-F2 and "r" did not work.
On Mon, Jan 25, 2016 at 11:46 AM, Greg Woods <woods(a)ucar.edu> wrote:
> On Mon, Jan 25, 2016 at 7:34 AM, John Maheu <maheujm1(a)gmail.com>
>> I need to reboot to get things working again.
> You can also hit ALT-F2 to get a command window, and type "r". This
> restarts gnome-shell. This always works when I see this and doesn't
> require you to close any windows, log out, or reboot.
> I'd love to know why this happens, but it's infrequent enough that
> I just do the "r" when it does.
> users mailing list
> To unsubscribe or change subscription options:
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
If the keyboard is working at all, you should be able to use the magic
It's possible that there is a complete kernel panic, and nothing is
running, so the keyboard and mouse are unavailable. The fact that the
mouse pointer moves and music continues to play makes this unlikely.
That couldn't happen unless instructions were being processed by the
CPU. What if you unplug and plug in the mouse? Does it start working
Did you try Ctrl-Alt-F2 to reach a virtual console? When in X, the
virtual consoles are only reachable via the Ctrl-Alt-F2 version. Once
you are in a virtual console, you can look at the X logs, examine
journalctl -r or check processes that are suspended. You can even kill
the X server, and restart it if you have to.
If you get no joy, try a different kernel, or downgrade X to an earlier
version. It is likely that either the video driver or the X version is
having a race condition, and locking up. I use the radeon driver on an
older amd video card and have no issues at all, so it might be that
your card is newer and not as well supported.
If all else fails, search at https://bugzilla.redhat.com/
for bugs that
have your problem (say 'X freeze' or 'radeon'), and add your comments,
and check for workarounds, or open a new bug describing your problem.
Open it against X, even though it could be other things.