Jaunty: It Takes A Long Time To Regain Control After Screensaver

[Jeremy LaCroix]

I am using Kubuntu 64-bit (Jaunty) with all current updates. After about 15 minutes my screensaver (default blank screen) activates. When it does, I cannot leave the screensaver by moving my mouse, I have to use my keyboard. After the screensaver closes, it takes about 1 minute for me to gain control of my mouse again. The cursor disappears but reappears about 30 seconds to a minute after the screen saver goes away. The system appears frozen during this time.

[Brett Johnson (linuxturtle)]

I also see a similar problem on two of my 32-bit gnome-ubuntu jaunty machines. The screensaver does not respond to moving the mouse, only to the keyboard. And it takes an abnormally long time for the passwd check to succeed, and for the screensaver to quit. FWIW, both machines have nvidia graphics, and use the nvidia driver. I also have another machine on jaunty which has ATI graphics, and uses the ati/radeon driver, and this machine does not exhibit the problem.

[Harald Sitter (apachelogger)]

Jeremy, does your machine also use the nvidia driver?

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

Yes, I do use the Nvidia driver.

[Jonathan Thomas (echidnaman)]

This would really be either an xscreensaver or nvidia driver problem. At the least not KDE-specific.

[Tormod Volden (tormodvolden)]

Does KDE use xscreensaver?

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[Kenyon Ralph (kralph)]

Are these wireless mice? I notice that my Logitech wireless mouse sometimes goes to sleep and will not wake unless I click the mouse button. I wonder if this could be present in this bug report.

[Brett Johnson (linuxturtle)]

I no longer see this problem in lucid or maverick. I'd say it's gone/fixed..