Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 493245 - [GTK3] Unhandled event loop exception on project and class creation
Summary: [GTK3] Unhandled event loop exception on project and class creation
Status: CLOSED DUPLICATE of bug 486069
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.5.2   Edit
Hardware: PC Linux
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-09 10:39 EDT by Chris Warrick CLA
Modified: 2016-05-09 10:43 EDT (History)
1 user (show)

See Also:


Attachments
Crash when creating new Java project (4.02 KB, text/x-log)
2016-05-09 10:39 EDT, Chris Warrick CLA
no flags Details
Crash when viewing installation details (5.49 KB, text/plain)
2016-05-09 10:40 EDT, Chris Warrick CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Warrick CLA 2016-05-09 10:39:31 EDT
Created attachment 261560 [details]
Crash when creating new Java project

Eclipse is unusable with GTK 3. Many operations end with an Unhandled event loop exception:

* New Java Project — does not show a window, instantly throws exception
* New Project → Java Project — first button press throws, second opens the „Enter a project name” window with the input widget missing
* New → Class — freezes in the “working” state after pressing Finish, the Stop button does nothing, killing Eclipse is the only way out; this curiously happens only with some checkbox combinations (main() + inherited abstract methods)
* Installation details — does not show a window, instantly throws exception

Arch Linux, GTK 3.20.3, KDE 5, Adwaita GTK theme.

(GTK 2 works fine.)
Comment 1 Chris Warrick CLA 2016-05-09 10:40:19 EDT
Created attachment 261561 [details]
Crash when viewing installation details
Comment 2 Eric Williams CLA 2016-05-09 10:43:31 EDT
This is a duplicate of bug 486069, which was fixed in 4.6 M6.

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