Bug 16414

Summary: digikam crashs on import collections
Product: Mageia Reporter: franck villaume <franck.villaume>
Component: RPM PackagesAssignee: KDE maintainers <kde>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal CC: anaselli, fundawang, mageia, marja11
Version: 5   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: digikam-4.8.0-1.mga5.src.rpm CVE:
Status comment:

Description franck villaume 2015-07-19 12:58:39 CEST 
Description of problem:

On a fresh mageia5 install, with a fresh kde profil and a fresh digikam installation, adding a collection with some files such as mp3, digikam crashes.


Version-Release number of selected component (if applicable):
digikam 4.8.0
mageia 5

lib64kexiv2_11-4.14.3-1.mga5
lib64exiv2_13-0.24-5.mga5
libkexiv2-4.14.3-1.mga5


How reproducible:
all the time.


Steps to Reproduce:
start digikam
configure a collection that contains mp3 files
crash...


Extract of the stackstrace:

digikam(5324)/KEXIV2: Cannot load metadata from file   (Error # 11 :  /home/xxxxx/xxx/xxxx/xxxxxxx.mp3: The file contains data of an unknown image type 
*** Error in `digikam': free(): invalid next size (normal): 0x00007f2c900045e0 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7241e)[0x7f2cbd3ee41e]
/lib64/libc.so.6(+0x7a158)[0x7f2cbd3f6158]
/lib64/libc.so.6(cfree+0x48)[0x7f2cbd3f9828]
/lib64/libexiv2.so.13(_ZN5Exiv29RiffVideo15infoTagsHandlerEv+0x256)[0x7f2cbadd1426]
/lib64/libexiv2.so.13(_ZN5Exiv29RiffVideo11decodeBlockEv+0x105)[0x7f2cbadd5265]
/lib64/libexiv2.so.13(_ZN5Exiv29RiffVideo10tagDecoderERNS_7DataBufEm+0x58)[0x7f2cbadd4eb8]
/lib64/libexiv2.so.13(_ZN5Exiv29RiffVideo11decodeBlockEv+0x105)[0x7f2cbadd5265]
/lib64/libexiv2.so.13(_ZN5Exiv29RiffVideo12readMetadataEv+0x340)[0x7f2cbadd55f0]
/lib64/libkexiv2.so.11(_ZNK11KExiv2Iface6KExiv24loadERK7QString+0xa9)[0x7f2cc293dc19]
/lib64/libdigikamcore.so.4.8.0(_ZNK7Digikam9DMetadata4loadERK7QString+0x26)[0x7f2cc2204156]
/lib64/libdigikamdatabase.so.4.8.0(_ZN7Digikam12ImageScanner12loadFromDiskEv+0x4a)[0x7f2cc1c2ae9a]
/lib64/libdigikamdatabase.so.4.8.0(_ZN7Digikam12ImageScanner7newFileEi+0x10)[0x7f2cc1c2b080]
/lib64/libdigikamdatabase.so.4.8.0(_ZN7Digikam17CollectionScanner11scanNewFileERK9QFileInfoi+0x14e)[0x7f2cc1bc037e]
/lib64/libdigikamdatabase.so.4.8.0(_ZN7Digikam17CollectionScanner9scanAlbumERKNS_18CollectionLocationERK7QString+0xa82)[0x7f2cc1bc38b2]
/lib64/libdigikamdatabase.so.4.8.0(_ZN7Digikam17CollectionScanner9scanAlbumERKNS_18CollectionLocationERK7QString+0x93f)[0x7f2cc1bc376f]
/lib64/libdigikamdatabase.so.4.8.0(_ZN7Digikam17CollectionScanner13scanAlbumRootERKNS_18CollectionLocationE+0x63)[0x7f2cc1bc40f3]
/lib64/libdigikamdatabase.so.4.8.0(_ZN7Digikam17CollectionScanner12completeScanEv+0x1cd)[0x7f2cc1bc586d]
digikam[0x5e2dbc]
/lib64/libQtCore.so.4(+0x7afff)[0x7f2cbdf46fff]
/lib64/libpthread.so.0(+0x75bd)[0x7f2cbb1535bd]
/lib64/libc.so.6(clone+0x6d)[0x7f2cbd4735cd]
======= Memory map: ========



Reproducible: 

Steps to Reproduce:
franck villaume 2015-07-19 13:03:46 CEST

Summary: digikam crashs on import collectino => digikam crashs on import collections

Comment 1 franck villaume 2015-07-19 13:04:05 CEST 
seems related to http://dev.exiv2.org/issues/997
Thierry Vignaud 2015-07-31 09:40:56 CEST

CC: (none) => anaselli, fundawang, lmenut

Luc Menut 2016-08-25 16:42:50 CEST

CC: lmenut => (none)

Samuel Verschelde 2016-10-31 15:11:07 CET

Assignee: bugsquad => kde

Comment 2 Nicolas Lécureuil 2016-12-31 10:57:12 CET 
is this bug still valid ? we have this commit already in mga5

CC: (none) => mageia

Comment 3 Marja Van Waes 2017-08-02 23:27:43 CEST 
(In reply to Nicolas Lécureuil from comment #2)
> is this bug still valid ? we have this commit already in mga5

7 months later, no reply :-(




Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED
CC: (none) => marja11