Welcome to NeoOffice developer notes and announcements
NeoOffice
Developer notes and announcements
 
 

Problems after upgrading to Sierra or High Sierra? Try these steps
Problems after upgrading to NeoOffice 2017? Try these steps
Download or installation problems? Try these steps


Support
· NeoOffice Support
· NeoWiki


Announcements
· Twitter @NeoOffice


Downloads
· Download NeoOffice
· Download latest patch
· User Guide
· User Guide Volume 2


RSS Feeds
· Announcements Only
· All Posts


  
NeoOffice :: View topic - NeoOffice/J 1.1 doesn't want to work under 10.4.2
 SearchSearch   ProfileProfile   Log inLog in 

NeoOffice/J 1.1 doesn't want to work under 10.4.2
 
Post new topic   Reply to topic    NeoOffice Forum Index -> NeoOffice Releases
View previous topic :: View next topic  
Author Message
Guest






PostPosted: Wed Jul 20, 2005 2:49 pm    Post subject: NeoOffice/J 1.1 doesn't want to work under 10.4.2 Reply with quote

Previous versions worked fine.
Updated to the full 1.1 release, but now when I launch NeoOffice/J, the icon bounces in the Dock for a while, disk thrashes, then the icon disappears again but NeoOffice/J refuses to start AND gives no error messages at all.

Even tried deleting it and doing a full fresh install of 1.1 to no avail.

Any ideas?

This is on a Dual 2.5GHz G5, 4.5GB RAM, MacOS X 10.4.2. Same result even after a fresh reboot.
Back to top
sardisson
Town Crier
Town Crier


Joined: Feb 01, 2004
Posts: 4588

PostPosted: Wed Jul 20, 2005 3:40 pm    Post subject: Reply with quote

Does the Console.log (/Applications/Utilities/Console.app) print anything when you try to launch Neo/J?

Smokey

_________________
"[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki
Back to top
View user's profile Send private message Visit poster's website
Guest






PostPosted: Wed Jul 20, 2005 3:58 pm    Post subject: Reply with quote

Hi Smokey,

Thanks for the reply. Just had another go and Console logs the following -

resolveUndefined(_abort) in /System/Library/Frameworks/JavaVM.framework/Versions/1.3.1/Home/../Libraries/libJDirect.jnilib
resolveUndefined(_abort) in /System/Library/Frameworks/JavaVM.framework/Versions/1.3.1/Home/../Libraries/libJDirect.jnilib
Exception in thread "Thread-1" java.lang.UnsatisfiedLinkError: /System/Library/Frameworks/JavaVM.framework/Versions/1.3.1/Libraries/libJDirect.jnilib:
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1414)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1330)
at java.lang.Runtime.loadLibrary0(Runtime.java:744)
at java.lang.System.loadLibrary(System.java:815)
at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:4Cool
at java.security.AccessController.doPrivileged(Native Method)
at com.apple.mrj.macos.carbon.CarbonLock.<clinit>(CarbonLock.java:12)
Jul 21 00:13:15 Gandalf-2 crashdump[2106]: soffice.bin crashed
Jul 21 00:13:18 Gandalf-2 crashdump[2106]: crash report written to: /Users/keith/Library/Logs/CrashReporter/soffice.bin.crash.log


The resultant soffice.bin.crash.log says

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000034

(amongst other things).


I have done Software Update and repaired permissions, and made sure I'm using NO/J 1.1 with Patch-0.

Worth reinstalling Java, or should I file a bug report including the full crash log?

Thanks for your help!
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11692
Location: California, USA

PostPosted: Wed Jul 20, 2005 4:18 pm    Post subject: Reply with quote

It appears that the Mac OS X 10.4.2 upgrade corrupted some of your Java 1.3.1 files. I am not sure how this can be fixed, but you may want to try rebooting and running "repair disk permissions" in the /Applications/Utilities/Disk Utility application. It probably won't help but it won't hurt.

Patrick
Back to top
View user's profile Send private message Visit poster's website
val1984
Oracle


Joined: May 30, 2005
Posts: 229
Location: France

PostPosted: Thu Jul 21, 2005 12:35 am    Post subject: Reply with quote

Maybe you should try to reapply Mac OS X 10.4.2 Combo Update ?

I have no problems with NeoOffice/J 1.1 patch 0 on 10.4.2 Smile
Back to top
View user's profile Send private message
Guest






PostPosted: Thu Jul 21, 2005 1:51 pm    Post subject: Reply with quote

OK, I've tried reapplying the big 10.4.2 patch.

I've rerun repair permissions.

I've even installed the latest release of Java (1.5.x).

All to no avail, NeoOffice/J still refuses to run and still crashes out with the same Java errors.

Anything else anyone can think I can try?

Oh, and why is it using 1.3.1 when the default on Tiger is 1.4.2?

Thanks in advance,
Keith
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11692
Location: California, USA

PostPosted: Thu Jul 21, 2005 2:13 pm    Post subject: Reply with quote

Anonymous wrote:
Anything else anyone can think I can try?


I think that the only way to get Java 1.3.1 reinstalled is to run the Mac OS X 10.4 install again. Sad

Anonymous wrote:
Oh, and why is it using 1.3.1 when the default on Tiger is 1.4.2


Because Java 1.4 did not exist when I started developing Neo/J, Java 1.4.1 was incredibly buggy when it first came out, and Neo/J needs access to the underlying native window and font C pointers that changed radically from Java 1.3.1 to Java 1.4.x.

I am in the process of moving the code to handle, but it is not a trivial amount of effort.

Patrick
Back to top
View user's profile Send private message Visit poster's website
sardisson
Town Crier
Town Crier


Joined: Feb 01, 2004
Posts: 4588

PostPosted: Thu Jul 21, 2005 2:17 pm    Post subject: Reply with quote

Anonymous wrote:
Oh, and why is it using 1.3.1 when the default on Tiger is 1.4.2?


Answer (that article is slightly out of date now that we've passed June 6, but it explains the situation for 1.1--which was less than 2 months from release after 10 months in development when 10.4 appeared, anyway--perfectly)

As for the failing to launch, you might see if the solutions suggested in this thread work.

If not, filing a bug and attaching your full crashlog (attach after submitting the bug initially; don't paste in the comments field) is probably the best option short of a reinstall of 10.4.0 + combo updater. Edit: Patrick posted while I was writing; he seems sure that Java 1.3.1 is corrupted, so looks like a reinstall.... Sad

Smokey

_________________
"[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki
Back to top
View user's profile Send private message Visit poster's website
Guest






PostPosted: Thu Jul 21, 2005 2:33 pm    Post subject: Reply with quote

Hi Patrick and Smokey,

thanks for your replies.

First off - ta for explaining why Neo uses 1.3.1 Java - all make sense!

Second - I think I would agree with you both that my 1.3.1 Java install is buggered. I'd rather avoid doing a full reinstall of Tiger if I can possibly help it, so what I'll try is copying the 1.3.1 Java tree from my iBook to my PowerMac and see how that goes. Of course, if that still fails then it's time to back everything up (goodness knows where to!) and then reinstall 10.4 I guess.


I'll let you know how it goes, although it may take a little time (especially if a reinstall is needed!).

Cheers,
Keith
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11692
Location: California, USA

PostPosted: Thu Jul 21, 2005 2:37 pm    Post subject: Reply with quote

Anonymous wrote:
Second - I think I would agree with you both that my 1.3.1 Java install is buggered. I'd rather avoid doing a full reinstall of Tiger if I can possibly help it, so what I'll try is copying the 1.3.1 Java tree from my iBook to my PowerMac and see how that goes. Of course, if that still fails then it's time to back everything up (goodness knows where to!) and then reinstall 10.4 I guess.


That sounds like a safe approach. Just to be really safe, only copy the /System/Library/Frameworks/JavaVM.framework/Versions/1.3.1 folder so that your Java 1.4.2 installation doesn't get messed up.

Patrick
Back to top
View user's profile Send private message Visit poster's website
Guest






PostPosted: Fri Jul 22, 2005 12:57 am    Post subject: Reply with quote

Update - I've installed Java 1.3.1 from another known working 10.4.2 Mac, rebooted, redone disk permissions, rebooted again.

And NeoOffice/J still crashed at startup with exactly the same errors logged in the console and crashlog Sad

I guess the only option left now is to log a bug, so I'll fill that out tonight.

Thanks,
Keith
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11692
Location: California, USA

PostPosted: Fri Jul 22, 2005 7:24 am    Post subject: Reply with quote

Before you waste time filing a bug report, you might want to verify that Java 1.3.1 actually works. You can do this by running a simple Java program using the following steps:

1. Create a file called Test.java and put the following lines in it:

Code:
import java.awt.*;

public class Test {

        public static void main(String[] args) {

                Frame f = new Frame();
                Panel p = new Panel();
                f.add(p);
                f.setSize(500, 500);
                f.show();

        }

}


2. Open a terminal and "cd" to the folder that you put the Test.java file in.

3. Compile the Test.java file using the following command (edit: updated the command as succeeding posts confirmed my original command had a typo):

Code:
javac Test.java


4. Run the compiled program with Java 1.3.1 using the following command:

Code:
/System/Library/Frameworks/JavaVM.framework/Versions/1.3.1/Commands/java -classpath . Test


If a blank window appears when you run the program, then you know that Java 1.3.1 is working.

Patrick


Last edited by pluby on Fri Jul 22, 2005 3:29 pm; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website
jjmckenzie51
The Anomaly


Joined: Apr 01, 2005
Posts: 1055
Location: Southeastern Arizona

PostPosted: Fri Jul 22, 2005 11:56 am    Post subject: Reply with quote

pluby wrote:
Before you waste time filing a bug report, you might want to verify that Java 1.3.1 actually works. You can do this by running a simple Java program using the following steps:

1. Create a file called Test.java and put the following lines in it:

Code:
import java.awt.*;

public class Test {

        public static void main(String[] args) {

                Frame f = new Frame();
                Panel p = new Panel();
                f.add(p);
                f.setSize(500, 500);
                f.show();

        }

}


Would it not be nicer to use something like the HelloWorld.java code that is around somewhere? That way they get the nice blank panel with the words "Hello World" in it.

If course, if they get a crash message, that means it is time to backup and rebuild, not something that is everyday with MacOSX. That is something that I did when my compiles of NeoJ and OOo 1.1.x and 1.9 would not work.

James
Back to top
View user's profile Send private message
Luke
Captain


Joined: Sep 08, 2003
Posts: 63
Location: Teesside, UK

PostPosted: Fri Jul 22, 2005 2:39 pm    Post subject: Reply with quote

Is this a typo?

pluby wrote
Quote:

Code:
java Test.java

I get
Code:
 Exception in thread "main" java.lang.NoClassDefFoundError: Test/java


Code:
 javac Test.java
works.

{Neo/J is working fine for me - I was trying out the minimal Java gui app to see if launching it would cause preloading of classes and speed up the first launch of Neo/J. It doesn't Sad }

Luke
Back to top
View user's profile Send private message
jjmckenzie51
The Anomaly


Joined: Apr 01, 2005
Posts: 1055
Location: Southeastern Arizona

PostPosted: Fri Jul 22, 2005 2:58 pm    Post subject: Reply with quote

Luke wrote:
Is this a typo?

Code:
 javac Test.java
works.


You are right, Luke. I've been working with Java for a while now and I missed that one (Slapping sound of hand hitting forehead.)

Luke wrote:
{Neo/J is working fine for me - I was trying out the minimal Java gui app to see if launching it would cause preloading of classes and speed up the first launch of Neo/J. It doesn't Sad }


Nor should it. Each Java workspace is called up on its own. There may be differing parameters. You should see how long it takes for a multiple java program to come up on a SUN system. Not knocking SUN, but whoever wrote the application could have called it up from one sandbox (JVM) but did not.

James
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    NeoOffice Forum Index -> NeoOffice Releases All times are GMT - 7 Hours
Goto page 1, 2  Next
Page 1 of 2

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group

All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © Planamesa Inc.
NeoOffice is a registered trademark of Planamesa Inc. and may not be used without permission.
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.02 Seconds