Bug 458952

Summary: upstream openoffice extensions do not work
Product: [openSUSE] openSUSE 11.1 Reporter: Felix Möller <felix>
Component: OpenOffice.orgAssignee: Petr Mladek <pmladek>
Status: RESOLVED FIXED QA Contact: Ke Yu <kyu>
Severity: Normal    
Priority: P2 - High CC: fstrba, kendy, mmeeks, novell, pmladek, rgb.mldc
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Felix Möller 2008-12-14 09:53:29 UTC 
I just spend some time trying to install an upstream openoffice extension, but this did not work.

Doing my research I found bug #411669.

I think this limits openoffice severely. If you do not support them please indicate this somehow.

/usr/lib/ooo3/program/unopkg.bin gui

starts the extension manager without a warning. How is a casual user supposed to now this is not working at all?

In the new splash screen there is even a button to get extensions!

I could solve the following by adding my ldlibrary path
        libuno_cppuhelpergcc3.so.3 => not found
        libuno_cppu.so.3 => not found
        libuno_sal.so.3 => not found

but where is libstlport_gcc.so? Is it not there at all anymore?

The german Duden (german spelling book) is going to release an openoffice spellchecking plugin. Hopefully all third party vendor remember to compile a suse version...
Comment 1 Petr Mladek 2009-01-12 19:11:28 UTC 
I agree that we should show a warning and clean up all the dialogs.

Jan, any chance you could look at it?
Comment 2 Felix Möller 2009-01-12 19:53:59 UTC 
From a user's perspective this is really a problem. Could anybody imagine Firefox not being able to load the upstream extensions?

I do not know the technical background of this decision, but please think about it thoroughly.
Comment 3 Petr Mladek 2009-05-14 09:34:55 UTC 
Hmm. we really have to improve the compatibility with upstream. Clearly, we can't rebuild every extension ourself, ... For example, see the bug #478626.

It is too late for OOo-3.1.

I think about to enable stlport for OOo-3.1.1. We will see if it helps...
Comment 4 Fridrich Strba 2009-05-15 09:20:39 UTC 
OK, so I tried the workaround, and installing the stlport on the system makes the upstream extensions work. I tried with the pdfimport extension and it was importing happily.
Now, one can download the stlport library for major rpm-based distributions here:
http://download.opensuse.org/repositories/home:/fstrba:/stlport/

So, as a workaround, this is there.
Comment 5 Ricardo Gabriel Berlasso 2009-06-07 12:22:59 UTC 
Not sure if this belongs here or I may open a new issue, but I'm having problems with OOoLatex extension on 3.1:
http://ooolatex.sourceforge.net/
It works without a problem on Sun build, but on Novell's build it fails with a "basic runtime error".
I tried to build stlport (I'm on a 64 bits system) but the build fails.
Comment 6 Fridrich Strba 2009-06-07 19:20:58 UTC 
Now, if you are on 64-bit system, no upstream release for that system is using stlport. Are you sure you are not installing 32-bit extension on 64-bit system with 64-bit OOo?

Alternatively, if you need the latex export you can use our community GoOo build that is available at http://go-oo.mirrorbrain.org/stable/linux-i586/
Just pick the http://go-oo.mirrorbrain.org/stable/linux-i586/GoOo-release-0.0.3-0.noarch.rpm and install it, it will add this repo to your zypper sources.

That release is a 32-bit build that runs well on 64-bit systems too. If you don't install desktop integration, it can easily coexist with openSUSE version (although they cannot run in the same time). Just launch it using /opt/openoffice.org3/program/soffice

Get back to us with feedback
Comment 7 Ricardo Gabriel Berlasso 2009-06-07 21:14:42 UTC 
OOoLatex allows you to insert LaTeX equations inside Writer/Impress documents. They look better than Math ;)
Thanks for clarifying me about stlport.
OOoLatex is written in starbasic and call tex and gs. As I said, the same extension work out of the box with 64 bits Sun build so it is not a 32/64 bits problem.
Comment 8 Petr Mladek 2009-06-08 09:48:32 UTC 
Ricardo, it might be also related to our changes in the StarBasic/VBA code. Could you please rather open a separate bug for this?
Comment 9 Ricardo Gabriel Berlasso 2009-06-08 12:15:28 UTC 
Reported here:
https://bugzilla.novell.com/show_bug.cgi?id=510894
Comment 10 Petr Mladek 2009-06-23 15:43:40 UTC 
I have created the libstlport_gcc4 and hacks in OpenOffice_org-ure to create the compat symlinks. The upstream PDF import extensions works here with the openSUSE OOo-3.1 build now.

You might try the packages in the OpenOffice.org:UNSTABLE project, see
http://en.opensuse.org/Additional_YaST_Package_Repositories#OpenOffice.org_UNSTABLE

IMPORTANT: You temporary need to install also libstlport_gcc4-devel. It will not be needed since OOo-3.1-alpha2 that will create the compat symlinks.

I am going to commit it into Factory and OpenOffice.org:STABLE project.

I am going to close this bug as FIXED now. Feel free to reopen it if you still see the problems in the future.

PS: Many thanks to Fridrich for the hint with the stlport package.
Comment 11 Petr Mladek 2009-06-24 14:38:11 UTC 
*** Bug 478626 has been marked as a duplicate of this bug. ***