| Summary: | Digikam can't find albums at start due to database problems | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Jens Westemeier <Jens_Westemeier> |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.4.0 | |
| Sentry Crash Report: | |||
| Attachments: | Console output | ||
I don't see any further debug output after starting the database server, I suspect that mysqld has crashed. We won't be able to do anything about that, you will have to start with a new database. Is it openSUSE Tumbleweed? In openSUSE Tumbleweed there was a major update for MariaDB, this can only be processed correctly with digiKam-7.4.0, as a mysql_upgrade from digiKam-7.4.0 can be carried out if necessary. Maik Thanks for the advice - yes, I'm on Tumbleweed. I was not expecting non backward compatible changes in mariadb. I will switch to the internal sqlight and hope that 7.4 will come soon (it does not show up in the actual release plan (https://www.digikam.org/documentation/releaseplan/). Jens. |
Created attachment 140715 [details] Console output SUMMARY Had a working digikam environment. "Suddenly" it stopr workin at startup. STEPS TO REPRODUCE 1. Start digikam. A GUI dialog asks for path to album directory, all previous albums are gone. 2. Adding an album on local hdd. -> GUI Dialog: Can't add album for the given path. -> OK 3. GUI Dialog: Can't connect to local mysql server through socket ... (111) -> OK 4. GUI Dialog: Error opening Database -> Abort 5. digikam still running, nothing happens -> CNTRL C on command line At the end, mysql.socket ist still existing. Removed before start of digikam. Similar results from installed rpms an app image ADDITIONAL INFORMATION Output from console: