Eclipse will not start (Edgy)

I got the same error after a fresh installation of ubuntu-6.10-rc-desktop-amd64.iso (without apt-get update and dist-upgrade). Eclipse doesn't start. I attached my workspace/.metadate/.log file.

I also got this problem after doing a (distribution) software update yesterday which installed eclipse 3.2.1. Attaching my .log file from trying to run with Sun jdk 1.5.0_08 amd64.

Running eclipse 3.2.1 amd64 downloaded from eclipse.org works fine however.

updating for edgy-proposed

The same with me.

Fresh installation of ubuntu-6.10-rc-desktop-amd64.iso(actually updated), eclipse 3.2.1 amd64, java version "1.5.0_09" and Eclipse not start.

I had the same problem. I can now start eclipse by doing this:

apt-get remove --purge `dpkg -l |grep eclipse|awk '{print $2}'` `dpkg -l |grep libswt|awk '{print $2}'`

rm -rf /usr/share/eclise /usr/lib/eclipse

apt-get install eclipse

Eclipse now runs. The only problem is that it does not close when closing the application (File-Exit):

25524 pts/3 S+ 0:00 /usr/lib/eclipse/eclipse -vm /usr/lib/jvm/java-1.5.0-sun/bin/java -install /usr/lib/eclipse -startup /usr

I will open an other bug report for this problem.

Is it related to this?
http://dev.eclipse.org/mhonarc/lists/platform-swt-dev/msg03850.html

claudio: I think you're avoiding the bug by making the eclipse startup fall back on sun's JVM. The bug is with GCJ eclipse. Or you can verify by installing: eclipse-gcj java-gcj-compat , which is likely to make startup fail again.

claudio: This will not work for me. The installation pulls in the eclipse-gcj packages, and even if I manually force it to use the sun-jvm, startup will fail with the same error.

I can start Eclipse when I download it and run it from my /home directory...

I will try this tomorrow and see if it works

Regards

Stuart

claudio@ubuntu wrote:

>I had the same problem. I can now start eclipse by doing this:
>
>apt-get remove --purge `dpkg -l |grep eclipse|awk '{print $2}'` `dpkg -l
>|grep libswt|awk '{print $2}'`
>
>rm -rf /usr/share/eclise /usr/lib/eclipse
>
>apt-get install eclipse
>
>Eclipse now runs. The only problem is that it does not close when
>closing the application (File-Exit):
>
>
>25524 pts/3 S+ 0:00 /usr/lib/eclipse/eclipse -vm /usr/lib/jvm/java-1.5.0-sun/bin/java -install /usr/lib/eclipse -startup /usr
>
>I will open an other bug report for this problem.
>
>
>

@Gabriel de Perthuis:
Yes, I use java from SUN setting the JAVA_HOME environment variable.

However, after installing the packages you proposed:
claudio@sydney:~$ eclipse -vm /usr/lib/jvm/java-1.4.2-gcj-4.1-1.4.2.0/bin/java

eclipse runs fine and mysteriously eclipse exists fine now (see bug https://launchpad.net/distros/ubuntu/+source/eclipse/+bug/68714 )

Claudio

This is a pretty serious problem for me. I was able to run Eclipse if I downloaded it manually and ran it from my home directory (all other methods crashed on startup), but it shuts down after about 20 seconds regardless of which JVM I use.

When I launch Eclipse, the logo appears and the progress bar gets about halfway through. Then an "Error notifying a preference change listener" dialog appears.

Clicking Okay makes the dialog box immediately re-appear. The cycle continues until I do a "killalll java".

I'm not sure if this is the same bug everyone else is having. I've tried deleing my .eclipse folder and installing a different combination of Eclipse packages, but no go.

The temporary solution is to remove the ~/workspace/.metadata folder. As long as this folder is missing, Eclipse will launch. Unfortunately this means re-creating the entire workspace from scratch every single time.

I'd also like to note that I've tried the default JVM as well as Sun's JVM, following the directions on the Ubuntu Wiki. Doesn't make a difference in terms of the program starting, so I'm inclined to believe the problem is in the Eclipse package and not with the JVM.

I'd like to add that I get the same error with a downloaded version when I chown -R root:root on the eclipse folder.

I thought that maybe if I chown the packaged install to my user it would fix the problem, however it did not.

bbzbryce wrote:

>I'd like to add that I get the same error with a downloaded version when
>I chown -R root:root on the eclipse folder.
>
>I thought that maybe if I chown the packaged install to my user it would
>fix the problem, however it did not.
>
>
>
Strange, because I downloaded the 3.2.1 gz file from Eclipse, unzipped
it to my desktop (not root), opened Eclipse and it ran fine. I wonder
if it is permissioning problems?

Regards

Stuart

> I'd like to add that I get the same error with a downloaded
> version when I chown -R root:root on the eclipse folder.
> I thought that maybe if I chown the packaged install to my
> user it would fix the problem, however it did not

Same here. I downloaded eclipse 3.2.1 for AMD64, unzipped, and it crashed with the same error.

I downloaded 3.3M2 (development version) and that worked ok.

I have the same problem. And if i try "eclipse -vm /usr/lib/jvm/java-1.4.2-gcj-4.1-1.4.2.0/bin/java" the problem rest.

Thanks

Fix posted by claudio@ubuntu at 2006-10-27 20:45:38 UTC does not work for eclipse* (3.2.1-0ubuntu1) sun-java5-* (1.5.0-08-0ubuntu1) on AMD 64. Also not after setting /etc/eclipse/java_home and running update-java-alternatives.

Hope a fix will be available soon.

I am also experiencing this problem, with both Sun and GCJ VM's.

I've tried running RadRails 0.71 too, but with similar SWT issues, albeit more info in the trace.

I have attached a traceback. Doesn't matter whether I use gcj or Sun Java5.

(I find it surprising that this made it through quality control; eclipse seems like a pretty big deal.)

This must be a problem with the SWT 3.2 package.

The same "memmove" problem occurs with Azureus 2.5

Nearly the same problem here. I will try the eclipse 3.3M3.

Same problem (memmove) here, Edgy Eft (final, fresh install), amd64.

So, is this already the solution to the problem?
https://launchpad.net/distros/ubuntu/+source/eclipse/+bug/68380

That solved the problem for me. Did apt-get source eclipse, applied the patch and built, then installed libswt3.2-gtk-jni, and all was well. Can we get this into the official package soon? This is affecting lots of developers around here.

Same thing here, downloading a version from eclipses sites and running seemed to work somewhat. I would really prefer to get one via apt-get, and I would prefer not to build it myself.

Edgy Eft, also final, amd64

This didn't work for me.
I got the source, applied the debdiff and built the whole thing.
After installing either all the resulting deb-packets or only the libswt3.2-gtk-jni packet I still get the same error.

Any suggestions?

I finally got stable Eclipse running... Had to
 1. Download Eclipse from their website (http://www.eclipse.org/downloads/)
 2. Download and install Sun Java 64 bit
 3. Point Eclipse to that JVM

Use this guide as reference:
http://www.ubuntuforums.org/showthread.php?t=201378&highlight=eclipse

That is the only way i got a *stable* eclipse running on x86_64.

Anyway its stable as long as I don't push "Web browser" then it will fail with a GWT error.

Please devs, fix this bug :)

This also does not work for me.
Still the same error.

Wow. You'd think a bug of this magnitude would be fixed in a few days. Guess Edgy isn't so stable after all.

Same problem here, Feisty on AMD64.

Could you write a guide how to apply the proposed patch, or perhaps rebuild the packages in the repos? Eclipse is very important to me.

Ahem, are there any progress on this? A solution has been posted, Matthias Klose is assigned and the status has been "in progress" for over three days now... I really hope something will happen soon. I miss both eclipse and azureus. Thank you :-)

Could at least the old version be readded until this is fixed so that version out there atleast works?

Experiencing the same thing... noticed there is a fix for this (https://launchpad.net/bugs/68380) but hasn't been committed yet. Anyone here know how I could make use of that fix in while I await for the powers-that-be to add it?

Meanwhile, I'm going to "vote" for that fix...

sudo /usr/lib/eclipse/eclipse

Will get eclipse running, but it will try and load the root workspace, you have to goto /home/username/workspace it will load

Just tried. sudo /usr/lib/eclipse/eclipse

Got the same error message but in the root workspace.

Tries as root user, still same error here. It's very frustrating. Could we at least roll back the repos to the last working state?

Running as root also fails here (x64 w/ Sun Java 1.5)

N:th the request for rollback or fixed packages

I just heard on #ubuntu-motu that something that looks like a fix has been released to edgy-proposed (which is a repo that you have to add manually (either using synaptic or using commandline))

I'm currently running Feisty so i cant tell you if it's true that this fixes the problem for edgy. So could somebody try to enable edgy-proposed and check?

The line in /etc/apt/sources.list would look like this:
deb http://archive.ubuntu.com/ubuntu/ edgy-proposed restricted main multiverse universe

I hope that this may be the solution for edgy, and that it would be merged to feisty soon :)

Here's a fairly complete procedure that will help a relative newbie fix this problem, using the uncommitted patch provided under bug #68380.

I'm new to Linux, so forgive the excessive detail--though others may be grateful for it. It was hard won.

oops. here's the attachment

I've tried this a second time.
This solution does not work for me. I'm still getting the same error.

Also, there's no updated packet in edgy-proposed-updates.

I'm seriously thinking about dropping Ubuntu for something that works... :-(

If I can attach this 140kb file successfully, this will provide a means for everyone to check whether my i386 solution works for similar systems without having to do the long compile step.

^^ Does not work for me, neither does the edgy-proposed packages. *Sigh*

For those who really need Eclipse, put debian's unstable branch to sources.list and install Eclipse from there. It's version 3.1.2 if I recall correctly but at least it works.

Tom's instructions worked for me.

BTW, in bug #68380 it's suggested that this fix be "run by the release team" to "get it into edgy-proposed" - anyone know how to get that particular ball rolling?

I had the same problem, in a amd64 edgy system.

So, for the other illiterate on dpkg-buildpakcage processes like me, I did the following, and it seems to have worked:

1) go to a temporary source directory

# cd ~/src

2) get the source

# apt-get source eclipse

3) apply the patch, see bug #68380, the first thing there is the pointer to this patch (eclipse.debdiff), just download it

# patch -p0 < eclipse.debdiff

4) move into the eclipse directory

# cd eclipse-3.2.1/

5) compile the whole thing, took hours on a dual core 2.167 system, and there was lots of warning/error messages, but it seems to have worked well enough

# dpkg-buildpackage -D -nc -b

6) back to the top directory

# cd ..

7) install the newly generated .deb (all of them had the version "_3.2.1-0ubuntu2_amd64.deb"). I'm not sure if all of them are necessary or not ... but I installed all of them over:

# dpkg --install libswt3.2-*.deb eclipse-*.deb

8) go back to your normal user, and, very important, remove previous configuration/setup -- that's the way I got things working, maybe not all of it is necessary. Actually I had previously moved my projects out of the way first, and the workspace/ was always some default created by eclipse:

$ rm -rf workspace/ .eclipse/

9) run eclipse, I'm using sun's java here:

$ eclipse -vm /usr/lib/jvm/java-1.5.0-sun/bin/java -ws gtk

hope this helps someone else :)

I did exactly this before.
I don't understand why this works for some people and not for others.

>I did exactly this before.
>I don't understand why this works for some people and not for others.

Several bugs at work, probably. I've noticed that some reports describe different symptoms than others.

Also... Some official word on whether this is going to ever be fixed, please? I'd like to know whether I should just go ahead and use the original Eclipse releases instead of Ubuntu packages. I'd prefer not to spend a day or so configuring it properly just to find out that a working Ubuntu release has finally been made.

Just a note, I just saw this happen in an SWT app that I wrote. I pinned down the error to be using a 64-bit JVM with 64-bit SWT libraries, _but a swt.jar file build for 32-bit_. I don't know if it's useful, but it might help someone fix it.

The error is still here on Feisty amd64.

With the latest update it works fine for me!

Confirmed. Works fine using feisty on amd64 today.

When using the AMD64 version of Eclipse, please make sure that you are also using the AMD64 version of the JDK. You can get it from the SUN website: http://java.sun.com/javase/downloads/index.jsp

Install this version to e.g. /usr/jdk1.5.0_10 and run Eclipse with the following command:

eclipse -vm /usr/jdk1.5.0_10/bin/java

Hope this works for you!

my java -version says:

dun@mars:~$ java -version
java version "1.5.0_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_08-b03, mixed mode)

Eclipse still does not start with this java vm.

Hi everyone!

I had the same problem with Eclipse 3.2.1 under a clean install (upgrade) of Ubuntu Edgy AMD64 (but not under Edgy i386). I got it working, however, by removing the files in /usr/lib/eclipse (I did not delete /usr/lib/eclipse/links/ though) and then copying the files in eclipse-SDK-3.2.1-linux-gtk-x86_64.tar.gz which I got from the eclipse download site to that directory. I then removed my ~/workspace directory entirely, and then running eclipse with the -clean parameter.

I was even able to copy my a backed up workspace directory from a previous installation to my home directory and use that (after doing a rm -rf ~/workspace first).

I made no changes to my java vm inbetween any of those steps nor to anything in /etc/alternatives. I have JDK/JRE 1.5 installed.

I still get the message "Unable to create view: memmove" in the welcome pane when eclipse starts, but everything other than that seems to work fine, including plugins.

Hope this helps someone.

I've had the problem too, build using the last maintence (unstable) build from the Eclipse-Downloadpage, it worked.
--> Problem should is solved in the coming Eclipse Release

After selecting a different workspace in eclipse I could launch it again

Hi!
I finally got it working on my AMD64. Here is my configuration:

tobi@hbd:~$ uname -a
Linux hbd 2.6.17-10-generic #2 SMP Tue Dec 5 21:16:35 UTC 2006 x86_64 GNU/Linux

tobi@hbd:~$ java -version
java version "1.5.0_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_08-b03, mixed mode)

tobi@hbd:~$ grep proposed /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu/ edgy-proposed universe main multiverse restricted

tobi@hbd:~$ dpkg -l |grep eclipse|awk '{print $2 $3}'
eclipse3.2.1-0ubuntu2
eclipse-jdt3.2.1-0ubuntu2
eclipse-pde3.2.1-0ubuntu2
eclipse-platform3.2.1-0ubuntu2
eclipse-rcp3.2.1-0ubuntu2
eclipse-source3.2.1-0ubuntu2
tobi@hbd:~$ dpkg -l |grep eclipse|awk '{print $2,$3}'
eclipse 3.2.1-0ubuntu2
eclipse-jdt 3.2.1-0ubuntu2
eclipse-pde 3.2.1-0ubuntu2
eclipse-platform 3.2.1-0ubuntu2
eclipse-rcp 3.2.1-0ubuntu2
eclipse-source 3.2.1-0ubuntu2
tobi@hbd:~$ dpkg -l |grep swt|awk '{print $2,$3}'
libswt3.2-gtk-java 3.2.1-0ubuntu2
libswt3.2-gtk-jni 3.2.1-0ubuntu2
tobi@hbd:~$ dpkg -l |grep jdk|awk '{print $2,$3}'
sun-java5-jdk 1.5.0-08-0ubuntu1

Important: When I tried to start eclipse, I still got the same error. So I deleted the workspace, still the same error. Finally I deleted the workspace and started eclipse with "eclipse -clean" and then it worked!

While starting I get this message:
using specified vm: /usr/lib/jvm/java-1.5.0-sun

HTH!

Yes, the solution proposed by Tobias works. Would be good to figure out how to update the package so that it fixes for everyone else. I suspect deleting the workspace is not needed, as long as eclipse is run with -clean first time round.

The solution from Tobias also works for me, though I'm using java-gcj, not the sun jvm. I guess promoting the ubuntu2 version from proposed would fix for all?

The package form edgy-proposed did work for me.
I just had to use once "eclipse -clean" after the install of the package.
Afterwards it worked
I'm using sun's java VM

Tobias' solution above also works for me. Except after adding:

deb http://archive.ubuntu.com/ubuntu/ edgy-proposed universe main multiverse restricted

to

/etc/apt/sources.list

dpkg still reported eclipse3.2.1-0ubuntu1, but 'apt-get install' selected the right one. Possibly my 'sudo apt-get check' or 'sudo apt-get update' helped.
Eclipse now works fine. Thanks.

The edgy-proposed Azureus package also works (same SWT problem).

Tobias' solution worked here as well.

I had a similar problem, however it was not with Eclipse directly. I simply had a java app that was compiling with gcj against the org.eclipse.swt.gtk.linux.x86_64_3.2.1.v3235.jar.so file.

I followed a similar line of thinking to the above but I downloaded these packages instead:
pool/universe/e/eclipse/libswt3.2-gtk-gcj_3.2.1-0ubuntu2_amd64.deb
pool/universe/e/eclipse/libswt3.2-gtk-java_3.2.1-0ubuntu2_amd64.deb
pool/universe/e/eclipse/libswt3.2-gtk-jni_3.2.1-0ubuntu2_amd64.deb

These files can be found on your nearest mirror. :-)

You can install the packages just by clicking on them, but at some time you're going to have to do a 'sudo apt-get install -f' on a command line to remove the old ones.

This approach protects you from other issues that can happen if you add edgy-proposed to your feed.

I hope this helps someone!

Cheers,
Tudor.

fixed in eclipse_3.2.1-0ubuntu3 in edgy-updates