| Summary: | Digikam crashes when clicking on the Table button, new installation | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | bcr |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 5.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | macOS (DMG) | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed In: | 5.1.0 | |
| Sentry Crash Report: | |||
|
Description
bcr
2016-07-16 09:14:05 UTC
How do you setup your external DB ? Which DB settings do you use exactly ? Here i use an external MariaDB server running under Linux with an OSX client, and crash is not reproducible... Gilles Caulier I get this warning when I start up: Error message: Error opening database backend. Unknown database 'digikam_thumbs' QMYSQL: Unable to connect I didn't specify any options in the configuration dialog except for the names of the three databases requested: 'digikam', 'digikam_thumbs', and 'digikam_faces'. Username chosen was 'digikam', not 'root' as shown in the requirements tab In the DB I gave the digikam user every possible privilege, pretty much admin level rights. Well, your DK is not connected to Mysql server. Did you follow instruction in DK.setup/DB pages to init the remove digiKam DB ? This is what i used to test and it work fine. You can use different DB names without problem. Gilles Caulier Well, its partially connected. I can see a populated 'digikam' table full of data that got created on my few images. I just don't see the other two tables mentioned. Not sure what could have prevented their creation. correction: its a digikam database with about 20 tables and one view in it. Just no sign of the other databases. This is a first-time digiKam installation on both OSX and the remote MariaDB I recommend to re-init Mysql database and re-create it using the procedure given in DB setup panel. Look 'Requirements" tab for details. Gilles Caulier My setup for ex : digikam version 5.0.0 Images: JPG: 11501 PGF: 1 PNG: 237 PPM: 5 RAW-ARW: 212 RAW-CR2: 63 RAW-CRW: 10 RAW-DCR: 3 RAW-DNG: 81 RAW-HDR: 1 RAW-MRW: 36 RAW-NEF: 39 RAW-ORF: 4 RAW-PEF: 10 RAW-RAF: 153 RAW-RAW: 4 RAW-RW2: 1 RAW-RWL: 1 RAW-X3F: 4 TIFF: 39 XCF: 3 total: 12408 : Videos: 3GP: 1 AVI: 2 MKV: 1 MOV: 4 MP4: 3 MPEG: 1 total: 12 : Total Items: 12420 Albums: 5921 Tags: 178 : Database backend: QMYSQL Host Name: 192.168.1.20 Host Port: 3306 User account: digikamuser Connect options: Core Db name: digikamOSX Thumbs Db name: digikamOSX Face Db name: digikamOSX To init the database on server : CREATE USER 'digikamuser'@'%' IDENTIFIED BY 'password'; GRANT ALL ON *.* TO 'digikamuser'@'%' IDENTIFIED BY 'password'; CREATE DATABASE digikamOSX; GRANT ALL PRIVILEGES ON digikamOSX.* TO 'digikamuser'@'%'; FLUSH PRIVILEGES; Gilles Caulier Screenshot of DK 5.0.0 in action under OSX with a remote MAriaDB database running under Linux server : https://www.flickr.com/photos/digikam/28263744781 Gilles Caulier Ah, ok. I guess I’m playing the part of the clueless user, I didn’t fully read the requirements tab and know that I had to execute a script. Its odd that digiKam would create the first database but not the others though. Being unable to reach a db should not cause digiKam to crash however, network issues could cause the same problem. I’ll put some UI suggestions in another post. Thanks for looking into it. |