Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 91606 - Load FAILED with error: libchrome.so:No such file
Load FAILED with error: libchrome.so:No such file
Product: Red Hat Linux
Classification: Retired
Component: openoffice.org (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dan Williams
Depends On:
  Show dependency treegraph
Reported: 2003-05-25 15:51 EDT by d. johnson
Modified: 2007-04-18 12:54 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-02-04 22:17:17 EST
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 d. johnson 2003-05-25 15:51:27 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030512

Description of problem:
% ooffice foo.xls
Checking for existing user installation ...   ...   NOT FOUND
Performing first-time installation for user ...   ...   DONE
Starting OpenOffice.org ...
GetFactory(/usr/lib/openoffice/program/components/libchrome.so) Load FAILED with
error: /usr/lib/openoffice/program/components/libchrome.so: cannot open shared
object file: No such file or directory

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

How reproducible:

Steps to Reproduce:
1. Load oofice for the first time under any user
2. Wait ...
3. Above message is displayed after it finishes loading

Expected Results:  It should not be looking for a lib that oofice doesnt include.

Additional info:
Comment 1 Dan Williams 2003-12-05 15:32:26 EST
Wierd.  Does this happen with 1.0.2?
Comment 2 d. johnson 2003-12-05 16:21:30 EST
This bug was reported so many months ago that I have since upgraded to
1.1.0-6, and no longer have this issue.
Comment 3 Dan Williams 2004-02-04 22:17:17 EST

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