Bug 435902

database type is Mysql ? if yes, do you use Internal version or Server ?

HI.

Yes I think it is mysql. Internal version - assuming that means I've downloaded it to my laptop and opening it off there.




Unofficial

-----Original Message-----
From: bugzilla_noreply@kde.org <bugzilla_noreply@kde.org> 
Sent: Monday, 19 April 2021 2:58 PM
To: Daniel C Purdey (DELWP) <Daniel.Purdey@delwp.vic.gov.au>
Subject: [digikam] [Bug 435902] error massage = insufficient privileges on the database...


EXTERNAL SENDER: Links and attachments may be unsafe.

https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.kde.org_show-5Fbug.cgi-3Fid-3D435902&d=DwIFaQ&c=JnBkUqWXzx2bz-3a05d47Q&r=_DGlHQHjrtzMShQxTxL106BOdYz9cYPuftwsNXesUhs&m=5ONp4Gz0fDPTS1r4akobZlCEmreXzIBCV3MiHo2Qyhg&s=eZ3tCqlx5wwVlAktn6cFFIBsiXmHTGsOZYUbjmESZmk&e= 

--- Comment #1 from caulier.gilles@gmail.com --- database type is Mysql ? if yes, do you use Internal version or Server ?

--
You are receiving this mail because:
You reported the bug.

(In reply to caulier.gilles from comment #1)
> database type is Mysql ? if yes, do you use Internal version or Server ?

HI.

Yes I think it is mysql. Internal version - assuming that means I've downloaded it to my laptop and opening it off there.
Have you heard of this issue/error message before?

(In reply to caulier.gilles from comment #1)
> database type is Mysql ? if yes, do you use Internal version or Server ?

My colleagues have successfully downloaded and used this application, and love it, on similar their work laptops without experiencing this error

Check in Setup/Database dialog page to be sure.

Why did you use 7.1.0 and not last stable 7.2.0 released few weeks ago ?

Please give us the DebugView log from the start, as described here also for Windows: 

https://www.digikam.org/contribute/

Don't forget to set the environment variable.

But I suspect that the internal database is defective. We had a bug in digiKam-7.1.0 which could lead to the destruction of the internal MySQL database when exiting digiKam. This problem has been fixed in digiKam-7.2.0. You will likely have to start with a new database.

Maik

(In reply to caulier.gilles from comment #5)
> Check in Setup/Database dialog page to be sure.
> 
> Why did you use 7.1.0 and not last stable 7.2.0 released few weeks ago ?

Apologies. I have 7.2.0. I didn't see it was updated. I've been downloading the latest from the digikam site several times over the pat 2 weeks and didn't notice the update.

Small note, message can be mistaken.
In my case, following a wrong import, disk was filled completely and when digikam restarted, it returns this error even if was not relevant (sqlite backend = no grant)

Digikam 7.1 on Fedora33/Qubes.

If youre running Windows and this error pops up, make sure you have allowed digikam.exe in Windows Defenders "controlled folder access".
Wem auf Windows diese Fehlermeldung aufpoppt darf nicht vergessen digikam im "Überwachter Ordnerzugriff" freizugeben.

Type in Windows search " controlled folder access ". Then   " allow app ...  " / .. add app  / recently blocked app / digikam.exe  
In Windows Suche " überwachter Ordnerzugriff " eingeben. Dann "App ... zulassen " / Zulässige App hinzufügen / zuletzt blockierte.. /digikam.exe 

This solved  " you have insufficient privileges on the database. Following privileges are not assigned to you: CREATE TABLE Check you privileges on  the database and restart digikam "  error message.
Das löst die " Sie besitzen nicht die benötigten Rechte für die Datenbank. Sie besitzen folgende Rechte nicht: CREATE TABLE. Überprüfen sie Ihre Rechte für die Datenbank und starten Sie digiKam neu " Fehlermeldung.

Cheers
Prost

Dan,

Instructions from comment #9 can solve your problem ?

Best

Gilles Caulier

I had this problem last month and had to recreate the (MYSQL Internal Database), after reverting to MariaDB 10.5.1. Since then everything worked until a few minutes ago, when the error recurred. I don't use Windows Defender and don't believe McAfee is to blame, because nothing changes between digikam working, then failing the next time it runs.
The only solution that works for me is to restore the latest backup of the .mysql.digikam folders.

I did discover that 2 instances of digikam were running the last time it ran successfully.

@Steve

digiKam 8.0.0 is out. This entry still valid with this release ?

Best regards

Gilles Caulier

(In reply to caulier.gilles from comment #12)
> @Steve
> 
> digiKam 8.0.0 is out. This entry still valid with this release ?
> 
> Best regards
> 
> Gilles Caulier
It is fine now, you may close the bug report.
Kind Regards
Steve