Ubuntu
eclipse package

Eclipse 3.5 hangs on splash 'loading workbench'

Asked by Martijn_Hoekstra

When trying to start eclipse, the splash screen hangs on 'loading workbench'.
Eclipse Galileo on Maverick
Reconfiguring and reinstalling the Eclipse package didn't work.

Can I possibly clear a workbench file or something?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu eclipse Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
Last query:
Last reply:
Revision history for this message
Best actionparsnip (andrew-woodhead666) said : 		#1

Log a bug, the packages in maverick are still beta. Maveric is NOT ready and NOT stable. What did you expect....

Revision history for this message
Martijn_Hoekstra (martijnhoekstra) said : 		#2

Since the eclipse package hadn't changed, and depends only on java, I expected it to work. I doubt this is actually a bug, it's been a while since I used eclipse, and I doubt this is actually a bug but rather a problem with my local profile, ill see if removing my local profile will help

Revision history for this message
Benjamin Drung (bdrung) said : 		#3

If you want to get rid of the configuration remove or rename ~/.eclipse (Note: All additional plugins will be gone).

Please make sure that you don't have old xulrunner packages installed (xulrunner-1.9.2 should be sufficient).

Revision history for this message
Martijn_Hoekstra (martijnhoekstra) said : 		#4

On Fri, Sep 24, 2010 at 2:16 AM, Benjamin Drung
<email address hidden> wrote:
> Your question #126552 on eclipse in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/eclipse/+question/126552
>
> Benjamin Drung posted a new comment:
> If you want to get rid of the configuration remove or rename ~/.eclipse
> (Note: All additional plugins will be gone).
>
> Please make sure that you don't have old xulrunner packages installed
> (xulrunner-1.9.2 should be sufficient).
>
> --
> You received this question notification because you are a direct
> subscriber of the question.
>

Benjamin,
Removing an old xulrunner package resolved this problem for me.