Bug 493676

Summary: digikam freezes when adjusting date/time
Product: [Applications] digikam Reporter: Martin Tlustos <martin.tlustos>
Component: Plugin-Bqm-TimeAdjustAssignee: Digikam Developers <digikam-bugs-null>
Status: REPORTED ---    
Severity: normal CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 8.4.0   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Martin Tlustos 2024-09-26 07:36:44 UTC 
SUMMARY
When applying date/time changes to images, digikam freezes infinitely. Changes are applied successfully.

STEPS TO REPRODUCE
1. Select image that you want to change
2. edit date and time
3. click "apply" or "OK"

OBSERVED RESULT
Digikam freezes, I have to force close it (I waited for half an hour the first time)

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.8.0-45-generic (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Acer
Product Name: Aspire A515-44G
System Version: V1.12

ADDITIONAL INFORMATION
It makes no difference whether the image already has an date and time exif entry or not.
The freeze also happens with only one image.
Comment 1 Maik Qualmann 2024-09-26 08:06:02 UTC 
The problem cannot be reproduced here under Linux or Windows. Does "Neon" mean that you are using digiKam as a Snap package with sandbox? Please test our AppImage to see if the problem can be reproduced.

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

Maik
Comment 2 caulier.gilles 2024-09-26 08:41:51 UTC 
Hi,

It's can help to see where happen using GDB. Look instructions here :

https://www.digikam.org/contribute/

Else, please try also the 8.5.0 pre-release AppImage bundle to see if the problem is reproducible :

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

Gilles Caulier
Comment 3 Martin Tlustos 2024-09-26 09:13:24 UTC 
KDE Neon, digikam installed from the (underlying) ubuntu repositories
Comment 4 Maik Qualmann 2024-09-26 09:26:57 UTC 
Then it is a Snap package with sandbox. You only have access to files in your home directory. The Snap package is useless in connection with digiKam. Since your distribution cannot provide a native digiKam, use/try our AppImage.

Maik
Comment 5 Martin Tlustos 2024-09-26 09:31:35 UTC 
(In reply to Maik Qualmann from comment #4)
> Then it is a Snap package with sandbox. You only have access to files in
> your home directory. The Snap package is useless in connection with digiKam.
> Since your distribution cannot provide a native digiKam, use/try our
> AppImage.
> 
> Maik

No, repositories, I have disabled snap.
Comment 6 Martin Tlustos 2024-09-26 09:31:44 UTC 
Funny, now it works - but I  unchecked the "Update only existing timestamps" and before had used it on images without any timestamps (whatsapp-sent images). Maybe that was the reason.

So you might try it on images without any exif or xmp metadata, and check the "update only existing timestamps". Maybe that triggers this behavior. If not, then well it was just a weird coincidence...
Comment 7 Martin Tlustos 2024-09-26 09:32:59 UTC 
(In reply to Martin Tlustos from comment #5)
> (In reply to Maik Qualmann from comment #4)
> > Then it is a Snap package with sandbox. You only have access to files in
> > your home directory. The Snap package is useless in connection with digiKam.
> > Since your distribution cannot provide a native digiKam, use/try our
> > AppImage.
> > 
> > Maik
> 
> No, repositories, I have disabled snap.

And it is
4:8.4.0-0zneon+22.04+jammy+release+build5
from the neon repositories, not ubuntu, sorry
Comment 8 Martin Tlustos 2024-09-26 09:37:17 UTC 
And it doesn't show up in discovery, so it probably lacks appstream data and I probably installed it with muon...