Summary: | openoffice-ximian segment fault on "setup" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Zhang Weiwu <zhangweiwu> |
Component: | New packages | Assignee: | Gentoo Office Team <office> |
Status: | VERIFIED NEEDINFO | ||
Severity: | major | CC: | dmackie-lists-gentoobugs, gustavoz |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | Sparc | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Zhang Weiwu
2005-01-13 22:09:49 UTC
Could you please check if this could be your problem: http://bugs.gentoo.org/show_bug.cgi?id=73083 Andreas, I think, perhaps not. I am using dev-java/blackdown-jdk-1.4.1-r1 which is an earlier version than the one mensioned "working correctly" in #73083 The bug could be because of JDK, only I don't know how to make sure of it. I can hardly replace it with another JDK, I am on sparc, AFAIK blackdown-jdk is the only one. Do you suggest me emerge an older version and try again? No, blackdown should be fine. Could you try the advice in the bug I mentioned and see if the java path in /opt/OpenOffice.org/share/config/javarc is the correct one for your system? I recently committed regular openoffice-1.1.4 & openoffice-ximian-1.3.7 to ~sparc. They built just fine for me with java enabled, can you give one of those a spin? Also please post your emerge --info since, for example, ~sparc glibc is known to break blackdown-jdk. Thanks. Thank you for your suggestion Gustavo Zacarias. It will take me several days to emerge your version of openoffice, so I prefer first re-compile glibc (the same verison. I cannot recall if I compiled glibc-2.3.3.20040420-r2 with ~sparc, so I now re-emerge it without ~sparc), and try other people's suggestion, adjust jdk and so like. If all fails, I'll try your 1.3.7;) Basically glibc-2.3.4* is broken for blackdown on sparc, if you have glibc-2.3.3.20040420-r2 you don't need to re-emerge it. I have quickpkg'ed my openoffice builds if you wanna try those for a quick spin. Cool, Gustavo. The question is how do I get the package? By p2p or can you give me / mail me a link? Thank you. By the way, this morning I came back to the office and emerge glibc is finished, but bug is there still. http://dev.gentoo.org/~gustavoz/sparc/packages/ Download and place the one you want into /usr/portage/packages/All and use emerge -k. I prefer to emerge openoffice-ximian from source. I started to do it now, the result will be out the day after tomorrow. Because I am running gnome, emerge kde-env and kde-libs takes time too. I emerged your ~sparc xoo but now it failed with exactly the same error message. Andreas: I checked but this file on my box /opt/Ximian-OpenOffice/share/config/javarc Does not refer to anything like black-down, so I don't know how to follow your suggestion in 73083 Here is my javarc [Install] InstallationPath=. CPLD=0 AdditionalClasspath=<OFFICE_CLASSDIR>/classes.jar:<OFFICE_CLASSDIR>/sandbox.jar:<OFFICE_CLASSDIR>/ridl.jar:<OFFICE_CLASSDIR>/unoil.jar:<OFFICE_CLASSDIR>/jurt.jar:<OFFICE_CLASSDIR>/juh.jar:<OFFICE_CLASSDIR>/java_uno.jar:<OFFICE_CLASSDIR>/xt.jar:<OFFICE_CLASSDIR>/jaxp.jar:<OFFICE_CLASSDIR>/java_uno_accessbridge.jar:<OFFICE_CLASSDIR>/aportisdoc.jar:<OFFICE_CLASSDIR>/htmlsoff.jar:<OFFICE_CLASSDIR>/jmc.jar:<OFFICE_CLASSDIR>/minicalc.jar:<OFFICE_CLASSDIR>/pexcel.jar:<OFFICE_CLASSDIR>/pocketword.jar:<OFFICE_CLASSDIR>/XFlatXml.jar:<OFFICE_CLASSDIR>/xmerge.jar:<OFFICE_CLASSDIR>/XMergeBridge.jar: AdditionalJars=javaplugin.jar;plugin.jar RequiredVersion=1.4.1_01 [Java] Java=0 JavaScript=0 Applets=0 Another possible reason for setup crashing is a problem with one your fonts I think perhaps it's not a font problem. I only have one font that is not in Gentoo port tree (actually, I never emerged a font). And I removed that font and openoffice still crash. All my fonts are very common. Another idea: Do you have a mounted /proc filesystem? Yes I have. Currently I am adjusting CFLAGS and trying differen options (like -java and -O1). Each trial will take several days, and it's very close to Chinese new year, too many things to sort out, I would be very slow. However I will keep putting up my trial result in this bug tracker. There is nothing we can do without more info, please reopen if you get it again. I failed again. Error message attached. However, I am stupid enough to find that after compiled several days, that I am only compiling 1.3.5-r1 rather than expected 1.3.7 for wrong ACCEPT_KEYWORDS. I don't have much faith in try it again. I think I should just close this bug and install the binary Gustavo Zacarias provided. In case I need to compile it again and have problem again, I will reopen this bug to report further information? We are up to openoffice-ximian-1.3.8 in ~sparc starting yesterday night. I just finished uploading the quickpkg. Note that this one is built with mostly everything on, so it'll probably pull gnome & kde. Gustavo: Today I installed the pkg 1.3.7 you provided with URI, and again, it crashed with segment fault. I hope I am the only one who has this problem. Is it my system has some problem or triggered a hidden bug? Are you using some locale/LINGUAS different than the default? Just curious, i just use english and haven't had any problems. You are right I guess! I login as root where root LOCAL is set to en_US, and openoffice launched successfully. Currently I am using zh_CN.UTF-8 /home/zhangweiwu> locale LANG=zh_CN.UTF-8 Any further suggestions? I must use zh_CN and I already have tone of file and documents in UTF-8, so I dislike to move to zh_CN.GB18030 or other locale. And I heard some people are using zh_CN in UTF-8 under the zh_CN.EUC locale. Not sure if it's true. Nope. I failed again. With segment falult It seems only root can run xopenoffice. I currently run openoffice fine with a sudo to root. Run xopenoffice in any other users, even if locale is English, it fail with segment fault. this doesn't work and still produce seg fault. mv -r /root/.xopenoffice /root/.xversionrc /home/zhangweiwu As openoffice-2.0.0 is now marked ~sparc could you please try with this and report back if it works now, should generally go a lot better than older versions Shouldn't be a problem anymore with 2.0.0, also would need some feedback, otherwise there is nothing we can do The bug should be closed because I only meet this bug on sparc with 1.x but now my sparc is broken and I don't use 1.x anymore, thus not being able to reproduce this bug. |