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

            Bug ID: 500445
           Summary: digiKam "You have insufficient privileges on database.
                    Following privileges are not assigned to you: CREATE
                    TABLE" after cataloging 300k images and simply
                    restarting digiKam
    Classification: Applications
           Product: digikam
           Version: 8.1.0
          Platform: Other
                OS: Microsoft Windows
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: Database-Engine
          Assignee: digikam-bugs-n...@kde.org
          Reporter: ticedo...@hotmail.com
  Target Milestone: ---

Created attachment 178621
  --> https://bugs.kde.org/attachment.cgi?id=178621&action=edit
Database configuration details

SUMMARY:
 I am getting an error message when I restart digiKam saying the MySQL database
user "digikam" lacks the privilege to "CREATE TABLES". Everything worked the
first time when it created all the tables and entries needed to catalog the
300k images (screenshots attached), so it seems it was okay at first, then
something changed.

I'm trying to set up a system where multiple PC can access the same SMB shared
NAS picture library. The NAS (WD PR4100 w/ 16GB RAM, 24TB usable) has a
"built-in" MariaDB (v10.5.19-MariaDB) being used for the MySQL Server in the
digiKam app.

This error message is popping up on both PCs that were fine when the logged in
the 1st time and started to catalog images, so they are both now locked out.

And, most importantly, when I was testing this on a smaller scale, I didn't
have to do anything to see if digiKam on a MySQL server with multiple PCs
access the shared image library was possible. It just worked. Then I
uninstalled digiKam on 2 PCs, dumped the database and started over from
scratch.

STEPS TO REPRODUCE
1. Using a Remote MySQL server that is "built-in" on a WD PR4100 NAS (MariaDB
v10.5.19-MariaDB) and phpMyAdmin to manage (3rd Party app installed on the
NAS). 
Used phpMyAdmin to create a new user "digikam" and assigned a simple password
(digikam) for that use. phpMyAdmin also created a database with the name
"digikam" and assigned all the privileges for that user to own the database. At
this point, the database is empty with no tables.
2. Install digiKam 8.1 on the Windows 10 PC, filled in all the details for the
remote MySQL server and the local databases. 
Then create a new collection and start cataloging 300k images (see attached
screenshots). 
At this point, all the tables get successfully created on the NAS's digikam
database and over the course of 36 hours, the tables end up with enough entries
for 300K-plus images.
3. After it finished, I closed digiKam. 
After that, digiKam will not start again. 
Every time I start digiKam, it fails to open with the error message popped up.
The only option is to cancel, so I can't see if there is something fixable in
another setting
4. According to phpMyAdmin, all the privileges are the same as when I started
and nothing has changed.
The local databases are on a drive that still has 600GB free 
5. I completely uninstalled DigiKam from the PC and drop the NAS database
digikam. 
I also disabled and re-enabled the NAS's "Network Shared Database" to get a
fresh copy running and started over from scratch.
I tried this 2x with the same results.
6. I retyped the "Remote Server Settings" password to match the database
server's digikam account, and that didn't help.

OBSERVED RESULT
Failure to open digiKam or reconnect to the remote MySQL database

EXPECTED RESULT
DigiKam should run normally and connect to the remote MySQL database

SOFTWARE/OS VERSIONS
Windows: 10 Pro (64bit X86), 22H2 (OS Build 19045.5487)
Western Digital PR4100 (16GB RAM / 24TB usable, OS5 5.30.103) using MariaDB
10.5.19-MariaDB - Source distribution).
DigiKam 8.1.0 for Windows.

ADDITIONAL INFORMATION
The NAS was updated with a new version of its OS5 on Feb 11. But the release
notes do not have any mention of an update to the MariaDB version.

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

Reply via email to