Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39145 - [gnucash] Displays libdbi errors when started from the command line.
Attached to Project:
Arch Linux
Opened by Richard Ullger (rullger) - Tuesday, 04 March 2014, 12:49 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Tuesday, 04 March 2014, 22:11 GMT
Opened by Richard Ullger (rullger) - Tuesday, 04 March 2014, 12:49 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Tuesday, 04 March 2014, 22:11 GMT
|
DetailsDescription:
Produces the following errors in the terminal: libsqlite.so.0: cannot open shared object file: No such file or directory libdbi: Failed to load driver: /usr/lib/dbd/libdbdsqlite.so libpq.so.5: cannot open shared object file: No such file or directory libdbi: Failed to load driver: /usr/lib/dbd/libdbdpgsql.so libmysqlclient.so.18: cannot open shared object file: No such file or directory libdbi: Failed to load driver: /usr/lib/dbd/libdbdmysql.so Additional info: * package version(s) gnucash 2.6.1-1 libdbi-drivers 0.9.0-2 libdbi 0.9.0-2 sqlite 3.8.3.1-1 Steps to reproduce: Start gnucash from a terminal |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Tuesday, 04 March 2014, 22:11 GMT
Reason for closing: Not a bug
Tuesday, 04 March 2014, 22:11 GMT
Reason for closing: Not a bug
You have sqlite installed, but libsqlite.so.0 is part of the sqlite2 package (also an optdep of libdbi-drivers). If it couldn't find sqlite, it would be throwing an error about
/usr/lib/dbd/libdbdsqlite3.so not finding libsqlite3.so.0. pkgfile if very useful for finding these kind of things.
As you're saying that the errors are a side effect of the unused db backends not being installed you can close this task.