After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 795049 - GnuCash 2.6.20-1 (Fedora Linux package) is unable to open MariaDB database
GnuCash 2.6.20-1 (Fedora Linux package) is unable to open MariaDB database
Status: VERIFIED FIXED
Product: GnuCash
Classification: Other
Component: Backend - SQL
git-maint
Other Linux
: Normal critical
: future
Assigned To: gnucash-core-maint
gnucash-core-maint
: 795206 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2018-04-07 11:04 UTC by Alexey Kosilin
Modified: 2018-07-01 17:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alexey Kosilin 2018-04-07 11:04:46 UTC 
Hello!

I'm unable to read my MariaDB database since GnuCash has been updated to version 2.6.20-1. My environment: Fedora Linux 27 x86_64, GnuCash 2.6.20-1, mariadb 10.2.14-1, libdbi 0.9.0-9.

Error message is: "GnuCash could not complete a critical test for the presence of a bug in the "libdbi" library. This may be caused by a permissions misconfiguration of your SQL database. Please see https://bugzilla.gnome.org/show_bug.cgi?id=645216 for more information."

In a fact, GnuCash is trying to recreate 'numtest' table. Exactly this thing has changed since 2.6.18 (previous package version in Fedora repos). Now GnuCash is trying to recreate table by using strange SINGLE query 'DROP TABLE IF EXISTS numtest;CREATE TEMPORARY TABLE numtest ( test_int BIGINT, test_unsigned BIGINT, test_double FLOAT8 )'. MariaDB doesn't understand it and returns 'syntax error' response.

As I think, recreation of this table should be performed by executing of TWO separate queries:

DROP TABLE IF EXISTS numtest
CREATE TEMPORARY TABLE numtest ( test_int BIGINT, test_unsigned BIGINT, test_double FLOAT8 )

In this case everything will work fine.

Thanks in advance,
Alexey Kosilin
Comment 1 Jim Y 2018-04-08 22:08:59 UTC 
I forgot to mention that I went back to version 2.6.19 and saved the database using the xml format. I tried to open that in version 3.0 and ran into the same error. So it's not anything specific to the database.
Comment 2 John Ralls 2018-04-08 22:12:04 UTC 
(In reply to Jim Y from comment #1)
> I forgot to mention that I went back to version 2.6.19 and saved the
> database using the xml format. I tried to open that in version 3.0 and ran
> into the same error. So it's not anything specific to the database.

Are you commenting on the wrong bug?
Comment 3 John Ralls 2018-04-09 00:11:52 UTC 
I've got a fix for this committed but not pushed because it turns out that it doesn't affect unstable. I want to confer with Geert about whether we should have a 2.6.21.
Comment 4 Frank H. Ellenberger 2018-04-09 05:36:28 UTC 
I think, in this case we should.
Comment 5 John Ralls 2018-04-10 21:44:41 UTC 
Fixed. We'll release 2.6.21 shortly.
Comment 6 Alexey Kosilin 2018-04-11 09:45:36 UTC 
(In reply to John Ralls from comment #5)
> Fixed. We'll release 2.6.21 shortly.

Ok. Thank you very much!

Best regards,
Alexey Kosilin
Comment 7 John Ralls 2018-04-12 18:12:56 UTC 
*** Bug 795206 has been marked as a duplicate of this bug. ***
Comment 8 John Ralls 2018-06-30 00:07:32 UTC 
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=795049. Please update any external references or bookmarks.
Comment 9 Alexey Kosilin 2018-07-01 17:16:30 UTC 
The version 2.6.21 is working well. Thank you very much! The bug can be closed as I think.