Summary: | digiKam crash when left open | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Antti Poikela <antti.poikela> |
Component: | Portability-Runtime | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andresbajotierra, caulier.gilles |
Priority: | NOR | ||
Version: | 1.6.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.6.0 | |
Sentry Crash Report: |
Description
Antti Poikela
2010-12-13 22:33:42 UTC
backtrace is uncomplete. please install debug package and try again. Run also digiKam into GDB to get a complete backtrace Gilles Caulier I installed "digikam-debuginfo" but didn't get any better traces. The crash occurs every time I close showFoto: 1. Open shoFoto 2. Open any image in application 3. Close application -> crash Using gdb I got the following trace: Program received signal SIGABRT, Aborted. 0x00007ffff46dd9e5 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff46dd9e5 in raise () from /lib64/libc.so.6 #1 0x00007ffff46deee6 in abort () from /lib64/libc.so.6 #2 0x00007ffff4718c53 in __libc_message () from /lib64/libc.so.6 #3 0x00007ffff471e226 in malloc_printerr () from /lib64/libc.so.6 #4 0x00007ffff4f18eb9 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib64/libstdc++.so.6 #5 0x00007ffff46e04e1 in __run_exit_handlers () from /lib64/libc.so.6 #6 0x00007ffff46e0535 in exit () from /lib64/libc.so.6 #7 0x00007ffff46c9b84 in __libc_start_main () from /lib64/libc.so.6 #8 0x0000000000412c69 in _start () at ../sysdeps/x86_64/elf/start.S:113 This doesn't look exactly helpful either. Just point out if there is something else I could do. [Comment from a bug triager] This is likely to be an OpenSuse + Strigi bug, being tracked at bug 257944. (It is actually about Dolphin, but there are reports about other applications crashing on exit too) Regards [Comment from a bug triager] Merging with bug 257944. Thanks *** This bug has been marked as a duplicate of bug 257944 *** Fixed with https://bugs.kde.org/show_bug.cgi?id=257944 |