0

My system has been running for 61 days:

$ uptime
09:30:37 up 61 days,  5:09,  1 user,  load average: 0.42, 0.63, 0.49

Of course I don't have it powered on all the time destroying the environment, it is suspended most of the time:

$ suspendtime
Linux uptime 5,289,027 seconds (8 weeks, 5 days, 5 hours, 10 minutes, 27 seconds)
127 Suspends 3,159,701 seconds (5 weeks, 1 day, 13 hours, 41 minutes, 41 seconds)
Real uptime 2,129,326 seconds (3 weeks, 3 days, 15 hours, 28 minutes, 46 seconds)

Source of suspendtime: How to get real uptime?

I kind of brag about how much better Ubuntu is than Windows because you don't have to reboot it all the time. However:

  • Two days ago a terminal screen froze
  • Last couple of days keyboard repeat rate slowed about 20%
  • Buttons on my python program grew 10 times too high

Do I have to reboot?

WinEunuuchs2Unix
  • 105,762

1 Answers1

1

Simply logout and login again

Powering off and on is the best way of cleaning your system out entirely and starting fresh. Rebooting comes very close to that.

However many times you can simply logout and back in to start with a fresh desktop without any frozen windows, lagging keyboard or mouse, etc. If problem persists then you can go the extra mile and reboot.

When you log back in you may receive a crash report like the one below. I've checked the box to show more details. Because this is a random error and it was 61 days in the making I'm not sending the crash report to the folks at Canonical (makers of Ubuntu). I don't want to waste their time on such a trivial issue.

To prevent sending crash report to Canonical, uncheck the box at the bottom titled "Send an error report to help fix this problem".

Unresponsive Terminal Internal Error after logging in.png

WinEunuuchs2Unix
  • 105,762