Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 315010

Summary: Editor does not accept input after coming back from screensaver
Product: [Eclipse Project] Platform Reporter: Dan Buhrman <dan.buhrman>
Component: IDEAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: minor    
Priority: P3 CC: dan.buhrman, niels, remy.suen
Version: 3.5.2   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
See Also: https://launchpad.net/bugs/586329
Whiteboard:

Description Dan Buhrman CLA 2010-05-30 11:57:43 EDT
Build Identifier: M20100211-1343

Originally reported at: https://bugs.launchpad.net/bugs/586329

Binary package hint: eclipse

This is simple to reproduce. Start Eclipse, open a .java file, do some editing. Wait for the screensaver to come on the lock the screen. Move the mouse or whatever, type in your password, and then Eclipse will not accept any input. Minimize Eclipse, then maximize it, and you can edit again.

Not a very critical bug, just an annoyance.

Also, this did not seem to be an issue before 10.04.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: eclipse 3.5.2-2ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Thu May 27 08:11:14 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: eclipse
xulrunner-versions: /usr/lib/xulrunner-1.9.2.3

This bug has also been confirmed by two other Ubuntu users.

Reproducible: Always

Steps to Reproduce:
1. Launch Eclipse and open a Java file.
2. Allow Ubuntu to start the screensaver, thus locking the screen.
3. Come back from screensaver, and the editor will not accept input.
Comment 1 Remy Suen CLA 2010-05-30 21:33:04 EDT
Pretty sure there's another bug open for this.
Comment 2 Remy Suen CLA 2010-05-30 21:33:56 EDT

*** This bug has been marked as a duplicate of bug 298261 ***