https://bugs.kde.org/show_bug.cgi?id=451153
Bug ID: 451153
Summary: Incomplete PrivCheck delete causes Digikam to fail
Product: digikam
Version: 7.6.0
Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Database-Mysql
Assignee: digikam-bugs-n...@kde.org
Reporter: bugskde...@goland.org
Target Milestone: ---
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
1. Not completely sure since the state described below shouldn't have happened,
I can only assume that the DROP TABLE in PrivCheck got into a bad state?
2.
3.
OBSERVED RESULT
Starting Digikam causes the error:
You have insufficient privileges on the database.
Following privileges are not assigned to you:
CREATE TABLE
Check your privileges on the database and restart digikam.
EXPECTED RESULT
Program works fine
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Linux Mint 20.3 Cinnamon
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
At some point Maria DB entered a state where .mysql.digikam/db_data/digikam
contained a PrivCheck.idb file but no PrivCheck.frm file. Once Maria DB got
into this state the PrivCheck table creation fails because it can't create a
table under those circumstances. In the end the only fix I could find was to
manually delete the PrivCheck.idb file from the file system.
I have no expertise with mariadb but the docs imply that it isn't possible to
issue a CREATE TABLE and a DROP TABLE in the same transaction. But perhaps it
would be possible to put in code that when PrivCheck fails, checks the table
directory to see if this state has been entered and deletes the PrivCheck.idb
file and tries again? Just a thought.
--
You are receiving this mail because:
You are watching all bug changes.
