https://bugs.kde.org/show_bug.cgi?id=451153
Maik Qualmann changed:
What|Removed |Added
Version Fixed In|7.7.0 |8.2.0
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #22 from caulier.gil...@gmail.com ---
@Nadine,
Any feedback here ?
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451153
Nadine changed:
What|Removed |Added
CC||cnhelk...@comcast.net
--- Comment #21 from Nadine
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #20 from Maik Qualmann ---
The database is broken. The normal process would be to create a database dump
and re-import in a new database. You can last try to delete all PrivCheck*
files in the MySQL digiKam folder.
Maik
--
You are
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #19 from bugskde...@goland.org ---
(In reply to Maik Qualmann from comment #18)
> Try running the following commands in the database (mysql) if it works
> normally:
>
> USE digikam;
> CREATE TABLE IF NOT EXISTS PrivCheck (id INT) ENGINE
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #18 from Maik Qualmann ---
Try running the following commands in the database (mysql) if it works
normally:
USE digikam;
CREATE TABLE IF NOT EXISTS PrivCheck (id INT) ENGINE InnoDB;
DROP TABLE PrivCheck;
Maik
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #17 from bugskde...@goland.org ---
(In reply to Maik Qualmann from comment #16)
> The message actually says that no database server is running. You have to
> leave digiKam with the error window open, otherwise the internal server will
> be
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #16 from Maik Qualmann ---
The message actually says that no database server is running. You have to leave
digiKam with the error window open, otherwise the internal server will be shut
down again. Otherwise start a MySQL server manually
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #15 from bugskde...@goland.org ---
yaron@yaron-MS-7B79:~/Pictures/.mysql.digikam/db_data/digikam$ mysql -u root
--socket=/home/yaron/.local/share/digikam/db_misc/mysql.socket
ERROR 2002 (HY000): Can't connect to local MySQL server through
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #14 from Maik Qualmann ---
There is no password, just press enter or omit the -p option. Are you still
being asked for a password?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #13 from bugskde...@goland.org ---
It asks me for a password, I tried empty and I tried the one I set when I setup
digikam and neither works. What's the easiest way to just blow away the entire
database and start fresh?
--
You are
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #12 from Maik Qualmann ---
One could only guess what the cause is. digiKam crash, bug in MariaDB (there
are bug entries for 10.3 for corrupted tables as well). A disk problem can also
be the cause.
Depending on how familiar you are with
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #11 from bugskde...@goland.org ---
yaron@yaron-MS-7B79:~/Applications$ mariadb --version
mariadb Ver 15.1 Distrib 10.3.34-MariaDB, for debian-linux-gnu (x86_64) using
readline 5.2
I think the key question is - why did the DB get corrupt in
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #10 from Maik Qualmann ---
Hmm, I'm lost at the error message too. The database may be corrupt and you
need to start over with a new one.
Which MySQL/MariaDB version are you using exactly?
Maik
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #9 from bugskde...@goland.org ---
That would be privcheck.idb. I deleted it and ran again:
yaron@yaron-MS-7B79:~/Applications$ export QT_LOGGING_RULES="digikam.*=true"
yaron@yaron-MS-7B79:~/Applications$
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #8 from Maik Qualmann ---
However this problem came about, here is a pretty good solution:
https://itecnote.com/tecnote/mysql-error-tablespace-for-table-xxx-exists-please-discard-the-tablespace-before-import/
Look for an *.idb file that
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #7 from bugskde...@goland.org ---
Here is the log I generated, please let me know what other information I can
provide. I'd really like to understand why the database stopped working.
Thanks!
Yaron
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #6 from Maik Qualmann ---
Is there any news, could the debug log be created?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #5 from Maik Qualmann ---
Enable Qt debug output:
export QT_LOGGING_RULES="digikam.*=true"
Start the AppImage in the terminal and post the log.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #4 from bugskde...@goland.org ---
(In reply to Maik Qualmann from comment #3)
> If the database rights check reports an error, you do not have the
> appropriate rights. The tables would be automatically deleted at the next
> start if the
https://bugs.kde.org/show_bug.cgi?id=451153
--- Comment #3 from Maik Qualmann ---
If the database rights check reports an error, you do not have the appropriate
rights. The tables would be automatically deleted at the next start if the
rights were correct. Nothing must and should not be deleted
https://bugs.kde.org/show_bug.cgi?id=451153
bugskde...@goland.org changed:
What|Removed |Added
Resolution|WORKSFORME |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=451153
Maik Qualmann changed:
What|Removed |Added
Version Fixed In||7.7.0
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=451153
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
24 matches
Mail list logo
