Apache OpenOffice (AOO) Bugzilla – Issue 10210
Unresolved symbol in libsal.so.3
Last modified: 2013-08-07 15:12:47 UTC
If I try and import excel spreadsheets OOo crashes with the following console output: /opt/OpenOffice.org643/program/soffice.bin: relocation error: /opt/OpenOffice.org643/program/libsvx643li.so: symbol _ZN7EditDocC1EP11SfxItemPool, version UDK_3_0_0 not defined in file libsal.so.3 with link time reference
Hi Christian, Sascha told me it could be yours. Frank
Owen, Please attach this Excel file.
Problem just happened again this time trying to load two Word documents so this maybe a Framework issue. As soon as it happens with a document which is no deemed company confidential I'll attach it.
target->OOoLater
I just stumbled on this again : after a bit of work in writer (satisfying), an some research in a Postgres database (*quite* satisfying with the unixODBC drivers and driver manager, not so much with the native Postgres driver ...), I wanted to open a new spreadsheet. OOo 643c died with : /opt/OpenOffice.org643/program/soffice.bin: relocation error: /opt/OpenOffice.org643/program/libsvx643li.so: symbol _ZN7EditDocC1EP11SfxItemPool, version UDK_3_0_0 not defined in file libsal.so.3 with link time reference It might be another problem (libc6 2.1.3-13 as of Debian unstable, xlibs 4.2.1-5 (same source)). It could be a problem with the application frame, as already suggested (I filed another issue with 644_m1, which cannot start at all on my setup ...). I suggest to raise the priority of this issue : something smells of a serious problem with build tools or platform ... And, BTW, could someone *confirm* this ?
I have this problem on * saving writer document * creating calc document
@ALL: I guess those of you who have problems are using linux distros with glibc 2.3.1. Am I right? This is a problem of the glibc which the GNU team fixed in glibc 2.3.2. Peter @DR: #107277#
You are right. Works fine with glibc 2.2.5
DR->PJ: No Excel filter problem, reassign to you.
Hi, due to this is probably not our problem I close this one. Peter @Emmanual: Yes, can confirm this. You're right that it's a serious platform problem because glibc 2.3.1 is buggy.
-> Closed
*** Issue 11695 has been marked as a duplicate of this issue. ***
*** Issue 13242 has been marked as a duplicate of this issue. ***
*** Issue 10186 has been marked as a duplicate of this issue. ***
*** Issue 13577 has been marked as a duplicate of this issue. ***
*** Issue 13758 has been marked as a duplicate of this issue. ***
*** Issue 15819 has been marked as a duplicate of this issue. ***
*** Issue 15578 has been marked as a duplicate of this issue. ***
*** Issue 16106 has been marked as a duplicate of this issue. ***
*** Issue 16865 has been marked as a duplicate of this issue. ***