Bug 807025 - libreoffice-writer fails to start with version
libreoffice-writer fails to start with version
Product: Fedora
Classification: Fedora
Component: libreoffice (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Caolan McNamara
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-03-26 15:25 EDT by Scott Williams
Modified: 2012-03-28 23:52 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-03-28 23:52:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Scott Williams 2012-03-26 15:25:26 EDT
Description of problem:

Libreoffice writer fails to start with following error on f16:

WARNING: couldn't connect to: /tmp/keyring-IKJACy/pkcs11: No such file or directory
/usr/lib64/libreoffice/program/soffice.bin: symbol lookup error: /usr/lib64/libreoffice/program/../basis-link/program/libswdlx.so: undefined symbol: _ZN16SfxFilterMatcherD1Ev

Reinstalling version did not fix, but downgrading to 1: did.

Version-Release number of selected component (if applicable):


How reproducible:

Every time

Steps to Reproduce:
Open any text document with libreoffice or simply call libreoffice-writer.
Splash screen appears briefly, then disappears.  

Actual results:
Libreoffice-writer does not successfully open.

Expected results:
Libreoffice-writer should succesfully open and load documents

Additional info:

Arch is x86_64
Comment 1 Caolan McNamara 2012-03-27 06:44:08 EDT
x86_64 libreoffice-writer- starts here without problem, if it was a global problem I'd expect to be flooded with bug reports, so I think this is something specific to your local install.

does allowing yum upgrade to re-upgrade to libreoffice-writer- still result in epic-failure to launch ?
Comment 2 Scott Williams 2012-03-28 23:52:02 EDT
Upgrading again to the current version works.  Closing bug.  Thanks!

Note You need to log in before you can comment on or make changes to this bug.