Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Every now and then everything appears to lock up and I can't really do anything. I can move my mouse and it will reflect that on the screen but I can't really do anything else. Sitting long enough it is apparent the clock isn't updating. I can use Ctl-Alt-F1 but I don't really know what to do to make anything responsive. I am using gnome-shell. I don't know if anything similar would happen if I used Unity instead.

Edit: By switching to a text terminal and putting the computer to sleep and bringing it up back I was able to get the GUI terminal to be responsive. I'm still interested in why this could be happening and an easier way to bring it to be responsive after it happens.

Edit the dos: It appears after working with 11.10 for a while that the only time that this occurs is when I'm reading a pdf using evince. If I load evince from the terminal I get this always:

(evince:6963): GLib-GObject-WARNING **: g_object_set_valist: construct property "enable-gestures" for object `EvView' can't be set after construction

Could this have something to do with the computer locking up?

share|improve this question

closed as too localized by Mateo, Eric Carvalho, user68186, Raja, bcbc May 16 '13 at 19:11

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

I'm no longer able to check if answers to this question work - The computer in question is no more. – Dason Nov 18 '11 at 19:46

Try switching to a different tty (Ctrl-Alt-F1), login in, and then at the prompt type:

gnome-shell --display :0 --replace

Then switch back to the GUI (Ctrl-Alt-F7).

share|improve this answer

I had this happen after locking the screen, in the middle of the Oneiric upgrade. I fixed the problem, temporarily, by killing gnome-screensaver (oddly, its name was cut off in the pgrep output). I don't know if this will cause problems with gnome-screensaver. Since it will daemonize when run (in theory), you can just start it again.

share|improve this answer
I'll give this a try. Are you suggesting to kill gnome-screensaver until I need it or to kill it if everything locks up? – Dason Oct 22 '11 at 13:55
Kill it if things lock up, and then try to restart it. As this is an intermittent issue, if restarting it causes problems you can reboot instead; that should spawn a new "proper" instance of it. If you don't restart the process somehow, I think you could have problems with the screensaver not starting on time (or at all). – Kevin Oct 25 '11 at 3:32
This didn't end up working for me. – Dason Oct 27 '11 at 23:20
Does rebooting fix the issue? – Kevin Oct 29 '11 at 1:53
If I reboot the computer everything goes back to normal. But a lot of times I don't want to have to do that. Putting the computer to sleep and bringing it back up actually fixes the problem as well but that is a pain. I would like to know what could be causing this and how to prevent it from happening. – Dason Oct 29 '11 at 2:43

Not the answer you're looking for? Browse other questions tagged or ask your own question.