| Summary: | digikam crashes, when removing and adding tags | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Axel Krebs <axel.krebs> |
| Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | ahuggel, caulier.gilles |
| Priority: | NOR | ||
| Version: | 2.1.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.3.0 | |
| Sentry Crash Report: | |||
|
Description
Axel Krebs
2011-12-07 05:51:05 UTC
It crash in LibExiv2. Which version you use ? Look into Help/Components Info for details... Gilles Caulier Hi Gilles,
My components are as follows:
digiKam version 2.1.1
Exiv2 kann in JP2 speichern: Ja
Exiv2 kann in JPEG speichern: Ja
Exiv2 kann in PGF speichern: Ja
Exiv2 kann in PNG speichern: Ja
Exiv2 kann in TIFF speichern: Ja
Exiv2 unterstützt XMP-Metadaten: Ja
LibCImg: 130
LibClapack: Interne Bibliothek
LibExiv2: 0.21.1
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.7.2 (4.7.2)
LibKExiv2: 2.0.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.0.0
LibLCMS: 119
LibPGF: 6.11.24 - Interne Bibliothek
LibPNG: 1.2.46
LibQt: 4.7.4
LibRaw: 0.13.5
LibTIFF: LIBTIFF, Version 3.9.5 Copyright (c) 1988-1996 Sam Leffler
Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble-Funktion: 0.12.0 (stable release)
Parallelisiertes Entfernen von Mosaikmustern: Ja
Datenbanktreiber: QSQLITE
LibKface: 2.0.0
LibKipi: 1.2.0
LibOpenCV: 2.1.0
Libface: 0.2
Axel
Am 07.12.2011 07:42, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=288380
>
>
> Gilles Caulier <caulier.gilles@gmail.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |caulier.gilles@gmail.com
> Component|general |Metadata
>
>
>
>
> --- Comment #1 from Gilles Caulier <caulier gilles gmail com> 2011-12-07 06:42:08 ---
> It crash in LibExiv2. Which version you use ? Look into Help/Components Info
> for details...
>
> Gilles Caulier
>
ok, Now the idea is to find which image crash Exiv2 and try to reproduce the problem using Exiv2 command line tool. Gilles Caulier thank you for your considerations; the suggestet does not work, however. As described before, after re-importing several collections; I observed several sever problems; please see... <Fwd: [Bug 283681] After re-activating several collections, a huge number of raw pics cannot be opened> One consequence was, that I found the same tag ("Auto") at _two places; one at "Auto" (top level), one on "Freunde/Auto" (second level). When removing the tag "Auto" from the secondary level (Freunde/Auto), digiKam crashed. Therefore I feel not able to identify "the one" responsible pic that causes the crash (if, at all) :-( !! Months ago, I asked for/suggested pic check to protect the complete collection from harmful samples. What can I do? Axel Am 07.12.2011 16:22, schrieb Gilles Caulier: > https://bugs.kde.org/show_bug.cgi?id=288380 > > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |ahuggel@gmx.net > > > > > --- Comment #3 from Gilles Caulier <caulier gilles gmail com> 2011-12-07 15:22:43 --- > ok, Now the idea is to find which image crash Exiv2 and try to reproduce the > problem using Exiv2 command line tool. > > Gilles Caulier > Run KDEbugDialog and enable digiKam, KExiv2, KDcraw, Kipi, debug space. From a console, run digiKam through GDB, and look debug message before than crash appear to see which image is manage by digiKam. Report the full trace here. Gilles Caulier #Gilles:
as you wished... Hope this is ok.
bash: "digikam" (return): >>
ak@quadro:~$ digikam
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is
still in use, all queries will cease to work.
bash: "KExiv2" (return): >>
ak@quadro:~$ KExiv2
KExiv2: Befehl nicht gefunden. ("command not found")
bash: "KDcraw" (return): >>
ak@quadro:~$ KDcraw
KDcraw: Befehl nicht gefunden. ("command not found")
bash: "kipi" (return): >>
ak@quadro:~$ kipi
Der Befehl »kipi« wurde nicht gefunden, meinten Sie vielleicht:
Befehl »kiki« aus dem Paket »kiki« (universe)
kipi: Befehl nicht gefunden.
ak@quadro:~$ debug space
Der Befehl »debug« wurde nicht gefunden, meinten Sie vielleicht:
Befehl »ebug« aus dem Paket »libdevel-ebug-perl« (universe)
Befehl »udebug« aus dem Paket »openafs-client« (universe)
debug: Befehl nicht gefunden.
Axel
Am 10.12.2011 10:10, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=288380
>
>
>
>
>
> --- Comment #5 from Gilles Caulier <caulier gilles gmail com> 2011-12-10 09:10:28 ---
> Run KDEbugDialog and enable digiKam, KExiv2, KDcraw, Kipi, debug space.
>
>>From a console, run digiKam through GDB, and look debug message before than
> crash appear to see which image is manage by digiKam.
>
> Report the full trace here.
>
> Gilles Caulier
>
All messages are in German. I don't speak this language, i'm French... Gilles Caulier These info are a non sence... run kdebugdialog. It's a tool to turn on/off debug space in application as digiKam. select, "digiKam", "kexiv2", "kdcraw". http://docs.kde.org/stable/en/kdebase-runtime/kdebugdialog/index.html Close tool, and run digiKam from a console. Reproduce the problem and report all trace from the console here. Gilles Caulier Axel, What's new here ? Gilles Caulier Official digiKam 2.6.0 release is out since few days now : http://www.digikam.org/drupal/node/656 Please, check if this entry still valid, or update report accordingly. Thanks in advance. Gilles Caulier digiKam 3.5.0 is out. Can you give a fresh feedback about your report ? Crash still reproducible ? Thanks in advance Gilles Caulier In all case, crash is relevant of Exiv2 shared lib. Please report this crash in Exiv2 bugzilla. Gilles Caulier Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4 |