Bug 411946 - Crash when saving captions to picture
Summary: Crash when saving captions to picture
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Exif (show other bugs)
Version: 6.4.0
Platform: Appimage Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-15 19:48 UTC by MarcP
Modified: 2020-08-10 10:18 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.4.0
Sentry Crash Report:


Attachments
Backtrace of the crash (400.67 KB, text/plain)
2019-09-15 19:48 UTC, MarcP
Details
Backtrace of the exact same problem (and same picture) in another digikam session (378.87 KB, text/plain)
2019-09-15 19:55 UTC, MarcP
Details

Note You need to log in before you can comment on or make changes to this bug.
Description MarcP 2019-09-15 19:48:08 UTC
Created attachment 122673 [details]
Backtrace of the crash

SUMMARY

I had another crash today when saving the changes after editing the captions (title, description and date) of a jpg picture. 

I have attached the console output to this bug report, including the backtrace. The beginning of the output is missing due to its size (the terminal emulator only saves the last 10000 lines).

STEPS TO REPRODUCE
1. Start digikam and wait until the initial scan finishes.
2. Select one file, go to the Captions panel, and edit the title, description and date.
3. Save the changes

OBSERVED RESULT
Digikam immediately crashed and closed.

EXPECTED RESULT
Changes should be saved and the user should continue to use the software.

SOFTWARE/OS VERSIONS

digikam-6.4.0-git-20190915T141349-x86-64.appimage in Ubuntu 18.04LTS.
Comment 1 MarcP 2019-09-15 19:51:24 UTC
More info:

After restarting digikam, and checking on that file, I can see that the captions I had written had been saved to digikam's database but not to the image metadata. Editing any changes to that picture (e.g. the date, using the metadata editor) made those changes go away from the database.
Comment 2 MarcP 2019-09-15 19:55:01 UTC
Created attachment 122674 [details]
Backtrace of the exact same problem (and same picture) in another digikam session
Comment 3 Maik Qualmann 2019-09-15 20:19:45 UTC
Gilles is trying to fix the locale issue in AppImage.
It does not make sense at the moment to test the AppImage as it is a basic problem with the locale. Although I can prevent this crash, it will not fix the cause. And it's also not good for editing your images.

Maik
Comment 4 Maik Qualmann 2019-09-15 20:21:36 UTC
At the moment use a native digiKam version or compile a current git version.

Maik
Comment 5 MarcP 2019-09-15 20:27:22 UTC
Sure, no problem. I was just reporting what I experienced.
Comment 6 Maik Qualmann 2019-09-15 20:30:13 UTC
Git commit a43d38dc2aee580ad89a243193b6dc0dd5d65750 by Maik Qualmann.
Committed on 15/09/2019 at 20:28.
Pushed by mqualmann into branch 'master'.

prevent possible NULL pointer from QTextCodec
FIXED-IN: 6.4.0

M  +2    -1    NEWS
M  +1    -1    core/libs/metadataengine/engine/metaengine_exif.cpp

https://invent.kde.org/kde/digikam/commit/a43d38dc2aee580ad89a243193b6dc0dd5d65750
Comment 7 Maik Qualmann 2019-09-15 20:39:13 UTC
No problem, the bug is important to stabilize digiKam. But at the moment please do not edit your images with the current developer AppImage. Without a working locale there can be a lot of problems.

See here: Bug 410980

Maik
Comment 8 MarcP 2019-09-15 20:41:03 UTC
Ok, understood, thanks.