Bug 407022 - digiKam crash at start
Summary: digiKam crash at start
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Engine (other bugs)
Version First Reported In: 6.1.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-28 18:45 UTC by Daniel Bauer
Modified: 2021-05-04 04:00 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 7.3.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Bauer 2019-04-28 18:45:52 UTC 
SUMMARY
since the latest update digikam 6.1.0-196.1-x86_64 from obs://build.opensuse.org/KDE:Extra produces a segmentation fault immediately at start ("Speicherzugriffsfehler (Speicherabzug geschrieben)")

STEPS TO REPRODUCE
1. start dikigam from menu or console
2. 
3. 

OBSERVED RESULT
immediately crashes with segmentation fault

EXPECTED RESULT
start digikam

SOFTWARE/OS VERSIONS
Opensuse Leap 42.3
KDE-Plasma-Version: 5.8.7
KDE-Frameworks-Version: 5.32.0
Qt-Version: 5.6.2
Kernel-Version: 4.4.176-96-default
64bit


ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2019-04-28 19:20:32 UTC 
This will most certainly be a package problem. Which happens more often when the KDE:Extra repository is used. Please start digiKam from the console and post the messages.

Maik
Comment 2 Daniel Bauer 2019-04-28 20:48:41 UTC 
(In reply to Maik Qualmann from comment #1)
> This will most certainly be a package problem. 

Yes, it looks like that. But it's the first time it happens and I hope to reach the "packager" with this report :-)

> Please start digiKam from the console and
> post the messages.

The only message I get when staring form console is:

Speicherzugriffsfehler (Speicherabzug geschrieben)

nothing more...
Comment 3 Maik Qualmann 2019-04-28 20:59:34 UTC 
The "packagers" are probably not looking in here. I'll add your namesake.

Maik
Comment 4 Wolfgang Bauer 2019-04-29 14:15:03 UTC 
It was a problem with exiv2, and should be fixed already since a couple of hours.
Comment 5 Daniel Bauer 2019-04-29 15:27:04 UTC 
(In reply to Wolfgang Bauer from comment #4)
> It was a problem with exiv2, and should be fixed already since a couple of
> hours.

This is great, greater!
I can confirm that with the update today digikam runs again perfectly.
 
Thank you very much!
Comment 6 caulier.gilles 2021-05-04 04:00:01 UTC 
Not reproducible with 7.3.0