Problem description: Steps to reproduce: 1. click "Tools" 2. click "Extension Manager" 3. "English spelling dict..." 4. click "options" Current behavior: program crashes. On command line; $ /usr/local/opt/libreoffice3.5/program/soffice.bin: symbol lookup error: /usr/local/opt/libreoffice3.5/program/../program/libpyuno.so: undefined symbol: PyUnicodeUCS2_FromUnicode Expected behavior: Not crashing... Platform (if different from the browser): Debian Squeeze (Stable) Browser: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20100101 Firefox/12.0 Iceweasel/12.0
installed packeges: LibO_3.5.3_Linux_x86_helppack-deb_en-GB.tar.gz LibO_3.5.3_Linux_x86_install-deb_en-US.tar.gz LibO_3.5.3_Linux_x86_langpack-deb_en-GB.tar.gz
I'm new here so not sure how to report this... I'm unable to start LibreOffice at all. Attempting to run each of sbase, scalc, sdraw, simpress, smath, soffice, swriter, or soffice.bin from a bash shell in the /opt/libreoffice3.5/program/ directory always produced the splash screen for a moment then failure with the following error printed out on the command line: /opt/libreoffice3.5/program/soffice.bin: symbol lookup error: /opt/libreoffice3.5/program/../program/libpyuno.so: undefined symbol: PyUnicodeUCS2_FromUnicode I'm using Puppy Linux 528 Lucid, which is a variant based on Ubuntu Lucid Lynx. Initially installed from Puppy package: LibreOffice-3.5.1-en_us-2.sfs Then when it failed with that error I tried: LibO_3.5.3_Linux_x86_install-rpm_en-US.tar.gz LibO_3.5.3_Linux_x86_helppack-rpm_en-US.tar.gz That failed with the same error message.
The same crash when opening any ms-word document
Same happens to me on Centos 6.2 (the lookup-error). The way I can usually fix this is by export LD_LIBRARY_PATH=/opt/libreoffice3.5/program/:$LD_LIBRARY_PATH or with unset LD_LIBRARY_PATH So it is a pure library-lookup-problem and only happens if the user has LD_LIBRARY_PATH set. Would be nice if the installation was tolerant in this respect
In potuguese(do Brazil): helo,fiz download do LibreOffice 3,5.3 , anteriromente usava um LibreOffice3.4 ,e a configuração da página do editor de texto não9 sei como fazer para fazer minha mnografia,MAS o mais grave agora é que após instalar e reinstalar,um só e mesmo prloblema se apresenta, não visualizo o fundo branco do editor,esta parte fica,eu olhando,do lado direito meio escondido,e não fica centrado por nada que já tenha eu feito,foi isso, não sei como fazer para usar meu editor de texto ou writter,do LibreOffice 3.5.5.3.Thanks,Ricardo Loureiro Junger.
In potuguese(do Brazil): helo,fiz download do LibreOffice 3,5.3 , anteriromente usava um LibreOffice3.4 ,e a configuração da página do editor de texto não9 sei como fazer para fazer minha mnografia,MAS o mais grave agora é que após instalar e reinstalar,um só e mesmo prloblema se apresenta, não visualizo o fundo branco do editor,esta parte fica,eu olhando,do lado direito meio escondido,e não fica centrado por nada que já tenha eu feito,foi isso, não sei como fazer para usar meu editor de texto ou writter,do LibreOffice 3.5.5.3.Thanks,Ricardo Loureiro Junger. /ricardoljunger@gmail.com
After udate cannot print the correct size. drawing are all printing in the left top corner This is a massive problem for us
Seems like python configuration error. Did you try advice from comment 4?
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
*** Bug 50538 has been marked as a duplicate of this bug. ***
It seem to be related to the LD_LIBRARY_PATH setting as described in the comment #4.
Any update with recent LO version (4.2.4 or 4.1.6 for example)? Indeed, Python version has been upgraded to 3.X for quite a while.
No feedback since 6 months, I put it as WFM.