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

Bug 314897

Summary: [Compatibility] Renderer gets SWT exception
Product: [Eclipse Project] e4 Reporter: Paul Webster <pwebster>
Component: UIAssignee: Project Inbox <e4.ui-inbox>
Status: CLOSED DUPLICATE QA Contact: Remy Suen <remy.suen>
Severity: critical    
Priority: P3 CC: emoffatt, remy.suen
Version: 1.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Console exceptions none

Description Paul Webster CLA 2010-05-28 11:23:17 EDT
Created attachment 170364 [details]
Console exceptions

I deleted my deltas file and opened my e4 workspace with I20100527-2121

It came up great.  Then I went to open the Error Log, and got an NPE error dialog.  My console contains exceptions.  I've attached them to make them more readable.

PW
Comment 1 Paul Webster CLA 2010-05-28 11:25:05 EDT
I can no longer open views, like Error log or Search.

PW
Comment 2 Remy Suen CLA 2010-05-28 11:34:16 EDT
(In reply to comment #0)
> Then I went to open the Error Log

How was this opened? Ctrl+3? Window > Show View?
Comment 3 Paul Webster CLA 2010-05-28 11:46:09 EDT
The Error log I tried to open with CTRL+3.  After that I tried both with the same rror.

PW
Comment 4 Paul Webster CLA 2010-06-01 20:31:22 EDT
This happens to me if I only have one perspective open (I remove deltas.xml from my e4 workspace).  Then with only the Java perspective open I use CTRL+3 to open Console or Search or Error Log.

PW
Comment 5 Remy Suen CLA 2010-06-02 05:40:03 EDT
(In reply to comment #4)
> This happens to me if I only have one perspective open (I remove deltas.xml
> from my e4 workspace).  Then with only the Java perspective open I use CTRL+3
> to open Console or Search or Error Log.

I talked to Paul last night about this but was unable to reproduce this on Windows 7 with eclipse-SDK-I20100531-2039-win32.zip pointing at a fresh workspace.
Comment 6 Remy Suen CLA 2010-06-18 11:59:12 EDT
I believe this has been fixed by bug 316783.

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