Comment # 7 on bug 918221 from Axel K�llhofer

(In reply to Axel K�llhofer from comment #5)

> I will also try to remove all packages of libreoffice, try to find and
> remove all possible "leftovers" and see what happens.
> 

(In reply to Wolfgang Bauer from comment #6)

> In particular I would check/remove /usr/lib/libreoffice, /usr/lib64
> /libreoffice, and /usr/share/libreoffice (and of course /usr/share/templates).

DAMN!

This did the trick on two (sic!) systems, on the second one I am 100% sure
loffice has never been installed from OSS-Repo as I installed the packages
months after system had been set up.

The really odd thing, on both systems removing libreoffice-packages gave
additional output like this:

Zus�tzliche rpm-Ausgabe:
ls: cannot access /usr/lib//libreoffice/share/config/soffice.cfg/fps/ui/res/*:
No such file or directory
ls: cannot access
/usr/lib//libreoffice/share/config/soffice.cfg/modules/dbreport/ui/res/*: No
such file or directory
ls: cannot access
/usr/lib//libreoffice/share/config/soffice.cfg/modules/sabpilot/ui/res/*: No
such file or directory
ls: cannot access
/usr/lib//libreoffice/share/config/soffice.cfg/modules/sbibliography/ui/res/*:
No such file or directory
ls: cannot access
/usr/lib//libreoffice/share/config/soffice.cfg/modules/spropctrlr/ui/res/*: No
such file or directory

Zus�tzliche rpm-Ausgabe:
ls: cannot access /usr/lib//libreoffice/program/resource/*: No such file or
directory
ls: cannot access /usr/lib//libreoffice/share/registry/res/*: No such file or
directory

as if some files were missing although I certainly did not remove them
manually.

Maybe on updating from Loffice (4.2.X to 4.3.X something went wrong while
running post-install/post-update scripts?

Additionally, there actually were some "leftovers" in /usr/lib(64)/libreoffice
and I removed those ones manually (without having a closer look at the files
themselves, actually a really dumb idea of mine. If there were other users
having the same problem, they will not have really good clues on what really
might cause their problem).

Great, in a nutshell this means "much ado about nothing" from my side, if there
really was a bug involved (which one can doubt now), then it will be nearly
impossible to reproduce.

I�m sorry Wolfgang, seems like this thread will not be of any real use for
anybody and just wasted some of your time.

Greetings,

AK