https://bugs.kde.org/show_bug.cgi?id=500423
--- Comment #9 from Herb Smith <hesmith1...@aol.com> --- It has been almost a month and I thought I would update on how this issue is impacting me. And because the issue came back After my initial report for several days I just lived with the problem. Then Digikam started behaving very strangely and the only thing that made sense to me was database corruption. (When displaying photos by dates the center panel suddenly was not showing anything. At least not for the month and year that I had been working on when problem started. I soon discovered that if I went to the Albums display and selected the Album that contained the photos for that month and year it would display them. I also confirmed that the photos were still present on the hard drive. This told me that 1) I still had the photos and 2) the Thumbnails were still in that database. I ran all of items that were database related in Tools->maintenance. This did not fix issue. Finding no other tools for forcing a re index, used the database migration tool to export to what hopefully was a clean copy of the database. Took over a day and with rebuilding of the support db's several days [This with the db's on an SSD]. This fixed my display issue) Fixing this issue also fixed the problem with Google Maps API Key also. So things have been good for the past couple of weeks. Until today. I have again working in Dates view. Using <Shift><Control><D and G a lot. Suddenly <Shift><Control> before hitting anything else was opening up the Similarity tab on the left panel. If I reselected dates and then selected several photos, the first time I attempted to edit dates I was successful. If I need to adjust those same dates again I could not reenter date editing because <Shift><Control> took me to Similarity immediately. After trying maintenance and restarting Digikam, the problem went away with a full shut down of the entire system. On the first few reboots of the PC I noticed the Write Ahead databases (--WAL's) were bigger that the actual databases. (No opinion of what that means). After a few reboots PC and restarts of DigiKam (Only when activity monitor showed no disk usage by DigiKam) the Write Ahead's returned to a normal size. But now the problem with Google API key is back. Is there a way short of exporting the database and rebuilding all supporting DB's to force a rebuild of all the indexes? I am running the AppImage for Digikam 8.5 downloaded from Digikam web site, and Ubuntu 24.04. Thanks Herb Smith On 2/20/25 13:46, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=500423 > > --- Comment #7 from Maik Qualmann<metzping...@gmail.com> --- > Not OpenCL or Video Hardware settings, look for software OpenGL, CL != GL. > > Maik > -- You are receiving this mail because: You are watching all bug changes.
