Bug 303114 - Closing Digikam results in crash
Summary: Closing Digikam results in crash
Status: RESOLVED DOWNSTREAM
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (show other bugs)
Version: 2.6.0
Platform: unspecified Linux
: NOR critical
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-06 15:09 UTC by Mike Gutzschhahn
Modified: 2022-01-23 11:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Gutzschhahn 2012-07-06 15:09:19 UTC
After closing Digikam 2.6 crash handler pops up and give me


Application: digiKam (digikam), signal: Aborted
[Current thread is 1 (Thread 0xb0508b00 (LWP 1791))]

Thread 2 (Thread 0xaecffb40 (LWP 1798)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb40f9a4c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb47a626c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6
#3  0xb2ef704b in g_main_context_wait () from /usr/lib/libglib-2.0.so.0
#4  0xb2ef81cd in ?? () from /usr/lib/libglib-2.0.so.0
#5  0xb2ef87fa in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#6  0xb569f71f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#7  0xb566c33c in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#8  0xb566c631 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#9  0xb55599cc in QThread::exec() () from /usr/lib/libQtCore.so.4
#10 0xb564aacd in ?? () from /usr/lib/libQtCore.so.4
#11 0xb555cd90 in ?? () from /usr/lib/libQtCore.so.4
#12 0xb40f5e32 in start_thread () from /lib/libpthread.so.0
#13 0xb479893e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb0508b00 (LWP 1791)):
[KCrash Handler]
#6  0xffffe424 in __kernel_vsyscall ()
#7  0xb46dc30f in raise () from /lib/libc.so.6
#8  0xb46ddbf3 in abort () from /lib/libc.so.6
#9  0xb471a3a5 in __libc_message () from /lib/libc.so.6
#10 0xb4720ae2 in malloc_printerr () from /lib/libc.so.6
#11 0xb494fb2f in operator delete(void*) () from /usr/lib/libstdc++.so.6
#12 0xb5557000 in QMutex::~QMutex() () from /usr/lib/libQtCore.so.4
#13 0xb46df723 in __cxa_finalize () from /lib/libc.so.6
#14 0xb3e50044 in ?? () from /usr/lib/libopencv_highgui.so.2.3
#15 0xb3e913bd in _fini () from /usr/lib/libopencv_highgui.so.2.3
#16 0xb773bfc4 in ?? () from /lib/ld-linux.so.2
#17 0xb46df381 in __run_exit_handlers () from /lib/libc.so.6
#18 0xb46df40d in exit () from /lib/libc.so.6
#19 0xb46c73dd in __libc_start_main () from /lib/libc.so.6
#20 0x080c4549 in _start ()

Reproducible: Always

Steps to Reproduce:
1. Open
2. Close/Quit
Actual Results:  
Crash

Expected Results:  
Close normaly
Comment 1 Kyle Altendorf 2012-07-07 01:13:40 UTC
Ditto.  I am using digiKam 2.6.0 from the philip5 PPA under Kubuntu 12.04 Precise with KDE 4.8.3:

altendky@ly:~$ apt-cache policy kipi-plugins digikam
kipi-plugins:
  Installed: 4:2.6.0-precise~ppa3
  Candidate: 4:2.6.0-precise~ppa3
  Version table:
 *** 4:2.6.0-precise~ppa3 0
        400 http://ppa.launchpad.net/philip5/extra/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status
     4:2.5.0-1ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
digikam:
  Installed: 4:2.6.0-precise~ppa3
  Candidate: 4:2.6.0-precise~ppa3
  Version table:
 *** 4:2.6.0-precise~ppa3 0
        400 http://ppa.launchpad.net/philip5/extra/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status
     4:2.5.0-1ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

Perhaps there are other libraries I need to make certain are coming from philip5?  The result of the crash is:

Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4bcc274a00 (LWP 5180))]

Thread 3 (Thread 0x7f4ba8ad1700 (LWP 5182)):
#0  0x00007fffe735c8de in ?? ()
#1  0x00007f4bbdae115d in __GI_clock_gettime (clock_id=<optimized out>, tp=<optimized out>) at ../sysdeps/unix/clock_gettime.c:116
#2  0x00007f4bc6739bb4 in do_gettime (frac=0x7f4ba8ad0918, sec=0x7f4ba8ad0910) at tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4  0x00007f4bc6811b8d in QTimerInfoList::updateCurrentTime (this=0x7f4b9c002660) at kernel/qeventdispatcher_unix.cpp:343
#5  0x00007f4bc6811ec3 in QTimerInfoList::timerWait (this=0x7f4b9c002660, tm=...) at kernel/qeventdispatcher_unix.cpp:450
#6  0x00007f4bc681097c in timerSourcePrepareHelper (src=<optimized out>, timeout=0x7f4ba8ad09ec) at kernel/qeventdispatcher_glib.cpp:136
#7  0x00007f4bc6810a25 in timerSourcePrepare (source=<optimized out>, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#8  0x00007f4bbee71846 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007f4bbee71f5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f4bbee72164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f4bc6811426 in QEventDispatcherGlib::processEvents (this=0x7f4b9c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#12 0x00007f4bc67e0c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#13 0x00007f4bc67e0ed7 in QEventLoop::exec (this=0x7f4ba8ad0b50, flags=...) at kernel/qeventloop.cpp:204
#14 0x00007f4bc66dffa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#15 0x00007f4bc67c09ff in QInotifyFileSystemWatcherEngine::run (this=0x2213140) at io/qfilesystemwatcher_inotify.cpp:248
#16 0x00007f4bc66e2fcb in QThreadPrivate::start (arg=0x2213140) at thread/qthread_unix.cpp:298
#17 0x00007f4bc1224e9a in start_thread (arg=0x7f4ba8ad1700) at pthread_create.c:308
#18 0x00007f4bc590f4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#19 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f4ba2aef700 (LWP 5185)):
#0  0x00007fffe735c8de in ?? ()
#1  0x00007f4bbdae115d in __GI_clock_gettime (clock_id=<optimized out>, tp=<optimized out>) at ../sysdeps/unix/clock_gettime.c:116
#2  0x00007f4bc6739bb4 in do_gettime (frac=0x7f4ba2aee918, sec=0x7f4ba2aee910) at tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4  0x00007f4bc6811b8d in QTimerInfoList::updateCurrentTime (this=0x7f4b90002460) at kernel/qeventdispatcher_unix.cpp:343
#5  0x00007f4bc6811ec3 in QTimerInfoList::timerWait (this=0x7f4b90002460, tm=...) at kernel/qeventdispatcher_unix.cpp:450
#6  0x00007f4bc681097c in timerSourcePrepareHelper (src=<optimized out>, timeout=0x7f4ba2aee9ec) at kernel/qeventdispatcher_glib.cpp:136
#7  0x00007f4bc6810a25 in timerSourcePrepare (source=<optimized out>, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#8  0x00007f4bbee71846 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007f4bbee71f5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f4bbee72164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f4bc6811426 in QEventDispatcherGlib::processEvents (this=0x7f4b900008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#12 0x00007f4bc67e0c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#13 0x00007f4bc67e0ed7 in QEventLoop::exec (this=0x7f4ba2aeeb50, flags=...) at kernel/qeventloop.cpp:204
#14 0x00007f4bc66dffa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#15 0x00007f4bc67c09ff in QInotifyFileSystemWatcherEngine::run (this=0x286d670) at io/qfilesystemwatcher_inotify.cpp:248
#16 0x00007f4bc66e2fcb in QThreadPrivate::start (arg=0x286d670) at thread/qthread_unix.cpp:298
#17 0x00007f4bc1224e9a in start_thread (arg=0x7f4ba2aef700) at pthread_create.c:308
#18 0x00007f4bc590f4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#19 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f4bcc274a00 (LWP 5180)):
[KCrash Handler]
#6  __strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:214
#7  0x00007f4bc29f89c5 in cvFindType () from /usr/lib/libopencv_core.so.2.3
#8  0x00007f4bc29f89e9 in cvUnregisterType () from /usr/lib/libopencv_core.so.2.3
#9  0x00007f4bc5858d3d in __cxa_finalize (d=0x7f4bc2cf43c0) at cxa_finalize.c:56
#10 0x00007f4bc2968516 in ?? () from /usr/lib/libopencv_core.so.2.3
#11 0x0000000000000135 in ?? ()
#12 0x00007fffe72ae9e0 in ?? ()
#13 0x00007fffe72af400 in ?? ()
#14 0x00007f4bc2aa83e1 in _fini () from /usr/lib/libopencv_core.so.2.3
#15 0x00007fffe72af400 in ?? ()
#16 0x00007f4bcc0c692d in _dl_fini () at dl-fini.c:259
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Comment 2 caulier.gilles 2012-07-07 05:09:35 UTC
It crash in OpenCV shared library, not digiKam... Check your system...

Gilles Caulier
Comment 3 Mike Gutzschhahn 2012-07-09 12:21:03 UTC
I've mounted an SMB or FTP share with fuse or curlftpfs. When i close Digikam it causes a disconnect and giving the mount folder wired user and group rights like

d?????????  ? ?     ?           ?            ? smbmount/

When i mount in verbose mode it seems a process (maybe thumbs) is working in the background. After i quit nothing special is shown in the terminal. Any suggestion how to fix that?

Thanks 4 your support
Comment 4 caulier.gilles 2012-07-09 12:30:52 UTC
Mike,

your report is not relevant of this entry...

Also, i don't have any ideas to help you...

Gilles Caulier
Comment 5 Mike Gutzschhahn 2012-07-09 12:37:08 UTC
Ok, thanks anyway
Comment 6 caulier.gilles 2012-07-22 15:25:34 UTC
Mike check and update OpenCV library package. It' not a digiKam relevant crash...

Gilles Caulier