Apache OpenOffice (AOO) Bugzilla – Issue 91224
suse menu integration for 2.4.1 crashes opensuse 10.2
Last modified: 2008-07-10 06:47:28 UTC
Installing the suse-integration RPM for 2.4.0 on my suse 10.2 system causes OOo to continually carsh! :( I removed this RPM and now I can use the app at least, but darn!, no menu integration. Needless to say, I've installed many versions of OOo and used the suse menu integration RPM and have never had this happen. Please correct.
Created attachment 54900 [details] OOo main starter script for Linux
Created attachment 54901 [details] uno script for OOo for Linux
I just uploaded two corrected versions of ../program/soffice and ../programs/unopkg. Both of these scripts reference shell scripts which are no longer provided with the 2.4.1 packaging. This was causing OOo to crash repeatedly on my Linux box. I have changed this to 2.4.1 instead of 2.4.0 as well to be accurate.
@ jl & obr: Please have a look at the attached files. Is this something that might be valid for OOo3.0?
IIRC the sopatchlevel.sh has always been Solaris only. Also the proposed patch has nothing to do with the suse-menus integration package. My guess would be that `pwd` is unable to determine the current working directory for some reason (e.g. due to permission problem or because the working directory of the shell has moved). Do you have some strace or 'set -x' output you could attach ?
Some clarification. What I attached were towo script files, VERBATIM, from the suse-integraion menu scripts packaged with OOo 4.1. commented out a small section, beginning with the letters KLS, that was, in my opinion, causing them to hang/crash because the referenced script, sopatchlevel.sh, as you point out, is not found, and thus the "exit". My point is that this section should be REMOVED from the suse-menu integration menu scripts, i.e. these two scripts. If this is done, as I did on my system, the crashing problem no longer occurs. I installed this version of OOo the same as I always do, so this is very odd to me.
The scripts you changed are not in the suse-menus package, but in some core0? package. And the exit statement you commented out should never be reached when there is no sopatchlevel.sh (that's what if [-x "$sd_prog/sopatchlevel.sh" ]; then is for). There must be something else going on. Please remove the comment marks you added again and also the one before the 'set -x' . Then run soffice from a terminal and attach the output.
Your comment is not correct. I did an rpm install of the suse-menu package, did an rpm query to see what it did, and these scripts were included. Check out the rpm yourself. They may also been in one of the core packs but the scripts were then overwritten with the suse-meu install.
> rpm -q --queryformat '[%{FILEMODES:perms} %{FILENAMES} -> %{FILELINKTOS}\n]' -p OH680_m17_native_packed-1_es.9310/RPMS/desktop-integration/openoffice.org-suse-menus-2.4-9268.noarch.rpm | grep soffice lrwxr-xr-x /usr/bin/soffice -> /etc/openoffice.org2.4/program/soffice > rpm -q --queryformat '[%{FILEMODES:perms} %{FILENAMES} -> %{FILELINKTOS}\n]' -p OOH680_m17_native_packed-1_es.9310/RPMS/desktop-integration/openoffice.org-suse-menus-2.4-9268.noarch.rpm | grep unopkg lrwxr-xr-x /usr/bin/unopkg -> /etc/openoffice.org2.4/program/unopkg => The only 'soffice' and 'unopkg' contained in the *-menus packages are symbolic links. Also /etc/openoffice.org2.4 is a symbolic link created at install time, so the only real instances of those files are the ones delivered with the core package.
OK, obr--point taken. I just this morning was forced to go back to 4.0, which gave me no troubles. The crash docs generated seemed to indicate a failure with one of the UI libraries for 4.1., so my sending the tickets off should clue someone in. My best guess at this point is the mismatch in builds (9286 for the menu integration, 9310 for the product). Really, I'm not a developer so I couldn't say for sure, but 4.1 was CONTINUALLY crashing no matter what. Anyway, thanks fo ryour time on this. But clearly things are mismatched here!
Thank you for your report. Your last comment about your problem makes me think what you have faced might be yet another variant of Issue 89718 (introduced with support for libXrandr.so). *** This issue has been marked as a duplicate of 89718 ***
Note that the fix for issue 89718 is not in OO.o 3.0 Beta 1, but will be in any release candidate and/or subsequent Beta releases (if any). Please consider testing one these builds to make sure your problem is fixed there as well. Feel free to re-open this issue if you are still able to reproduce the problem with one of those builds.