Re: Can't open evergreen

Martin Dorey

unread,

Mar 23, 2010, 2:31:42 PM3/23/10

to Susi Berrington, evergre...@googlegroups.com

Adding the public mailing list. Elliott added some Java 6-specific code, then made it only build and run with Java 6, then went round adding a fair bit of other Java 6 code. I presume you're using Java 5 because it works better with some dodgy Windows X server? If so, then you're stuck with the Evergreen of a couple of days ago or working out a solution that lets you upgrade Java. Surely the latter is the way of the future. Wasn't there some hack you can do with "insets" or something that makes it tolerable?

From: Susi Berrington
To: Martin Dorey
Sent: Tue Mar 23 11:24:18 2010
Subject: Can't open evergreen

Uncaught exception

An error occurred in Evergreen:

Exception RuntimeError: Java failed with #<Process::Status: pid=17132,exited(1)>

Please send us the contents of the application log, from /tmp/edit.log.16905.

An idea of what you were doing when Java exited might be useful.

at /usr/share/software.jessies.org/evergreen/Resources/salma-hayek/bin/invoke-java.rb:486:in `launch'
at /usr/bin/evergreen:105:in `launch0'
at /usr/bin/evergreen:20:in `launch'
at /usr/share/software.jessies.org/evergreen/Resources/salma-hayek/bin/show-alert.rb:122:in `call'
at /usr/share/software.jessies.org/evergreen/Resources/salma-hayek/bin/show-alert.rb:122:in `initialize'
at /usr/share/software.jessies.org/evergreen/Resources/salma-hayek/bin/show-alert.rb:134:in `new'
at /usr/share/software.jessies.org/evergreen/Resources/salma-hayek/bin/show-alert.rb:134:in `report_exceptions'
at /usr/bin/evergreen:20:in `launch'
at /usr/bin/evergreen:113

Tried to start it from a console and saw this exception on the console:

clinton$ evergreen &
[1] 17453
clinton$ Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)

I closed evergreen because it was failing to open a file I need to look at.

Says "Please send us ..." but doesn't say who "us" are, so you get it! :-)

I would attach /tmp/edit.log.16905 but it's not interesting:

clinton$ ll /tmp/edit.log.16905
-rw-rw-r-- 1 susiw software 0 2010-03-23 11:09 /tmp/edit.log.16905
clinton$ cat /tmp/edit.log.16905
clinton$

These are all the edit.log files:

clinton$ ls -lh /tmp/edit.log.*
-rw-rw-r-- 1 susiw software    0 2010-03-23 11:09 /tmp/edit.log.16905
-rw-rw-r-- 1 susiw software    0 2010-03-23 11:10 /tmp/edit.log.17453
-rw-rw-r-- 1 susiw software 276K 2010-03-23 03:13 /tmp/edit.log.25469
-rw-rw-r-- 1 susiw software 901K 2010-03-22 17:40 /tmp/edit.log.4299
-rw-rw-r-- 1 susiw software 3.2M 2010-03-15 14:14 /tmp/edit.log.7740
-rw-rw-r-- 1 susiw software    0 2010-03-23 10:00 /tmp/edit.log.8868
clinton$

Attached the one modified today and yesterday.

I don't know if you want to look at this or just forward it to someone at jessies.org, or is there just something I'm doing wrong?

Ta,

Susi

Martin Dorey

unread,

Mar 23, 2010, 2:42:12 PM3/23/10

to evergre...@googlegroups.com, Susi Berrington

> stuck with the Evergreen of a couple of days ago

http://software.jessies.org/downloads/debian/org.jessies.evergreen_6.175.3205_amd64.deb might be handy. If you try that and it works, let us know and I'll stash a copy on the server.

--
You received this message because you are subscribed to the Google Groups "evergreen-users" group.
To post to this group, send email to evergre...@googlegroups.com.
To unsubscribe from this group, send email to evergreen-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/evergreen-users?hl=en.

Elliott Hughes

unread,

Mar 23, 2010, 3:47:27 PM3/23/10

to evergre...@googlegroups.com, Susi Berrington

I thought i'd changed the invoke-java script to fail if it couldn't find a java 6 vm. This looks like it went ahead with a java 5 vm...

On Mar 23, 2010 11:42 AM, "Martin Dorey" <mdo...@bluearc.com> wrote:
>> stuck with the Evergreen of a couple of days ago
>
> http://software.jessies.org/downloads/debian/org.jessies.evergreen_6.175.3205_amd64.deb might be handy. If you try that and it works, let us know and I'll stash a copy on the server.
>
> ________________________________
> From: evergre...@googlegroups.com [mailto:evergre...@googlegroups.com] On Behalf Of Martin Dorey
> Sent: Tuesday, March 23, 2010 11:32
> To: Susi Berrington
> Cc: 'evergre...@googlegroups.com'
> Subject: Re: Can't open evergreen
>
>
> Adding the public mailing list. Elliott added some Java 6-specific code, then made it only build and run with Java 6, then went round adding a fair bit of other Java 6 code. I presume you're using Java 5 because it works better with some dodgy Windows X server? If so, then you're stuck with the Evergreen of a couple of days ago or working out a solution that lets you upgrade Java. Surely the latter is the way of the future. Wasn't there some hack you can do with "insets" or something that makes it tolerable?
>
> ________________________________
> From: Susi Berrington
> To: Martin Dorey
> Sent: Tue Mar 23 11:24:18 2010
> Subject: Can't open evergreen
> Uncaught exception
>
> An error occurred in Evergreen:
>
> Exception RuntimeError: Java failed with #<Process::Status: pid=17132,exited(1)>
>
> Please send us the contents of the application log, from /tmp/edit.log.16905.
>
> An idea of what you were doing when Java exited might be useful.
>
> Command line was:

Martin Dorey

unread,

Mar 23, 2010, 6:59:06 PM3/23/10

to evergre...@googlegroups.com, Susi Berrington

Fixed in svn.

Elliott Hughes

unread,

Mar 23, 2010, 7:08:49 PM3/23/10

to evergre...@googlegroups.com, Susi Berrington

D'oh! Thanks. My grep didn't find that.

On Mar 23, 2010 3:59 PM, "Martin Dorey" <mdo...@bluearc.com> wrote:
> Fixed in svn.
>
> ________________________________
> From: evergre...@googlegroups.com [mailto:evergre...@googlegroups.com] On Behalf Of Elliott Hughes
> Sent: Tuesday, March 23, 2010 12:47
> To: evergre...@googlegroups.com
> Cc: Susi Berrington
> Subject: Re: RE: Can't open evergreen
>
>
> I thought i'd changed the invoke-java script to fail if it couldn't find a java 6 vm. This looks like it went ahead with a java 5 vm...
>

> On Mar 23, 2010 11:42 AM, "Martin Dorey" <mdo...@bluearc.com<mailto:mdo...@bluearc.com>> wrote:
>>> stuck with the Evergreen of a couple of days ago
>>
>> http://software.jessies.org/downloads/debian/org.jessies.evergreen_6.175.3205_amd64.deb might be handy. If you try that and it works, let us know and I'll stash a copy on the server.
>>
>> ________________________________

>> From: evergre...@googlegroups.com<mailto:evergre...@googlegroups.com> [mailto:evergre...@googlegroups.com<mailto:evergre...@googlegroups.com>] On Behalf Of Martin Dorey

>> Sent: Tuesday, March 23, 2010 11:32
>> To: Susi Berrington

>> Cc: 'evergre...@googlegroups.com<mailto:evergre...@googlegroups.com>'

>> Subject: Re: Can't open evergreen
>>
>>
>> Adding the public mailing list. Elliott added some Java 6-specific code, then made it only build and run with Java 6, then went round adding a fair bit of other Java 6 code. I presume you're using Java 5 because it works better with some dodgy Windows X server? If so, then you're stuck with the Evergreen of a couple of days ago or working out a solution that lets you upgrade Java. Surely the latter is the way of the future. Wasn't there some hack you can do with "insets" or something that makes it tolerable?
>>
>> ________________________________
>> From: Susi Berrington
>> To: Martin Dorey
>> Sent: Tue Mar 23 11:24:18 2010
>> Subject: Can't open evergreen
>> Uncaught exception
>>
>> An error occurred in Evergreen:
>>
>> Exception RuntimeError: Java failed with #<Process::Status: pid=17132,exited(1)>
>>
>> Please send us the contents of the application log, from /tmp/edit.log.16905.
>>
>> An idea of what you were doing when Java exited might be useful.
>>
>> Command line was:

>> at /usr/bin/evergreen:105:in `launch0'
>> at /usr/bin/evergreen:20:in `launch'

>> I don't know if you want to look at this or just forward it to someone at jessies.org<http://jessies.org>, or is there just something I'm doing wrong?

>>
>> Ta,
>> Susi
>>
>> --
>> You received this message because you are subscribed to the Google Groups "evergreen-users" group.

>> To post to this group, send email to evergre...@googlegroups.com<mailto:evergre...@googlegroups.com>.
>> To unsubscribe from this group, send email to evergreen-use...@googlegroups.com<mailto:evergreen-users%2Bunsu...@googlegroups.com>.

>> For more options, visit this group at http://groups.google.com/group/evergreen-users?hl=en.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "evergreen-users" group.

>> To post to this group, send email to evergre...@googlegroups.com<mailto:evergre...@googlegroups.com>.
>> To unsubscribe from this group, send email to evergreen-use...@googlegroups.com<mailto:evergreen-users%2Bunsu...@googlegroups.com>.

Reply all

Reply to author

Forward