Bug 500423

Are you using the Ubuntu digikam Snap package?

Maik

Ok, didn't read all the way through, AppImage.

Maik

I can't reproduce the problem. We create a copy of the Google Maps Start HTML file with your private key at "~/.local/share/digikam/geoiface/backend-googlemaps.html".
If this file exists, it will be used automatically.
Is it possible that this file is being deleted for some reason?

Maik

Created attachment 178615 [details]
backend-googlemaps.html

The file does not disappear when I stop Digikam.   I have attached the file.

When Digikam starts and I go into settings,  the API key is there.   But 
if I just exit without changing it,  when I click on any of the tabs for 
a map I just get white blank screen.   If I start digikam go directly to 
map without going to settings same issue.

To fix for the session,  I go into settings and delete just the last 
letter of the API key.  Then exit.  Clicking on a map tab gives a 
message that say "Oops .......".   If I check the HTML file, it has the 
modified API key.

Go back into settings and put the last letter in place.   The HTML file 
is back normal.  And I can get the map.

No evidence that file is getting deleted.   The permissions look 
standard.   Read write for me and the group.   Read-Only for others.  No 
one has Execute.


Anything else I should look at??


Herb


On 2/19/25 11:31, Maik Qualmann wrote:
> https://bugs.kde.org/show_bug.cgi?id=500423
>
> --- Comment #3 from Maik Qualmann<metzpinguin@gmail.com> ---
> I can't reproduce the problem. We create a copy of the Google Maps Start HTML
> file with your private key at
> "~/.local/share/digikam/geoiface/backend-googlemaps.html".
> If this file exists, it will be used automatically.
> Is it possible that this file is being deleted for some reason?
>
> Maik
>

You have now published your key by posting the HTML file, so you should now create a new key. Remember, if you reply to the email, it will also be published in the bug tracker; you should generally only write in the bug tracker website.

If you delete a letter from the key and an "Oops ......." appears, the correct file is being used. If the window remains white, there is another cause. This is due to OpenGL. First try to force a software OpenGL in the digiKam settings under Miscellaneous -> System (restart digiKam).

Maik

Created attachment 178646 [details]
attachment-1053530-0.html

Yes, dumb move on my part posting the file with the key.   I have gotten 
a new one.  The new one has the same behavior.

Tried changing the openCL settings.  Stopped and restarted Digikam after 
each change.   No luck.  problem persisted

Tried changing the "Decoding backend to render video.   Restart. No luck.

With the following I got some more info
1)   Select an Album from left panel with some geocode photos

2) Center display on Thumbnails

3) Right panel select Map

4 Select a geocoded photo

5) the right map display is white where the map should be. Altitude, 
Latitude, Longitude, and Date all display
6) Bottom right corner where I can select a map to use.   None of them 
when select will display a map.
7) clicking on the Globe next to the selection box will bring up a 
window with the map displayed accurately.
8) The Globe at lower left corner.  With Google maps, none of the 
display type produce anything, still white display

9)  Select Marble virtual globe and I get a map.  All of its variants work.
10)  Going into settings and editing the API as before still is temp fix 
to the issue.

Should I enable the internal debugging?   If so how do I access it to 
send to you

Thanks

Herb



On 2/20/25 01:14, Maik Qualmann wrote:
> https://bugs.kde.org/show_bug.cgi?id=500423
>
> --- Comment #5 from Maik Qualmann<metzpinguin@gmail.com> ---
> You have now published your key by posting the HTML file, so you should now
> create a new key. Remember, if you reply to the email, it will also be
> published in the bug tracker; you should generally only write in the bug
> tracker website.
>
> If you delete a letter from the key and an "Oops ......." appears, the correct
> file is being used. If the window remains white, there is another cause. This
> is due to OpenGL. First try to force a software OpenGL in the digiKam settings
> under Miscellaneous -> System (restart digiKam).
>
> Maik
>

Not OpenCL or Video Hardware settings, look for software OpenGL, CL != GL.

Maik

Created attachment 178690 [details]
attachment-1274180-0.html

I tried all the combinations on that screen,  Just In Case.  None worked.

I am currently running with the Software OpenGL checked and none of the 
others checked.    No changes and no relief.   This is after several 
reboots.

As an aside, in looking careful at the settings page,  the line for the 
hardware is clearly  OpenCL,  it is distinctly different than on the 
software line where it is OpenGL.   Or are these two different technologies.

Thanks


Herb


On 2/20/25 13:46, Maik Qualmann wrote:
> https://bugs.kde.org/show_bug.cgi?id=500423
>
> --- Comment #7 from Maik Qualmann<metzpinguin@gmail.com> ---
> Not OpenCL or Video Hardware settings, look for software OpenGL, CL != GL.
>
> Maik
>

Created attachment 179514 [details]
attachment-4105211-0.html

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<metzpinguin@gmail.com> ---
> Not OpenCL or Video Hardware settings, look for software OpenGL, CL != GL.
>
> Maik
>

Hi Herb,

The new AppImage bundle 8.7.0 pre-release for Linux based on Qt 6.8.3 is
online at usual place :

https://files.kde.org/digikam/

Let's me know if the problem remain.

Best regards

Gilles Caulier

Created attachment 182842 [details]
attachment-1190357-0.html

Just downloaded and installed the 8.7 production release.  It does not 
appear to have solved the problem.

Thanks


Herb Smith

On 4/3/25 20:23, bugzilla_noreply@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=500423
>
> caulier.gilles@gmail.com changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |caulier.gilles@gmail.com
>
> --- Comment #10 fromcaulier.gilles@gmail.com ---
> Hi Herb,
>
> The new AppImage bundle 8.7.0 pre-release for Linux based on Qt 6.8.3 is
> online at usual place :
>
> https://files.kde.org/digikam/
>
> Let's me know if the problem remain.
>
> Best regards
>
> Gilles Caulier
>