Created attachment 119368 [details] Output of journalctl relating to digikam error SUMMARY After updating OpenSuse Tumbleweed to 20190409, digicam fails to load. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Window displays with error message and OK button, which then exits digicam. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Your digikam4.db is read-only, please check the file permissions. Maik
Hi Maik, Thank you for the quick response. Dijikam 6.0.0 now opens, but nothing shows up under the albums tab? Regards, Bill > On Fri, 12 Apr 19, at 11:17:44, Maik Qualmann <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=406461 > > Maik Qualmann <metzpinguin@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |metzpinguin@gmail.com > > --- Comment #1 from Maik Qualmann <metzpinguin@gmail.com> --- > Your digikam4.db is read-only, please check the file permissions. > > Maik > > -- > You are receiving this mail because: > You reported the bug.
The question is, why was the database write-protected? Is it on a local or network drive? Otherwise start digiKam in the console and post the messages here. Maik
As the *.db files were read only perhaps the entire "/home/bill/Photos/" is also? If you've not already done so, check the permissions of your home directory. As an aside, I'm also running openSUSE TW 20190409 and didn't have any problems, either with "weird permissions" or any applications.
Hi Maik, The database is on a network drive (as are all the photos), but I really can’t remember when I made it write-protected or why. Digikam opens ok now, but no photos show for the collection that was there previously. I’m now into the process of adding my photos back in, removing duplicates, and adding tags. all of which will take a long time. When I’m done doing that, is there any way of backing up the database from within digicam? Thank you for your help. Regards, Bill > On Fri, 12 Apr 19, at 12:59:47, Maik Qualmann <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=406461 > > --- Comment #3 from Maik Qualmann <metzpinguin@gmail.com> --- > The question is, why was the database write-protected? Is it on a local or > network drive? Otherwise start digiKam in the console and post the messages > here. > > Maik > > -- > You are receiving this mail because: > You reported the bug.
For me, the question is more, why your images were all gone now. It was possible to write-protect database by changing mount options through the update of Tumbleweed. But why should it have emptied the database? Presumably, it can no longer be determined. There is no backup in digiKam. With SQLite, only the 4 database files (*.db) need to be backed up. Maik
*** Bug 406675 has been marked as a duplicate of this bug. ***
*** Bug 412417 has been marked as a duplicate of this bug. ***
I close this bug. DigiKam-7.0.0-RC checks whether the core database is write-protected and issues a corresponding message and then exits. Maik