| Summary: | crash if I name a face | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Johannes <listen> |
| Component: | Faces-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | grave | CC: | caulier.gilles, listen |
| Priority: | NOR | ||
| Version: | 4.7.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.0.0 | |
| Sentry Crash Report: | |||
| Attachments: | no start of digikam under gdb | ||
Created attachment 91373 [details]
no start of digikam under gdb
how to start digikam to get a bug trace?
Install digiKam debug package to have a suitable GDB backtrace Gilles Caulier sorry but digikam debug package is installed. if I see it right I have to install nearly all of KDE debug packages. see output when start gdb: .. Reading symbols from /usr/bin/digikam...Reading symbols from /usr/lib/debug/usr/bin/digikam.debug...done. done. (gdb) maybe this could help?
Temporary breakpoint 1, main (argc=1, argv=0x7fffffffdde8) at /usr/src/debug/digikam-4.7.0/core/app/main/main.cpp:71
71 {
(gdb)
(gdb)
(gdb) start
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Temporary breakpoint 2 at 0x49fdb0: file /usr/src/debug/digikam-4.7.0/core/app/main/main.cpp, line 71.
Starting program: /usr/bin/digikam
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Traceback (most recent call last):
File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", line 9, in <module>
from gobject import register
File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
import gdb.backtrace
ImportError: No module named backtrace
Temporary breakpoint 2, main (argc=1, argv=0x7fffffffdde8) at /usr/src/debug/digikam-4.7.0/core/app/main/main.cpp:71
71 {
(gdb)
sorry for lot of comments. I checked parallel consumption of memory use and when using "name faces" memory use grows up to max (overflow) to get killed by OS for I could use this with 4.6.0 it seems this bug is renewed in 4.7.0 but I'm not quite sure if it works first with 4.7.0 too until some updates in opensuse 13.1 same behaviour when downgrade to 3.5.0 (original for opensuse 13.1) New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier I will try as soon as on opensuse delivers 4.11.x May be I will try to compile it myself during next weekend Johannes Am 24.06.2015 um 18:17 schrieb Gilles Caulier: > https://bugs.kde.org/show_bug.cgi?id=344735 > > --- Comment #7 from Gilles Caulier <caulier.gilles@gmail.com> --- > New digiKam 4.11.0 is available : > > https://www.digikam.org/node/740 > > Can you reproduce the problem with this release ? > > Gilles Caulier > Actually I updated to 4.11.0 but still crashes main window. When starting on command line I get again following output: (later I will try again a gdb crash report) johannes@Johannes-Desktop:~> digikam digikam(2046)/KEXIV2: Cannot remove Xmp tag using Exiv2 (Error # 35 : Keine Namensrauminformation für den XMP-Präfix `acdsee' verfügbar digikam(2046)/KEXIV2: Cannot remove Xmp tag using Exiv2 (Error # 35 : Keine Namensrauminformation für den XMP-Präfix `acdsee' verfügbar digikam(2046)/KEXIV2: Cannot remove Xmp tag using Exiv2 (Error # 35 : Keine Namensrauminformation für den XMP-Präfix `acdsee' verfügbar digikam(2046)/KEXIV2: Cannot set Xmp tag string into image using Exiv2 (Error # 35 : Keine Namensrauminformation für den XMP-Präfix `acdsee' verfügbar digikam(2046)/KEXIV2: Cannot remove Xmp tag using Exiv2 (Error # 35 : Keine Namensrauminformation für den XMP-Präfix `acdsee' verfügbar digikam(2046)/KEXIV2: Cannot set Xmp tag string into image using Exiv2 (Error # 35 : Keine Namensrauminformation für den XMP-Präfix `acdsee' verfügbar Getötet johannes@Johannes-Desktop:~> Johannes I will try as soon as on opensuse delivers 4.11.x May be I will try to compile it myself during next weekend Johannes Am 24.06.2015 um 18:17 schrieb Gilles Caulier: > https://bugs.kde.org/show_bug.cgi?id=344735 > > --- Comment #7 from Gilles Caulier <caulier.gilles@gmail.com> --- > New digiKam 4.11.0 is available : > > https://www.digikam.org/node/740 > > Can you reproduce the problem with this release ? > > Gilles Caulier > libkexiv2 from Kdegraphics/libs need to be updated to fix this problem. Gilles Caulier *** This bug has been marked as a duplicate of bug 347753 *** Problem is fixed with new 7.0.0-beta1 through this long story from this bug https://bugs.kde.org/show_bug.cgi?id=399923 You can test digiKam 7.0.0-beta1 with bundle available here: https://download.kde.org/unstable/digikam/ Don't hesitate to give us a fresh feedback about his entry. Thanks in advance Gilles Caulier |
silent crash with not opening bug tracking window, often it looks like name is stored before crah in database Reproducible: Always Steps to Reproduce: 1. go to faces 2. name one face in picture overview 3. wait a few seconds to see digikam crash (there is a lot of activity on hd at this time, stopping two seconds after the crash) Expected Results: save the name and wait to go on to name more faces try to open digikam under gdb end up with line: Temporary breakpoint 1, main (argc=1, argv=0x7fffffffdde8) at /usr/src/debug/digikam-4.7.0/core/app/main/main.cpp:71 71 { (gdb) see also bug trace file: gdb_start