Bug 68412 - Cannot access Bonobo/ConfigDatabase on womnat:
Cannot access Bonobo/ConfigDatabase on womnat:
Product: Red Hat Linux
Classification: Retired
Component: evolution (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
  Show dependency treegraph
Reported: 2002-07-09 19:59 EDT by Leigh L. Klotz, Jr.
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-07-09 19:59:36 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 Leigh L. Klotz, Jr. 2002-07-09 19:59:28 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1a) Gecko/20020611

Description of problem:
When I start evolution-1.0.3-6 or -4, it prints
  evolution-shell-WARNING **: Cannot access Bonobo/ConfigDatbase on wombat:

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

How reproducible:

Steps to Reproduce:
1. Install evolution
2. Upgrade mozilla to 1.0.0 or later
3. Start evolution

Actual Results:  Evolution fails to start

Expected Results:  Evolution should have started.

Additional info:

This appears to be the result of a missing libssl3.so, which is provided in
RedHat 7.3 by mozilla-nss-0.9.9-7.  If you upgrade mozilla to a later revision
(say 1.0.0), libssl3.so moves from /usr/lib to /usr/lib/mozilla-1.0.0/libssl3.so

As a workaround you can do
 export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/lib/mozilla-1.0.0

evolution claims to depend on mozilla-nss without a version number.  Perhaps
it's a packager difference (RPMS from mozilla.org vs. from RedHat CD).
Comment 1 Jeremy Katz 2002-07-09 20:06:03 EDT
Add /usr/lib/mozilla-1.0.0 to /etc/ld.so.conf or wait for mozilla 1.0.1 which
moves the libs back to /usr/lib.  Unfortunately, the changes sort of came up out
of nowhere so I really couldn't have even fixed it with a version require (well,
without requiring a specific version, but that's not the case)

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