Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

When my computer is locked, regardless of it timing out after 10 minutes or by me pressing CTRL+L, it takes forever to activate it.

It also appears as if the time it takes is linear to the time it as been locked.

If I lock my computer in the evening, at 8 o'clock in the morning it will take between one or two minutes to get the login-prompt when touching any keys or moving the mouse.

The computer somewhat responds immediately though, the CPU-fan goes into hyper-drive, ergo it's doing something. If I've left the System Monitor running, it will show both CPU's becoming rather busy the second I touched a key.

Running dmesg doesn't reveal any errors or indications about what it has been spending time on.

I'm running Gnome Classic, with the following settings:

System Settings: Power enter image description here

System Settings: Brightness and Lock enter image description here

Worth mentioning is that this behavior was introduced with 12.04, I had no issues whatsoever with 11.10.

If anybody could help me fix this rather annoying issue my ulcer will go away.

share|improve this question

closed as off-topic by Eric Carvalho, Luis Alvarado Jul 25 at 0:57

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Bug reports and problems with the development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." – Eric Carvalho, Luis Alvarado
If this question can be reworded to fit the rules in the help center, please edit the question.

Your link to your System Settings:Power screen shot is broken... –  TheX Sep 28 '12 at 14:04
I wrote a small script that invoked top every three seconds, and it showed me that it was Xorg who jumped up to use ~60% of the CPU until I was allowed/able to log in: –  Håkan Oct 9 '12 at 6:20
My previous comment was broken when I pressed <kbd>Enter</kbd> I'm afraid. Anywho, as Xorg went from using ~4% of the CPU up to ~60%, I now need to find a way to debug/diagnose Xorg I guess... –  Håkan Oct 9 '12 at 6:31