| Summary: | [EditorMgmt] Keyboard input impossible after screensaver | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Gerben Blom <g.d.blom> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | CLOSED DUPLICATE | QA Contact: | Remy Suen <remy.suen> |
| Severity: | minor | ||
| Priority: | P3 | Keywords: | needinfo |
| Version: | 3.5.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Gerben Blom
Is this specific to eclipse or the system itself is not responsive in general ? Also, you mention editors; is it a problem with editors only while the other parts of eclipse respond to keyboard input ? Please do provide other details like whether this happens consistently / frequently on your system or if you noticed anything in the logs, etc. Need info to move this bug further; marking as WORKSFORME for the time being. This is specific to Eclipse. The rest of Ubuntu is responsive as usual. This only happens when an editor window has the cursor focus. It only seems to affect the editor. Normal editing is possible again after either - editing somewhere else in Eclipse (f.e. a find/replace dialog box) - minimizing and maximizing the Eclipse window - any other window gets the focus It does happen often but after some testing I must conclude that it does not happen every time. I did the reopen the ticket, was I supposed to do this? (In reply to comment #3) Stumbled upon Bug 70397 as well ... Are you using Compiz? Can you try using Metacity instead? Hi Remy, Switched to Metacity and could not reproduce the problem. Switched back to Compiz and it did occur again. Switched back to Metacity, no problem. Definitely something to do with Compiz. Gerben. (In reply to comment #6) > Switched to Metacity and could not reproduce the problem. Switched back to > Compiz and it did occur again. Switched back to Metacity, no problem. > Definitely something to do with Compiz. Thanks for the information, Gerben. *** This bug has been marked as a duplicate of bug 298261 *** |