Ask Your Question

Fedora Unresponsive After Timeout

asked 2018-08-21 15:03:42 -0600

iliffe gravatar image

updated 2018-08-23 13:18:26 -0600

Fedora 27; most recent updates installed; Gnome desktop

After a timeout, the keyboard and mouse locked out and are unresponsive so not possible to recover desktop that was running. Need to do a hard reboot to get back on computer.

This happens even when the security settings are set to "screen lock off".

The problem is obviously that if I take a phone call and if I forget to hit <shift> every few minutes I lose all my current unsaved work.

Sorry for the delay in responding to the answer #1, had to find the time to let it time out. I was unable to recover the screen, with either a command line or the GUI. The mouse and keyboard are locked out at this point so the only option is a hardware reset. Note that I have Gnome set to never time out so this should never occur.

Also, when I rebooted, there was a note flashed on the Gnome desktop for a few seconds, something about "We're sorry that boot image ...." Didn't have time to read the rest and the actual boot image name was truncated. FYI, the Gnome version is 3.26.2 running on an AMD Ryzen 3-2200g with AMD Raven graphics.

edit retag flag offensive close merge delete


No, it's just the way Gnome comes. I selected the photo of the barn and the mountains as the background from the available choices. Sure I can show the startup but can you clarify just exactly what you need? The tail end of dmesg doesn't seem to have anything relevant.

One thing I have noticed is that during boot EVERY message is repeated twice but I can't figure a way to capture that. I am wondering if (1) there is a race condition (which would also explain the problems with Gnome failing to start sometimes) and (2) do I really have two systems running under the hypervisor.

iliffe gravatar imageiliffe ( 2018-08-25 23:27:22 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2018-08-21 16:57:12 -0600

wallyk gravatar image

updated 2018-08-21 16:58:12 -0600

That "lockup" is likely a device misbehaving.

To gather clues, open a console (terminal) and type dmesg. The last few screens (100-200 lines) probably have messages from a complaining device driver.

Once the GUI has "locked up", try opening a console session by typing Ctrl-Alt-F3. (To go back to the GUI, Ctrl-Alt-F1 or Ctrl-Alt-F2.) If the new session appears, login and type dmesg and amend the result to your question.

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2018-08-21 15:03:42 -0600

Seen: 78 times

Last updated: Aug 23 '18