Bug 159007 - No response whatsoever for any input dialog
Summary: No response whatsoever for any input dialog
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.2   Edit
Hardware: Other HP-UX
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2006-09-27 13:39 EDT by Kenneth Corgin CLA
Modified: 2008-04-10 16:32 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kenneth Corgin CLA 2006-09-27 13:39:03 EDT 
This is quite strange.  When I try to install Eclipse for the first time it pops up the Workspace Launcher dialog, but that dialog does not respond to any mouse or keyboard events, which makes it completely useless.  But when I run it without the Java JRE in my PATH, it pops up a normal dialog complaining that it can't find the Java JRE and that dialog responds normally.  Even stranger, I tried running version 3.1.1 and got the same result.  Then I went back to another system where I had installed and been using 3.1.1 some time in the past.  It brought up the main IDE window, but that IDE didn't respond to mouse or keyboard events either.

Currently running HP-UX B.11.11 PA-Risc architeture.  I'm thinking that the admins must have installed something new since I used to run eclipse that is blocking things.  I'll ask them if they have done anything to the motief libraries
Comment 1 Wassim Melhem CLA 2006-10-15 21:18:07 EDT 
I'm sure this is not an Eclipse issue

Moving to SWT though to comment/advise.
Comment 2 Grant Gayed CLA 2007-06-08 12:41:00 EDT 
Sorry for the late response on this.  I've never heard of this before, and am pretty sure it must be something on your system.  Has this been resolved in the meantime?
Comment 3 Grant Gayed CLA 2008-04-10 16:32:57 EDT 
Timed out, closing.  If this is still a problem with eclipse 3.4M6 or later then please reopen this report.