https://bugs.kde.org/show_bug.cgi?id=503894

--- Comment #22 from Chad B. <c...@bersche.com> ---
So this is still NOT working.  Same database server on 8.4 works just skippy. 
8.5, 8.6, or 8.7 all fail.  I've configured SSL:
MariaDB [(none)]> SHOW GLOBAL VARIABLES LIKE 'have_ssl';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| have_ssl      | YES   |
+---------------+-------+
MariaDB [(none)]> status
--------------
mysql  Ver 15.1 Distrib 10.3.39-MariaDB, for Linux (x86_64) using readline 5.1
SSL:                    Cipher in use is TLS_AES_256_GCM_SHA384

I set up a single database `digikam`.  I dropped the old one entirely, and did
all the grants per the setup.  
MariaDB [digikam]> show tables;
+--------------------+
| Tables_in_digikam  |
+--------------------+
| AlbumRoots         |
......
+--------------------+
32 rows in set (0.000 sec)

So clearly the initial tables are able to be created.
Alas, Event Viewer still shows:
Faulting application name: digikam.exe, version: 8.6.0.0, time stamp:
0x67d47119
Faulting module name: libmysql.dll, version: 8.0.40.0, time stamp: 0x679767b8
Exception code: 0x80000003
Fault offset: 0x000000000006e722
Faulting process id: 0x1f7c
Faulting application start time: 0x01dbeae03b70658f
Faulting application path: C:\Program Files\digiKam\digikam.exe
Faulting module path: C:\Program Files\digiKam\libmysql.dll

No idea why it keeps doing this, but it would seem that since it's starting
with a blank database, and adding tables, the communication to the DB is at
least somewhat functional.  Literally as I start digikam it'll show up in the
task list for about 2-3 second before it silently quits.  I'm installing the
"debug" version of 8.7 so if there's anything that can be done to help with
troubleshooting this "not a bug" that'd be great.  It's been crazy hard to set
up an external database, as there's not much troubleshooting info for an
external database.  I need an external DB because I'm going to be using
different systems to manage the same photos, so having the common external
database is the only realistic option for me, but the days of head scratching
have left me exhausted and frustrated.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to