Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi,

On Tue, Apr 19, 2011 at 23:06, Manfred J. Krause wrote:
2011/4/19 Vojta Kasalický wrote:
Hi, I have the same problem as sid32. Vojta K.

   * Subject: [libreoffice-users] 3.4Beta loading error - Ubuntu
   * From: sid32 <sid32@mailinator.com>
   * Date: Fri, 15 Apr 2011 12:52:33 -0700 (PDT)
   * To: users@libreoffice.org

Running ubuntu 10.10. Uninstalled libreoffice 3.3. Downloaded the new 3.4
beta US debs.

Installed Lib0_3.4 and the Lib0_ure files and now when I try to launch
libreoffice from the command line I get:

/opt/libreoffice/program/oosplash.bin: symbol lookup error:
/opt/libreoffice/program/oosplash.bin: undefined symbol:
sal_detail_initialize, version PRIVATE_1.1

Any Ideas?

I remember
Bug 36275 - LibO 3.4b1 fails to start with "symbol lookup error"
https://bugs.freedesktop.org/show_bug.cgi?id=36275 [...]

Bug 36275 will be fixed in LibO 3.4 RC1 [next build]
Status: RESOLVED FIXED [2011-05-03]

See also: Bug 36257 comments #23 and #27
https://bugs.freedesktop.org/show_bug.cgi?id=36275#c27

mjk

-- 
TDF Planet
http://planet.documentfoundation.org/

-- 
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.