| Summary: | Digikam cannot startup | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Chris Liebenberg <chris.liebenberg> |
| Component: | Database-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.5.0 | |
| Sentry Crash Report: | |||
| Attachments: |
Digikam trace file as requested
attachment-23752-0.html attachment-9590-0.html |
||
|
Description
Chris Liebenberg
2021-03-10 13:52:14 UTC
Please set the Debug environment variable for a better output of the messages, as described here: https://www.digikam.org/contribute/ We need the log from the start of digiKam. Maik We need a full debug log here, otherwise we cannot help. I suspect a package problem or not installed Qt Libs for the database support. Maik Created attachment 136580 [details]
Digikam trace file as requested
See trace file attached
Comment on attachment 136580 [details]
Digikam trace file as requested
digikam.dbengine: Error while opening the database. Error details [ QSqlError("14", "Error opening database", "unable to open database file") ]
"/proc/5282/root"
==> Sound like a right access problem
All database paths (core, thumbnail, face, similarity) probably point to a folder ("/run/media/chris/Photos"). Something went wrong here when choosing the database path. Delete the "digikamrc" in "~/.config" and start again from the beginning.
Maik
Created attachment 136602 [details] attachment-23752-0.html Mark, Thanks for the advice, but after deleting digikamrc and starting over, it still crash my linux when I select settings - configure digikam. Chris Liebenberg Senior Technical Quality Manager SAP AGS ZAt Tel +27-11-26356469 Mobile +27-828072283 chris.liebenberg@yahoo.com . On Thursday, March 11, 2021, 12:09:50 PM GMT+2, Maik Qualmann <bugzilla_noreply@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=434235 --- Comment #5 from Maik Qualmann <metzpinguin@gmail.com> --- All database paths (core, thumbnail, face, similarity) probably point to a folder ("/run/media/chris/Photos"). Something went wrong here when choosing the database path. Delete the "digikamrc" in "~/.config" and start again from the beginning. Maik I do not understand why digiKam does not append file names from the corresponding database type to the database paths. I'll look at the code again tonight. It may be related to the file dialog on Fedora. I guess Gnome as a desktop? Maik Created attachment 136618 [details] attachment-9590-0.html Maik, Firstly apologies for miss spelling your name in my previous mail. I also do not know what is going on as I have 25+ years of linux experience ,but everything I've tried does not work , deleting digikamrc file only helps to initialise digikam but the it fails if I try to go into configuration. My reason for the configurationis tjhat I have multiple drives that I need to add as collections. Chris Liebenberg Senior Technical Quality Manager SAP AGS ZAt Tel +27-11-26356469 Mobile +27-828072283 chris.liebenberg@yahoo.com . On Friday, March 12, 2021, 1:34:33 PM GMT+2, Maik Qualmann <bugzilla_noreply@kde.org> wrote:. And nothing I do seems to get this to work. https://bugs.kde.org/show_bug.cgi?id=434235 --- Comment #7 from Maik Qualmann <metzpinguin@gmail.com> --- I do not understand why digiKam does not append file names from the corresponding database type to the database paths. I'll look at the code again tonight. It may be related to the file dialog on Fedora. I guess Gnome as a desktop? Maik (In reply to Maik Qualmann from comment #7) > I do not understand why digiKam does not append file names from the > corresponding database type to the database paths. I'll look at the code > again tonight. It may be related to the file dialog on Fedora. I guess Gnome > as a desktop? > > Maik Maik, Yes it's Gnome desktop. Maik, I have done various testing this weekend. My desktop runs linux Fedora 32 with the latest updates, this is the one that I have the problem with and I believe this is after an update. I also run another linux Fedora 28 Scientific on another partition. I have Digikam 5.9 on it and I added the same volumes on it as on the other linux and everything works fine. digiKam 7.2.0 official release is published with more than 360 files closed from bugzilla: https://www.digikam.org/news/2021-03-22-7.2.0_release_announcement/ Can you reproduce the dysfunction with this version ? Thanks in advance for your feedback Gilles Caulier Chris, Stable digiKam 7.4.0 is published. Please check if problem is reproducible. https://www.digikam.org/download/ Thanks in advance Gilles Caulier No feedback. not reproducible with 7.5.0. Closed |