Issue 115180 - OOo does not find Java 6 update 22
Summary: OOo does not find Java 6 update 22
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOO330m12
Hardware: All Mac OS X, all
: P2 Trivial with 22 votes (vote)
Target Milestone: OOo 3.3
Assignee: thorsten.martens
QA Contact: issues@framework
URL: http://wiki.services.openoffice.org/w...
Keywords: oooqa
: 115182 115201 115228 115421 115444 115564 115569 115793 (view as issue list)
Depends on:
Blocks: 111112
  Show dependency tree
 
Reported: 2010-10-21 14:52 UTC by joachim.lingner
Modified: 2017-05-20 10:20 UTC (History)
14 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Crash log (93.57 KB, text/plain)
2010-10-22 15:42 UTC, aviret
no flags Details
Log of crash when I try to open an empty doc. (93.57 KB, application/vnd.oasis.opendocument.text)
2010-10-22 15:43 UTC, aviret
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description joachim.lingner 2010-10-21 14:52:47 UTC
The last automatic Java update on Mac installed Java 6 update 22 which cannot be
used by OOo because it does not find the Java VM. That is, wizard and Java uno
services will not work. The reason is that the value of the java.home system
property has changed.
Comment 1 joachim.lingner 2010-10-21 14:53:29 UTC
.
Comment 2 joachim.lingner 2010-10-21 15:10:46 UTC
Workaround:

cd /System/Library/Java/JavaVirtualMachines
sudo ln -s ../../Frameworks/JavaVM.framework/JavaVM JavaVM 
Comment 3 niklas.nebel 2010-10-21 19:17:11 UTC
*** Issue 115182 has been marked as a duplicate of this issue. ***
Comment 4 terry_nyorks 2010-10-21 23:44:31 UTC
Continuation from 
http://user.services.openoffice.org/en/forum/viewtopic.php?
f=17&t=34853&p=161265#p161265
-------------------------------------------------------------

After running patch via Terminal, from bug id=115180:

OO also detects RTE. However DBase still crashes when trying to open file , or when open - a 
table, or perform edit etc (several tries, each time) as per report attached.

Is anyone from OO/Oracle/Apple watching this, or can someone report the feedback.

I have to do a review of OO Base, and can't work - my deadline is fast approaching. Help!
Comment 5 aviret 2010-10-22 09:15:09 UTC
For me, OOo (StarOffice 9.2 or OpenOffice.org 3.3 Beta) is crashing during the opening of any file, not only 
Base file.

Greetings
Comment 6 mdxonefour 2010-10-22 11:22:34 UTC
md->aviret: We tried to reproduce what you describe. I can't confirm that any
file open leads to crash. .odt for example does not crash. May your test file
contain anything which needs java?
Comment 7 Olaf Felka 2010-10-22 14:25:33 UTC
*** Issue 115201 has been marked as a duplicate of this issue. ***
Comment 8 aviret 2010-10-22 15:42:13 UTC
aviret->md: I have a Calc document which I'm using without any problem, but a Writer doc leads to a crash 
when I use page-down for instance. Or when I try to open an empty doc. from the "Centre de démarrage" (I 
attach the log in the ticket).

A case has been opened for this: SR 73733263.

Greetings
Comment 9 aviret 2010-10-22 15:42:47 UTC
Created attachment 72154 [details]
Crash log
Comment 10 aviret 2010-10-22 15:43:38 UTC
Created attachment 72156 [details]
Log of crash when I try to open an empty doc.
Comment 11 aviret 2010-10-22 15:49:37 UTC
During the crash I had the following in the console:


MacBook:config vir$ /Applications/StarOffice.app/Contents/MacOS/soffice
2010-10-22 16:48:44.338 soffice[5239:903] [JVM Detection] FillMatcher: failed to get JavaVM.framework 
version
Bus error
MacBook:config vir$ 
Comment 12 papayes 2010-10-22 16:25:30 UTC
The two control lines
cd / System / Library / Java / JavaVirtualMachines
sudo ln-s .. / .. / Frameworks / JavaVM.framework / JavaVM JavaVM

can enable Java in OOo

but, if the path is well marked and the radio button checked

JAVA is not active, even after restarting and so and...

Worse:

1. Unable to install new OOo 3.2.1 on MacOS X 10.6.4 Intel:
OOo freezes at the fourth window of creating the profile by tapping the button
"Finish".

Other drawbacks are minor face this stopeur!

2 Can not install Extensions requiring JRE : for example : grammar Language Tool

3 After a purge of the profile,
after the 4th stage of creating the new profile, the program running on empty,
need to Force Quit ... Report sent to Apple.

By replacing the old saved profile, the program runs successfully, but ...

4. In launching a new file "Base", the program crashes when the registration of
the new database. Almost normal, since the wizard requires Java Database ...

5. The Impress Wizard freezes OOo

In fact, you can not use OOo, or install it after this update.

Every effort is made to the Apple world is destroyed in a single update of Java.

papayes
Comment 13 billmerkel 2010-10-22 18:57:49 UTC
This upgrade has also broken my OO3.2.1  I had added an extension to output different resolutions 
for graphic exports in Draw.  That extension is called EnhancedGraphicExportDialogs.oxt 0.2.1.  That 
broke in that OO would crash.  I tried the sudo command to map the new VM file.  still crashed. 
Rebooted, still crashed. I disabled the extension, rebooted, and now the native export crashes Draw.  
Only path I now have is do a PDF export, then re-export from Preview.app to a graphic file.  Sad....
Comment 14 mnsteve 2010-10-23 00:17:08 UTC
I am unable to use OOo 3.2.1 for any function requiring Java after installing
the distributed patch from Apple.  The workaround from jj results in a JRE being
recognized but the actually makes the problem worse.  Before the workaround, OOo
realized that it had no working Java and displayed an error popup.  Now it just
crashes, and since the problem-reporting mechanism uses Java, the crash is
recursive.  This has essentially put all Apple users of OOo out of business;
only the most simple tasks don't require Java.
Comment 15 amaloney 2010-10-23 19:03:15 UTC
The workaround has made matter worse!
How do I undo:

sudo ln-s .. / .. / Frameworks / JavaVM.framework / JavaVM JavaVM

and restore Java to its previous state?

Al Maloney

Comment 16 sierkb 2010-10-24 00:10:19 UTC
Maybe helpful for a proper solution in OpenOffice:

Please read and pay attention to what Apple tells in its recent Release Notes to
this recent Java Update:

Apple Developer: Java for Mac OS X 10.6 Update 3 and 10.5 Update 8 Release Notes
http://developer.apple.com/library/mac/#releasenotes/Java/JavaSnowLeopardUpdate3LeopardUpdate8RN/Introduction/Introduction.html#//apple_ref/doc/uid/TP40010380-CH1-SW1

Section "New and Noteworthy"
Subsection "Third Party JVM Support and Locations"
Subsubsection "Java SE 6 Locations"

http://developer.apple.com/library/mac/releasenotes/Java/JavaSnowLeopardUpdate3LeopardUpdate8RN/NewandNoteworthy/NewandNoteworthy.html#//apple_ref/doc/uid/TP40010380-CH4-DontLinkElementID_4

<cite>
The location of the Java SE 6 runtime home has changed to
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home. JDK bundles
provided via the Developer package, developer previews, and 3rd party JVMs
should be installed in /Library/Java/JavaVirtualMachines or
~/Library/Java/JavaVirtualMachines. Developer previews of Java can now be
installed and uninstalled without affecting the system JVM(s).
</cite>

and

Subsubsection "Java IDEs"
http://developer.apple.com/library/mac/releasenotes/Java/JavaSnowLeopardUpdate3LeopardUpdate8RN/NewandNoteworthy/NewandNoteworthy.html#//apple_ref/doc/uid/TP40010380-CH4-DontLinkElementID_5

<cite>
In testing, some Java IDEs have shown problems navigating into the new JDK
bundle structure, and persisting the location of the new JDK bundles. Some IDEs
may have to change how they prompt users to locate a JVM on Mac OS X, and should
ideally present a list of JVMs generated from /usr/libexec/java_home --xml,
which outputs each discovered JVM, and orders them according to the user's order
in Java Preferences.
</cite>

Also pay attention to the following comment to this issue (and such proposed
workaround like simply symlinking the JVM location) by one core developer of
NeoOffice, where this issue is also discussed but an non-issue, because
NeoOffice seems to detect the Java JVM another way (maybe the
official-and-recommended-by-Apple way?) than OpenOffice:

http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&p=60996#60996
Comment 17 sierkb 2010-10-24 00:47:27 UTC
See also:

Apple Developer: Technical Q&A QA1170: Important Java Directories on Mac OS X
http://developer.apple.com/library/mac/#qa/qa2001/qa1170.html

<cite>
Q: I am porting a Java product to Mac OS X. What are the equivalents for
directories and paths common to JDK installations on other platforms?

A: Since a JDK is preinstalled on every copy of Mac OS X, the location of the
Java VM may vary, but can be found using tools built into the OS. User input
should never be required to locate Java-related paths and directories.

Java Home

Many Java applications need to know the location of a $JAVA_HOME directory. The
$JAVA_HOME on Mac OS X should be found using the /usr/libexec/java_home command
line tool on Mac OS X 10.5 or later. On older Mac OS X versions where the tool
does not exist, use the fixed path "/Library/Java/Home". The
/usr/libexec/java_home tool dynamically finds the top Java version specified in
Java Preferences for the current user. This path allows access to the bin
subdirectory where command line tools such as java, javac, etc. exist as on
other platforms. The tool /usr/libexec/java_home allows you to specify a
particular CPU architecture and Java platform version when locating a $JAVA_HOME.

Another advantage of dynamically finding this path, as opposed to hardcoding the
fixed endpoint, is that it is updated when a new version of Java is downloaded
via Software Update or installed with a newer version of Mac OS X. For this
reason, it is important that developers do not install files in the JDKs inside
of /System, since the changes will be lost with subsequent updates by newer
versions of Java.

To obtain the path to the currently executing $JAVA_HOME, use the java.home
System property.
</cite>

Apple Manpage to java_home:
http://developer.apple.com/library/mac/#DOCUMENTATION/Darwin/Reference/ManPages/man1/java_home.1.html


How does OpenOffice determine $JAVA_HOME so far? This official and recommended
way? When not this recommended (because most flexible and future-safe) way, why
not? Maybe that is the way NeoOffice does it (and has no troubles)? Maybe a good
starting point for a fix of the issue in OpenOffice?
Comment 18 mnsteve 2010-10-24 01:07:14 UTC
Unfortunately, the directory provided by the dynamic tool is the same one that
is currently specified in my non-working installation of OOo.  Should something
be specified in the Parameters or Class Path on the Java options screen under
Preferences?

Or if there was a way to roll back the update, I'd take that action.  I have not
been able to locate the previous version or a way to install it.
Comment 19 alex.thurgood 2010-10-24 13:32:20 UTC
Adding oooqa keyword with regard to bug report.

Alex
Comment 20 lohmaier 2010-10-24 15:28:56 UTC
Not sure what else Apple changed wrt java, but maybe it's worth to revisit the 
patch to issue 92926 again once this issue is fixed.
Comment 21 sierkb 2010-10-25 00:38:50 UTC
Maybe these following two postings (and the thread around them) from February
2010 on Apples Mailinglist java-dev by Mike Swingler, Java Runtime Engineer
Apple Inc., could be also helpful to find a proper solution:

FYI: QA1170 updated for /usr/libexec/java_home
http://lists.apple.com/archives/java-dev/2010/Feb/msg00132.html

Re: FYI: QA1170 updated for /usr/libexec/java_home
http://lists.apple.com/archives/java-dev/2010/Feb/msg00150.html

And if does not suffice, then ask on Java-dev or email Mike Swingler personally
to help out.

-- 
Apple Java-dev -- This list is for technical discussions related to Java on Mac
OS X.
http://lists.apple.com/mailman/listinfo/java-dev

Apple lists.apple.com Mailing Lists:
http://lists.apple.com/mailman/listinfo
Comment 22 florian 2010-10-25 07:31:41 UTC
To undo the workaround simply issue
rm /System/Library/Java/JavaVirtualMachines/JavaVM
in the Terminal.
Comment 23 papayes 2010-10-25 08:29:22 UTC
On a forum English, a method to remove the freezing after creating a new profile.

Edit
~ / Library / Application
Support/OpenOffice.org/3/user/config/javasettings_MacOSX_x86.xml
Replace tag
Apple Inc. <vendor>. </ vendor>
by
<vendor> Apple Computers Inc.. </ vendor>
Save (Cmd + S) 

Tested with 3.2.1 and 3.3.0 RC2

BUT
there is still no memory of the activation of the JRE after quitting and
restarting OOo:
(Apple.inc radio button and the path does not appear immediately as they should)
where problems need a Java JRE enabled
- Freeze the registration of a New Base
- Language Tools inactive (using the old profile) or inability to install (New
Profile) 
Comment 24 Raphael Bircher 2010-10-25 08:35:17 UTC
Add myself to CC
Comment 25 ozlady 2010-10-26 03:16:30 UTC
Add myself to CC
Comment 26 eric_openoffice 2010-10-26 12:31:55 UTC
Add myself to CC
Comment 27 chcd 2010-10-26 13:56:32 UTC
This seems to be the same issue as 115200
Comment 28 joachim.lingner 2010-10-26 14:42:08 UTC
The new java versions are now located properly and OOo can handle old invalid
java settings (javasettings_MacOSX_x86.xml). That is, on MacOS 10.6 where the
URL to the runtime library, as encoded in the VendorData section, has become
invalid after the Java update, OOo will search and use the new Java.
Comment 29 joachim.lingner 2010-10-26 14:43:01 UTC
@tm: Please verify.
Comment 30 jsc 2010-10-26 14:53:39 UTC
cc me
Comment 31 ipellegrin 2010-10-26 15:00:59 UTC
Why has this issue marked as resolved / fixed?
The workaround does not work and I do not see a solution.
Please clarify
Comment 32 r_rethmann 2010-10-26 15:15:35 UTC
Had the same issues (OOO crashing when using macros/db-access). My workaround is to revert back to the last Java VM (1.6.0_20).
Here is what I did:
in Terminal I became super-user: sudo -s
Then I renamed the Java directories:
cd /Library/
mv Java Java.old
cd /System/Library/
mv Java Java.old
cd Frameworks/
mv JavaVM.framework JavaVM.framework.old
rm -rf /Users/yourname/Library/Caches/Java

Then I mounted my TimeMachine backup and went a few days back and copied the old folders over (except for the cache dir)

In OOO Java settings now 1.6.0_20 shows up and my macros work again...

Feel free to do this on your own risk...
Comment 33 chcd 2010-10-26 15:36:34 UTC
In my opinion, that does not fix the issue, but for a handful of users.

In order to apply this workaround, you would need Time Machine, or any other backup of the previous JVM, 
which is not available to many Mac OS users. Time machine is basically an external hard drive that Apple 
sells. Mac OS can work with that external drive, scheduling automatic backups.

By default, Mac OS's "Software Update" deletes the previous JVM as it has installed Java 6 update 22.

This issue affects to all OO components that use Java, making then useless on any Mac OS environment. Please see issue 115200, in which this has been assigned priority P1.
Comment 34 jsc 2010-10-26 15:44:22 UTC
i used the workaround and for me it works. I can run OOo 3.2.1 without any
problems and all Java extensions work. The wizards work as well. An OOo 3.3
developer snapshot (not including the fix) works in the same way. 

Comment 35 mnsteve 2010-10-26 16:30:40 UTC
The way that this issue has been handled has made me realize that I cannot rely
on this product for my day-to-day work.  It is ironic that Word 2011 for the
Apple is released today.  It was a good run on OpenOffice while it lasted, and I
really like the product and respect the group that puts so much effort into it,
but I cannot afford to be dependent on a product where a show-stopper bug is
"resolved" by someone changing text in a tracking database.
Comment 36 sierkb 2010-10-26 16:59:33 UTC
@chcd:

>Time machine is basically an external hard drive that Apple sells
>Mac OS can work with that external drive, scheduling automatic backups.

Correction to avoid irritations/misunderstandings:

That statement of you is not quite correct so far. Don't mess Time Machine (the
convenient backup service of MacOSX) with Time Capsule (the optional and not
compelling needed hardware drive offered by Apple). Time Machine is an integral
convenient part of MacOSX but optional service to automatically let backup the
whole system on a regulary basis.

You can use Time Machine with basically ANY external hard drive. You MAY use
Apples own offered external hard drive named "Time Capsule" for that job, but
you don't NEED (or are urged) to use that hardware -- you can use instead ANY
external Non-Apple HD (minimum capacity should ideally be equal to or greater
than the system's HD capacity) for that automatic backup job via Time Machine
that you want. You even can use Time Machine over a network and use a foreign
(meaning: Non-Apple HD) remote network drive, that is suitable prepared for that
job.

See also: 

Apple Time Machine
http://www.apple.com/macosx/what-is-macosx/time-machine.html

Apple Support: Time Machine
http://support.apple.com/kb/HT1427?viewlocale=en_US

Apple Time Capsule
http://www.apple.com/timecapsule/
Comment 37 eric_openoffice 2010-10-26 17:18:08 UTC
@mnsteve: I think that either jl or tm found a solution and applied a patch directly to the upstream OOo 
sources which will be used to build an upcoming RC3. That's my interpretation of the command that jl 
made today at 13:42 CET.

But any clarification from either jl or tm is welcome. 

If you complain about a lack of transparency try to report a similar issue to MS maybe they are more 
detailed and transparent on how they solve your issue. 
Comment 38 chcd 2010-10-26 18:33:08 UTC
Agreed on my misunderstanding. The point, which still stands, it was that you need an additional 
external drive, or a backup previous to the Java VM update, to apply the workaround (external drive, 
Time Capsule, back up media...).

Another question is that there are security reasons for the deployment of the new Java VM 
(http://www.oracle.com/technetwork/java/javase/6u22releasenotes-176121.html), so recommending a 
rollback to a previous version, opens a whole new can of worms.

I agree that you won't get much difference in support from Microsoft. You need to consider that there 
are 3 different organizations involved here, which slows down the response: Oracle (who changed the 
Java release), Apple (who made changes in the Java installation folders), and then OO.org, which didn't 
receive notifications until the end users notice the problems.

Unless there has been patched on version 3.3 R3 (or a 3.2.1 patch), and it is available for end users, my 
understanding is that this issue remains unsolved.
Comment 39 ylchiron 2010-10-26 19:55:36 UTC
Please, put back the status from resolved to new.  This problem is NOT fixed yet.  Proposing to roll back to 
an outdated java via messing around with Terminal commands and a hypothetical backup:
1) isn't possible for everybody
2) is not acceptable for a real fix.  
Furthermore, the fork NeoOffice (based on OOo 3.1.2) handles perfectly this java update.

Please, this is very serious problem.  I can't use Base anymore.

Thanks, Yannick
Comment 40 sierkb 2010-10-26 19:55:53 UTC
@chcd:

Agreed, concerning the problems and can of worms with reverting to an older Java
installation.

>and then OO.org, which didn't receive notifications
>until the end users notice the problems.

Maybe because they have slept and have been uninformed? And didn't seem to read
and follow neither the Developer Release Notes Apple has regulary enclosed with
its Java Previews in its free (!) ADC Download area since over a year nor the
since month public available statements of Mike Swingler, Java Runtime Engineer,
Apple Inc.?

The OOo team/Sun/Oracle may have known since month all about this and all about
this potential risk and potential trouble -- at least since February 2010 -- and
could have changed its Java detection code early enough to what Apple recommends
since over a year. Please read my comments and links to this bug, especially my
two links from Oct 24 23:38:50 to Apples java-dev Mailinglist entries from
February 2010:

http://lists.apple.com/archives/java-dev/2010/Feb/msg00132.html
http://lists.apple.com/archives/java-dev/2010/Feb/msg00150.html

Curious, that NeoOffice is NOT in trouble caused by this recent Java update,
because the NeoOffice team has obviously changed and adapted its JRE detection
code early enough (many month or years ago). This is, what they say to this
whole mess:
http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&p=60996#60996

I think, this issue, this mess, could have been totally avoidable. And it's not
Apple to blame on this in the first place but OpenOffice/Sun/Oracle. It's very
awkward and puts a bad light onto OpenOffice/Oracle (QA?), and it is grist to
the mills of forks like LibreOffice and NeoOffice and gives the user/Mac user
once more a reason to prefer or switch over to LibreOffice/NeoOffice. Or they
flee into the arms of Microsoft and use their MS Office.

Please, such kinds of issues like this should never happen again. Because this
particulary issue has been so foreseeable, avoidable and finally is so
dispensable. This issue should be a warning sign to improve QA and to better
hear and look what's going on on the platforms -- especially relating the Mac
platform (including better platform integration and adherence/impementation of
the platform-specific Human Interface Guidelines).

Where are the observable results of Oracle's promises to more foster Sun's
heritage with more developers and more money? Changing just icons ist not enough.
Comment 41 Raphael Bircher 2010-10-26 19:57:46 UTC
fyi: RESOLVED FIXED means it's fixed in a CWS. A QA, in this case tm has to
approve this changes and set the issue to FIXED VERIFIED.

After this the change goes into a millestone in this case I think it's RC 3. End
agen we make a final test at the RC and close this issue. This is our workflow.

No Panic, the Issue is always marked as stoper for the upcomming version 3.3, so
it will be fixed with the next release.
Comment 42 ylchiron 2010-10-26 20:04:12 UTC
Thanks a lot rbircher.
It is nice to be reassured on the way the problem will be handled.
Yannick
Comment 43 eric_openoffice 2010-10-26 20:39:12 UTC
@sierkb: Besides what Raphael already wrote I can only add that I'm - who does end-user QA - is not a 
coders himself and so I can't take a look at the code and see if it uses the Jave detection Apple sugests. I 
have to trust the developers that they did a code peer review. When I get an RC I install it and start doing 
the testing.

When 3.2.1 was in RC it did detect the then up to date Java and everything broken now was working back 
then. 

BTW: LibO is broken as well and we cannot use NeoOffice code because it's under GPL. 
Comment 44 Martin Hollmichel 2010-10-26 20:46:02 UTC
we're just investigating on how to provide a hot fix within the next days for
OpenOffice.org and other derivatives for the 3.1.x, 3.2.x releases. This fix is
also scheduled for upcoming 3.3 release. 
please keep in mind that issue tracker is an developer related tool and not a
customer, user facing tool, please follow announce@openoffice.org for the final
announcement of the availiblity of the patches. 
Sorry for the inconvience this caused, but for a small group of developers of a
multiplatform suite it is not that easy to keep track of all anouncements of all
aspects of the supported platforms.
Comment 45 ipellegrin 2010-10-27 08:25:44 UTC
A hot fix is most welcome.
Will it be readily downloadable from OO > Help > Check for Updates ?
Or is it necessary to download it from somewhere else? If so, could someone post the URL on here please?
Comment 46 Martin Hollmichel 2010-10-27 08:58:30 UTC
URL will be posted here, once it is available.

the check for update mechanism will be in place, once 3.3 is finally released.
Comment 47 ipellegrin 2010-10-27 10:18:16 UTC
Everybody, who like me, has not been able to use their OO spreadsheets on a Mac - and suffered from the 
consequent embarrassment with their clients - may like to use this alternative.

Download NeoOffice at http://www.neooffice.org, install it, and use it to work with your OO spreadsheets.
Comment 48 billmerkel 2010-10-27 12:43:31 UTC
Does anyone know if Oracle Open Office / Star Office has this problem?  Is one workaround to purchase 
a license from oracle?
Comment 49 pgaga 2010-10-27 15:56:53 UTC
This issues exists on all versions of OOo and its derivatives except NeoOffice.
 I have posted in the StarOffice, Oracle Office and OpenOffice forums about it.

Phil

Comment 50 mdxonefour 2010-10-27 16:16:07 UTC
md->tm/jl: With the libraries from CWS jl162 it looks ok on my 10.6.4 system. As
discussed marking this issue as verified now.
Comment 51 mdxonefour 2010-10-27 16:17:45 UTC
For the records: This issue is already accepted as stopper. This fix and the
corresponding CWS jl162 will are targeted for integration into our next build on
the OpenOffice.org 3.3 code line OOO330. That will be build OOO330m13 wihich
starts later this week.
Comment 52 mdxonefour 2010-10-27 16:21:09 UTC
For all those who like to get hands on the fixed libraries to try them out now,
please have a look at
http://wiki.services.openoffice.org/wiki/Documentation/FAQ/Platform/Mac_OS_X_10.6
There I put some information where to find the fixed libraries at least
temporarily for now and how to apply them manually.

Your feedback is welcome.
Comment 53 ylchiron 2010-10-27 17:38:09 UTC
I downloaded and installed the two fixed libraries.  As far as I can tell, it seems that it fixed the issue.  The 
files who had problems since the update work correctly (spreadsheet .ods and base .odb).  The Preferences 
of OpenOffice.org now show correctly the Java updated 1.6.0_22.   

On a side note, for people afraid with Terminal commands, one can access to the files by ctrl-clicking (or 
right-clicking) on OpenOffice.org.app in the Applications folder, and choose "Show Package Contents", 
then navigate in Contents/basis-link/ure-link/lib/.  From there, one can move the two old libraries to 
store them somewhere else as backup, and add the fixed libraries provided. 

Yannick
Comment 54 pgaga 2010-10-27 19:37:55 UTC
Personally for installing these patches, I will use a java file manager called
mucommander - in the case of these two files I will use it running as
administrator.  The program allows for GUI renaming and even has an editor.

Phil
Comment 55 Raphael Bircher 2010-10-27 19:46:27 UTC
Hi

I make a step by step how to wich describes how you can add the patch without
Commandline. You can find it on http://www.raphaelbircher.ch/computer_tagebuch.php

I hope it works.

Greeting Raphael
Comment 56 mnsteve 2010-10-28 00:42:38 UTC
I have downloaded and installed the two patched files and everything is working
fine for me.
Comment 57 pgaga 2010-10-28 01:15:47 UTC
I have installed and tested on multiple versions and all work fine.  Using the
terminologie extension for my immediate java test.

Phil
Comment 58 maks3w 2010-10-28 11:37:41 UTC
Don't work for me

Dyld Error Message:
  Library not loaded: @executable_path/../basis-link/ure-link/lib/libjvmfwk.dylib.3
  Referenced from: /Applications/OpenOffice.org.app/Contents/MacOS/soffice
  Reason: image not found
Comment 59 Raphael Bircher 2010-10-28 12:34:54 UTC
Two possibility for my point of view:

1)
You have a PPC and not a Intel based mac. The providet libs are for Intel and
not for PPC

2)
You run into right problems on your mac
Comment 60 mdxonefour 2010-10-28 12:46:54 UTC
According to http://support.apple.com/kb/HT4296, latest Java on PPC MacOS 10.5
is Java 1.5.0_26
Comment 61 maks3w 2010-10-28 18:07:06 UTC
Process:         soffice [39127]
Path:            /Applications/OpenOffice.org.app/Contents/MacOS/soffice
Identifier:      org.openoffice.script
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  launchd [241]

Date/Time:       2010-10-28 19:05:36.910 +0200
OS Version:      Mac OS X 10.6.4 (10F569)
Report Version:  6


MacBook PRO Unibody
Comment 62 maks3w 2010-10-28 18:19:10 UTC
Fixed.

When i downloaded the lib file with Google Chrome the browser duplicate the extension. 
(libjvmfwk.dylib.3.3

Removed the last .3 characters and open OOo

The fixed works fine to me too.
Comment 63 Raphael Bircher 2010-10-30 06:15:38 UTC
*** Issue 115228 has been marked as a duplicate of this issue. ***
Comment 64 Raphael Bircher 2010-10-30 06:16:12 UTC
close issue
Comment 65 Raphael Bircher 2010-10-30 06:17:20 UTC
Sorry, this was the wrong issue
Comment 66 Raphael Bircher 2010-10-30 06:18:05 UTC
Sorry, this was the wrong issue
Comment 67 Raphael Bircher 2010-10-30 06:19:25 UTC
reset to verified.
Comment 68 rbremer 2010-11-01 07:20:43 UTC
Solution worked for me. Thank you.

Ronny
Comment 69 r4zoli 2010-11-05 09:16:44 UTC
*** Issue 115421 has been marked as a duplicate of this issue. ***
Comment 70 r4zoli 2010-11-14 07:47:05 UTC
*** Issue 115569 has been marked as a duplicate of this issue. ***
Comment 71 howse 2010-11-16 20:00:28 UTC
With regard to the fix listed below (in this comment):

Thank you... I replaced the files and everything works great! Well done.


>>
>> comments from md Wed Oct 27 15:21:09 +0000 2010 
>>
>> For all those who like to get hands on the fixed libraries to try them out now,
>> please have a look at
>> http://wiki.services.openoffice.org/wiki/Documentation/FAQ/Platform/Mac_OS_X_10.6
>> There I put some information where to find the fixed libraries at least
>> temporarily for now and how to apply them manually.
>> 
>> Your feedback is welcome.
>> 
Comment 72 Raphael Bircher 2010-11-20 14:07:56 UTC
*** Issue 115444 has been marked as a duplicate of this issue. ***
Comment 73 ocke.janssen 2010-11-26 07:16:02 UTC
*** Issue 115793 has been marked as a duplicate of this issue. ***
Comment 74 Olaf Felka 2010-12-02 15:18:48 UTC
*** Issue 115564 has been marked as a duplicate of this issue. ***
Comment 75 Keith N. McKenna 2012-12-21 20:52:12 UTC
The FAQ's for OSX 10.5 and 10.6 still show this as an open problem. The only fix mentioned is to manually apply some new libraries. Was this ever resolved and is it still an issue with mac OSX.
Comment 76 Larry Gusaas 2012-12-21 21:29:53 UTC
(In reply to comment #75)
> The FAQ's for OSX 10.5 and 10.6 still show this as an open problem. The only
> fix mentioned is to manually apply some new libraries. Was this ever
> resolved and is it still an issue with mac OSX.

As the status states, the bug is verified and fixed. It was fixed with the release of OOo 3.3.
It was mentioned in several comments that the fix would be incorporated in OOo 3.3. The manually applied patch was for people using OOo 3.2.1 and older who had updated to the latest version of Java.

What FAQ's are you referring to?
Comment 77 Keith N. McKenna 2012-12-21 21:59:34 UTC
(In reply to comment #76)
> (In reply to comment #75)
> > The FAQ's for OSX 10.5 and 10.6 still show this as an open problem. The only
> > fix mentioned is to manually apply some new libraries. Was this ever
> > resolved and is it still an issue with mac OSX.
> 
> As the status states, the bug is verified and fixed. It was fixed with the
> release of OOo 3.3.
> It was mentioned in several comments that the fix would be incorporated in
> OOo 3.3. The manually applied patch was for people using OOo 3.2.1 and older
> who had updated to the latest version of Java.
> 
> What FAQ's are you referring to?

Larry the FAQ's in questtion are both here: http://wiki.openoffice.org/wiki/Documentation/FAQ/Platform. I only saw them as I am currently invloved in a consolidation of a number of sets o FAQ's in diferent places on the website into the mwiki structure. Along with this I am reviewing many of the current ones on the wiki for accuracy.

The status shows the bug as verified and fixed, not as closed, and though the comments do make mention of v3.3 as where it should be implamented, there is no clear indication that this happened, thus the question. If it has indeed been done I will change the FAQ's to state that the problem s resolved in newest release's. I do not have access to a mac so I appreciate the update.
Comment 78 Larry Gusaas 2012-12-21 22:41:11 UTC
(In reply to comment #77)
> The status shows the bug as verified and fixed, not as closed, and though
> the comments do make mention of v3.3 as where it should be implamented,
> there is no clear indication that this happened, thus the question. If it
> has indeed been done I will change the FAQ's to state that the problem s
> resolved in newest release's. I do not have access to a mac so I appreciate
> the update.

As I previously stated: "It was fixed with the release of OOo 3.3." Is that not clear? It was a show stopper for the release of 3.3 and the fix was applied and works in that release.

The FAQs for Mac OS X 10.6 state: 
"As reported in Issue 115180, latest Java 6u22 delivered via MacOS software update end of October 2010, breaks the Java configuration in OpenOffice.org 3.2.1 and earlier. OpenOffice.org 3.2.1 and earlier are unable to find the new Java."

That statement is correct. Newer versions than 3.2.1 find Java.
Comment 79 Keith N. McKenna 2012-12-21 23:04:28 UTC
(In reply to comment #78)
> (In reply to comment #77)
> > The status shows the bug as verified and fixed, not as closed, and though
> > the comments do make mention of v3.3 as where it should be implemented,
> > there is no clear indication that this happened, thus the question. If it
> > has indeed been done I will change the FAQ's to state that the problem s
> > resolved in newest release's. I do not have access to a mac so I appreciate
> > the update.
> 
> As I previously stated: "It was fixed with the release of OOo 3.3." Is that
> not clear? It was a show stopper for the release of 3.3 and the fix was
> applied and works in that release.
> 
> The FAQs for Mac OS X 10.6 state: 
> "As reported in Issue 115180, latest Java 6u22 delivered via Mac OS software
> update end of October 2010, breaks the Java configuration in OpenOffice.org
> 3.2.1 and earlier. OpenOffice.org 3.2.1 and earlier are unable to find the
> new Java."
> 
> That statement is correct. Newer versions than 3.2.1 find Java.

Larry as I previously stated the reason I ask the question is that the bug has never been formally closed. You answered that and I acknowledged your answer and thanked you or it. What I do not need is your condescending attitude. Thank you for the update and I will indeed update those particular FAQ's to reflect that the issue was resolved in a later release so that there is no potential for confusion in the future.
Comment 80 Larry Gusaas 2012-12-21 23:25:33 UTC
(In reply to comment #79)
> What I do not need is your condescending attitude. 
I posted that the bug was fixed. You then said "If it has indeed been done I will change the FAQ's"
I replied "As I previously stated: "It was fixed with the release of OOo 3.3." Is that not clear?"
If my repeating my previous answer when it seemed that you failed to comprehend it is seemed as condescending, Tough. 

Goodbye. I'm done with this.