Apache OpenOffice (AOO) Bugzilla – Issue 6585
I18N: Operating system doesn't support locale ""
Last modified: 2003-03-13 10:23:26 UTC
I just installed OOo on my MAC Powerbook G4 (OS 10.1.5). Instasllation went without problems, but following the directions at the end of the Installation, I set the environment varibales, and ran sh soffice in an xterm (I use OroborOSX to lauchch Xdarwin -- had no probnlems with 638!). The result was: % sh soffice soffice: no such file or directory: /usr/bin/test [89] I18N: Operating system doesn't support locale "" Abort Am I missing something? Is there a second phase of installation which sets a locale variable?
I also tried the launching scripts -- they don't do anything. Anyway, OS 10.2 will be available only after August 24. If OOo depends on a prerelease version of the OS, this should be stated explicitly (and the installer should check on the verion of OS X installed!). I also noticed that the "test" program resides in /bin/test not /usr/bin/test.
Hi, Once idea: try the following: setenv LANG en_US This sets that language to en_US which might help it properly detect the proper locale to use. AFAIK, this build was done using 10.1.5 (nothing from 10.2). Kevin
Thanks Kevin, LANG was set to en, I reset it to en_S -- dosn't help. I can't find any "locale" in my installation of Darwin/Xdarwin. The only mention of locale is in a perl script. What is calling the I18N stuff? What is the Darwin equivalent of ldd. It's been a while since I used NeXTStep ....
Hi, Here is a complete WAG: Maybe the script needs the "test" to get things working. As root, create a symbolic link from /bin/test to /usr/bin/test. cd /usr/bin ln -s ../../bin/test ./test That should create (it does under Linux anyway) a symbolic link so that the invocation of /usr/bin/test will work. Again, this is all a wag, I am still downloading it (all 160 meg of it). Sorry I can't be more help. Kevin
The same here: I18N: Operating system doesn't support locale "" Abort If I do unsetenv LANG the I18N-message vanishes, but the application still Aborts as above And the missing /usr/bin/test is not the problem, I patched to soffice-script to use /bin/test, but still no success
Over to Ed P. since he's the project lead for MacOS X/Darwin port.
Hi, Meinhard, what window manager are you using? And did you install X11 from fink or from the OpenOffice.org installer? What's your command sequence when launching from the terminal, without the AppleScript helpers? it should go like this: 1) Open terminal window 2) setenv DISPLAY localhost:0 3) setenv DYLD_LIBRARY_PATH /<your install location here>/program:/<your install location here>/program/filter:/usr/X11R6/lib 4) sh /<your install location here>/program/swriter This is what we all use for normal launching from the terminal. Dan
Oh, I don't think Ed or I have run into any problems iwth the "missing" /usr/bin/test, its just been such a low priority that we haven't gotten to it. I'm filing an issue for it if there isn't one already. Dan
1. /usr/bin/test is not the problem -- I symlinked it to /bin/test, but the I18N problem does not go away. 2. I looked in /usr/share/locale. Darwin (or OS 10.1.5) seems to have installed all but en and en_US subdirectories. But seting LANG=de or fr, did not help either. 3. I am running OroborOSX-vo8b. OOo638c ran OK under it. Was I supposed not to start Xdarwin before launching OOo1.0 ? The documentation does not say that or that OOo installs "its own" X11R6 --- it shouldn't overwrite any existing installation. Fortunately my xemacs-2.4.8 still works (as well as Abiword). 4. Yes I did set all the environment variables as described in Dan's post, but in an xterm -- not the Terminal, since I assumed that X should be running before stasrting up OOo. Will try the "terminal startup" and report back.
I tried starting from Terminal, as suggested by Dan. Here is the response: sh soffice I18N: Operating system doesn't support locale "" /Applications/OpenOffice.org1.0/program/soffice.bin: cannot open display "localhost:0" Please check your "DISPLAY" environment variable as well as the permissions to access that display. (See "man X" resp. "man xhost" for details) I tried xhost+ (and sudo xhost+) but since X is not running the DISPLAY localhost:0 is not recognized. Should I start X and then do everything from the terminal?
Wait... Are you running XDarwin rootless or rooted? Or are you running Darwin as opposed to MacOS X? The terminal start procedure requires an X server to be running before you do the stuff. Sorry about that. Try that. Dan
Progress report: I started Xdarwin "by hand" with % X -quartz & [2] 380 [8:51]rita@ip68-5-253-27{OpenOffice.org1.0/program}72% 2002-07-26 08:51:22.688 XDarwin[380] XDarwin 1.1 Running in parallel with Mac OS X Quartz window server. XFree86 Version 4.2.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 January 2002 If the server is older than 6-12 months, or if your hardware is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: Darwin Using keymapping provided in /System/Library/Keyboards/USA.keymapping. _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root Display mode: Rootless Quartz Screen 0 added: 1152x747 @ (0,21) Screen 0 placed at X11 coordinate (0,0). Then tried %sh soffice I18N: Operating system doesn't support locale "" Display can do XRender, but no installed. Please install for improved display performance zsh: command not found: lpstat zsh: no such file or directory: /usr/sbin/lpc Using keymapping provided in /System/Library/Keyboards/USA.keymapping. Display mode: Rootless Quartz Screen 0 added: 1152x747 @ (0,21) Screen 0 placed at X11 coordinate (0,0). Abort 11.760u 4.190s 0:42.03 37.9% 0+0k 371+68io 0pf+0w ---- COMMENTS: The system I have uses lpd and therefore lpstat should be lpq; and lpc resides in /usr/bin/lpc not /sbin/lpc. What installation of Darwin was used in the soffice script? When I run OroborOSX instead of X -quartz I get back the initial Abort.
I was running rootless -- and the OOo splash appeared before it aborted.
All of us (well, I can speak for Ed and me) are running 10.1.5 (Darwin 5.5?) and using XDarwin. I actually think Ed might be using OrborOSX. I use sawfish for window manager. We both run rootless and use the Terminal (not an Xterm) to launch applications. IE start XDarwin and then do the setenv stuff in the terminal and then launch the app. We've both installed all our X11 stuff from the distro included with the installer. AFAIK the problems with lpq/lpstat shouldn't make a difference (you won't be able to print I don't think then) for running the program, that won't make it abort. Do you have XDarwin around? Can you try that instead of X from the terminal or OrborOSX? Dan
Some progress: I unsetenv DISPLAY, started X -quartz rootless, setenv DISPLAY localhost:0 and then sh soffice. Lo and behold writer started up OK, but the fonts look terrible. Also, since I am not running a window manager, the windows are not resizable, the Addressbook screnn can't find my Mozilla adressbook (not a big deal). On the other hand, printing did work right away (to thedefault printer of lpd, which is an epson connected to my Linux box (wireless network). I will try to start up twm and then soffice. And where do I find XRender which OOo complains about?
Hi, Great!! Font rendering will look a bit off :) You don't have antialiasing becasue Xrender isn't around. Actually, you do have libXrender, its in /usr/X11R6/lib, but it won't load. Furhtermore, if you add /usr/X11R6/lib to your DYLD_LIBRARY_PATH it will find libXrender, but won't load it. We're still working on that, its part of the printing implementation that's being worked on by me right now in my (nonexistent) spare time :) Do you get hardcopy from the printer? I've never been able to test it as I don't have a networked printer... Dan
I am not used to twm -- haven't ever used it (used mwm, fvwm, and most recently sawfish), but I managed to get resizable windows. I managed to get 1 page of hardcopy, then my lpd seems to have died, (on a networked printer). And when this happens, writer sweems to be frozen (i.e., none of the menus work). I was able to open the one or two .doc files I have around; will try a spreadsheet and a presentation (or whatever it's called) next. I also managed to start up writer, calc, etc by clicking on the Applescripts when twm was running. OroborOSX -- which is a nicer window manager, seems to load an Xserver which is not compatible with OOo. Will play with it some more -- I may have to reboot to get printing to work again.
After rebooting lpr works again, but only once. After printing the menus (and everything else) in OOo seems locked. This is a serious bug and needs attention. Saving seems to work. There is no way of exiting OOo without an explicit kill! ------- Here is the way I start up Ooo. I should try to mkae this into a shell-script. 1. In Terminal % Xdarwin -quartz& % twm & % setenv DISPLAY localhost:0 % setenv DYLD_LIBRARY_PATH /Applications/OpenOffice.org1.0/program % setenv /Applications/OpenOffice.org1.0/progam/filter:/usr/X11R6/lib Then you can click on any of the applescripts to start up writer, calc, impress, or draw. The applescripts don't always exit graciously, so starting OOo from a shell may be the better option.
The AppleScripts already do the environment variable setting for DISPLAY and DYLD_LIBRARY_PATH and stuff, but if your config is different, you may need to adjust them. The sequence should be: 1. In Terminal % Xdarwin -quartz& % twm & % setenv DISPLAY localhost:0 % setenv DYLD_LIBRARY_PATH /Applications/OpenOffice.org1.0/program:/Application s/OpenOffice.org1.0/progam/filter:/usr/X11R6/lib Dan
I can confirm the contrast between Oroborus 0.8b and raw X + twm. The former exits with an abort, the latter runs (opened an HTML and an RTF file - nice!). Same problems with location of test, lpc, etc. Running 10.1.5 on a B&W G3.
I think the lpd lockup is due to OOo creating a Lock file and not removing it after the print job is finished. I logged in as another user, stopped and started the print queue from the Print Center, and one of the OOo Draw pages which were queued suddenly printed. Alos, the only way to get OOo to work as another user, was to copy the .sversionrc file over to the other home directory. Before that OOo popped up the big blue setup screen, but since there is no setup binary did nothing. As soon as I find out what's going wrong with the lpd, I'll file a separate issue.
Hi, The issue with lpd is in fact some core component of OOo that's not doing its job. We are actually getting a SIGSEGV during the EndJob() routine in printer handling. This is caused by some illegal memory access which I haven't tracked down yet. Anyway, our signal handler gets called but already we're up a creek. So the signal handler tries some cleanup but ultimately ends up calling pthread_mutex_lock () during the release of memory of a string during cleanup... I don't think its lpd's fault :) In any case, I'm still working on printing support and once I get a more final set of patches out then I'd say file another issue for printing... Dan
I would suggest opening a new issue, because there is a problem with the OroborosX v0.8 window manager. It is due to the window manager, and not OroborosX's "tweaked" XDarwin, because you can start standard XDarwin, kill twm, start OroborosX as the wm, and still see the problem (but it works OK with twm). OroborosX is fairly popular, so a notice on the download page may be appropriate. We should also let Adrian know about this problem. Here's the stack trace from the abort - can anyone narrow this down? Program received signal SIGABRT, Aborted. 0x7001a70c in kill () (gdb) where #0 0x7001a70c in kill () #1 0x7006f990 in abort () #2 0x00e8fb88 in XError__7SalXLibP9_XDisplayP11XErrorEvent () #3 0x00e8f254 in sal_XErrorHdl () #4 0x011788ac in _XError () #5 0x01177130 in _XReply () #6 0x011629c4 in XGetWindowProperty () #7 0x00e9ecf8 in __Q27vcl_sal14GnomeWMAdaptorP10SalDisplay () #8 0x00e9e158 in createWMAdaptor__Q27vcl_sal9WMAdaptorP10SalDisplay () #9 0x00e91d10 in Init__10SalDisplayUlPC11XVisualInfo () #10 0x00e90d04 in __10SalDisplayP9_XDisplayP6VisualUl () #11 0x00e8f994 in Init__7SalXLibPiPPc () #12 0x00e8f694 in Init__7SalDataPiPPc () #13 0x00e97e70 in InitSalMain__Fv () #14 0x00d17640 in InitVCL__FRCQ53com3sun4star3unot9Reference1ZQ53com3sun4star4lang20XMultiServiceFactory () #15 0x00d174e0 in SVMain__Fv () #16 0x00e8f190 in main () #17 0x000026a8 in _start () #18 0x000024d8 in start ()
I replaced twm by fvwm-1.24 (which i had used before) and am pleased to report that OOo works fine with it (even in full-screen mode). I can start it from a menu on the middle mouse button, etc. I don't think it can woork in rootless mode.
1. Fvwm-1.24 also works in rootless mode (except for mouse-menus in the finder-root-window, and pager). 2. As proposed by Sean, the OroborOSX should be a new issue. As far as I can tell, this one is "exhausted."
Since the OroborOSX-08 has become issue 6635 now, and OOo works fine under XDarwin+fvwm -- I propose changing to WORKSFORME now.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.