Bug 593090 - Gnucash does not see database backends on 64-bit
Summary: Gnucash does not see database backends on 64-bit
Alias: None
Product: Fedora
Classification: Fedora
Component: gnucash
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-17 19:36 UTC by Jonathan Corbet
Modified: 2014-03-17 03:23 UTC (History)
2 users (show)

Fixed In Version: gnucash-2.3.15-2.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-18 17:38:40 UTC
Type: ---

Attachments (Terms of Use)

Description Jonathan Corbet 2010-05-17 19:36:54 UTC
Description of problem:

In x86_64 rawhide, gnucash is unable to locate the libdbi backends and thus silently refuses to offer the new database storage options.

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


How reproducible:

Steps to Reproduce:
1. Ensure that the appropriate libdbi-dbd-* drivers are installed
2. Run gnucash
3. Note that you can neither open or save to anything except "xml."
Actual results:

My PostgreSQL server sits there alone, unwanted, and idle.

Expected results:

I should be able to store to postgres.

Additional info:

The problem is the usual /usr/lib64 obnoxiousness - it never ends.  The database drivers are in /usr/lib64, but gnucash wants them in /usr/lib.  Setting GNC_DBD_DIR seems like it should fix it, but it doesn't.  OTOH, doing 
"ln -s /usr/lib64/dbd /usr/lib" makes everything work.

Comment 1 Bill Nottingham 2010-05-18 17:38:40 UTC
Fixed in 2.3.12-3.

Comment 2 Fedora Update System 2010-05-20 13:35:16 UTC
gnucash-2.3.12-3.fc13 has been submitted as an update for Fedora 13.

Comment 3 Fedora Update System 2010-10-21 04:50:55 UTC
gnucash-2.3.15-2.fc13 has been submitted as an update for Fedora 13.

Comment 4 Fedora Update System 2010-10-30 23:47:50 UTC
gnucash-2.3.15-2.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

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