Bug 267408 - digikam new metadata template editor crash during save
Summary: digikam new metadata template editor crash during save
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Bqm-AssignTemplate (show other bugs)
Version: 2.0.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-01 21:20 UTC by Bruno Friedmann
Modified: 2022-09-08 07:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.12.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Friedmann 2011-03-01 21:20:27 UTC
Application: digikam (2.0.0-beta3)
KDE Platform Version: 4.6.00 (4.6.0)
Qt Version: 4.7.1
Operating System: Linux 2.6.37.1-2-desktop x86_64
Distribution: "openSUSE 11.4 RC 1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: I've edited a new template for author when I try to save it crash with the debug attached

The crash can be reproduced some of the time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f4dc93cd860 (LWP 16884))]

Thread 5 (Thread 0x7f4da8fde700 (LWP 16885)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f4dc222e14b in wait (this=<value optimized out>, mutex=0xc48f28, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0xc48f28, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x0000000000621c00 in Digikam::ScanController::run (this=0xc334e0) at /usr/src/debug/digikam2-1.9.92svn.rev1218712/core/digikam/scancontroller.cpp:602
#4  0x00007f4dc222da5e in QThreadPrivate::start (arg=0xc334e0) at thread/qthread_unix.cpp:285
#5  0x00007f4dc1f9ea3f in start_thread (arg=0x7f4da8fde700) at pthread_create.c:297
#6  0x00007f4dc041a67d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f4da87dd700 (LWP 16886)):
#0  next_valid_source (context=0xc3e6d0, priority=0x7f4da87dcbbc) at gmain.c:2486
#1  g_main_context_prepare (context=0xc3e6d0, priority=0x7f4da87dcbbc) at gmain.c:2794
#2  0x00007f4dba9e2fa9 in g_main_context_iterate (context=0xc3e6d0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3071
#3  0x00007f4dba9e3650 in g_main_context_iteration (context=0xc3e6d0, may_block=1) at gmain.c:3154
#4  0x00007f4dc2341976 in QEventDispatcherGlib::processEvents (this=0xbf13e0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#5  0x00007f4dc2316052 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f4dc2316265 in QEventLoop::exec (this=0x7f4da87dcce0, flags=...) at kernel/qeventloop.cpp:201
#7  0x00007f4dc222b1e4 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#8  0x00007f4dc22f7968 in QInotifyFileSystemWatcherEngine::run (this=0xd2fe60) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007f4dc222da5e in QThreadPrivate::start (arg=0xd2fe60) at thread/qthread_unix.cpp:285
#10 0x00007f4dc1f9ea3f in start_thread (arg=0x7f4da87dd700) at pthread_create.c:297
#11 0x00007f4dc041a67d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f4da7fdc700 (LWP 16919)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f4dc222e14b in wait (this=<value optimized out>, mutex=0xe56fc8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0xe56fc8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x00007f4dc5ee20d7 in Digikam::ParkingThread::run (this=0xe56fb0) at /usr/src/debug/digikam2-1.9.92svn.rev1218712/core/libs/threads/threadmanager.cpp:119
#4  0x00007f4dc222da5e in QThreadPrivate::start (arg=0xe56fb0) at thread/qthread_unix.cpp:285
#5  0x00007f4dc1f9ea3f in start_thread (arg=0x7f4da7fdc700) at pthread_create.c:297
#6  0x00007f4dc041a67d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f4d8c7d5700 (LWP 21140)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:211
#1  0x00007f4dc222e0b2 in wait (this=<value optimized out>, mutex=0xe1adb0, time=30000) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0xe1adb0, time=30000) at thread/qwaitcondition_unix.cpp:160
#3  0x00007f4dc2223eb8 in QThreadPoolThread::run (this=0x31e1e10) at concurrent/qthreadpool.cpp:140
#4  0x00007f4dc222da5e in QThreadPrivate::start (arg=0x31e1e10) at thread/qthread_unix.cpp:285
#5  0x00007f4dc1f9ea3f in start_thread (arg=0x7f4d8c7d5700) at pthread_create.c:297
#6  0x00007f4dc041a67d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f4dc93cd860 (LWP 16884)):
[KCrash Handler]
#6  0x00007f4dc2275c3a in QString::append (this=0x7fff74b33e60, str=...) at tools/qstring.cpp:1533
#7  0x00007f4dc587ac1a in operator+= (this=<value optimized out>) at /usr/include/QtCore/qstring.h:281
#8  operator+ (this=<value optimized out>) at /usr/include/QtCore/qstring.h:1024
#9  Digikam::ImageInfo::filePath (this=<value optimized out>) at /usr/src/debug/digikam2-1.9.92svn.rev1218712/core/libs/database/imageinfo.cpp:600
#10 0x00007f4dc587af19 in Digikam::ImageInfo::fileUrl (this=<value optimized out>) at /usr/src/debug/digikam2-1.9.92svn.rev1218712/core/libs/database/imageinfo.cpp:577
#11 0x00000000006d4b87 in Digikam::QueueListView::slotThumbnailLoaded (this=0xdb04b0, desc=..., pix=...) at /usr/src/debug/digikam2-1.9.92svn.rev1218712/core/utilities/queuemanager/queuelist.cpp:643
#12 0x00000000006d9a0e in Digikam::QueueListView::qt_metacall (this=0xdb04b0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff74b340b0) at /usr/src/debug/digikam2-1.9.92svn.rev1218712/build/core/utilities/queuemanager/queuelist.moc:97
#13 0x00007f4dc232bdef in QMetaObject::activate (sender=0x1ca33d0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff74b340b0) at kernel/qobject.cpp:3272
#14 0x00007f4dc5eb8007 in Digikam::ThumbnailLoadThread::signalThumbnailLoaded (this=<value optimized out>, _t1=<value optimized out>, _t2=<value optimized out>) at /usr/src/debug/digikam2-1.9.92svn.rev1218712/build/core/digikam/thumbnailloadthread.moc:109
#15 0x00007f4dc5ebe343 in Digikam::ThumbnailLoadThread::slotThumbnailLoaded (this=0x1ca33d0, description=..., thumb=<value optimized out>) at /usr/src/debug/digikam2-1.9.92svn.rev1218712/core/libs/threadimageio/thumbnailloadthread.cpp:767
#16 0x00007f4dc5ebe70e in Digikam::ThumbnailLoadThread::slotThumbnailsAvailable (this=0x1ca33d0) at /usr/src/debug/digikam2-1.9.92svn.rev1218712/core/libs/threadimageio/thumbnailloadthread.cpp:729
#17 0x00007f4dc5ebe944 in Digikam::ThumbnailLoadThread::qt_metacall (this=0x1ca33d0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x5552370) at /usr/src/debug/digikam2-1.9.92svn.rev1218712/build/core/digikam/thumbnailloadthread.moc:93
#18 0x00007f4dc232aa6a in QObject::event (this=0x1ca33d0, e=<value optimized out>) at kernel/qobject.cpp:1211
#19 0x00007f4dc124dd14 in QApplicationPrivate::notify_helper (this=0xb6eb50, receiver=0x1ca33d0, e=0xf20b20) at kernel/qapplication.cpp:4445
#20 0x00007f4dc125622a in QApplication::notify (this=<value optimized out>, receiver=0x1ca33d0, e=0xf20b20) at kernel/qapplication.cpp:4324
#21 0x00007f4dc2c779e6 in KApplication::notify (this=0x7fff74b34e20, receiver=0x1ca33d0, event=0xf20b20) at /usr/src/debug/kdelibs-4.6.0/kdeui/kernel/kapplication.cpp:311
#22 0x00007f4dc2316bfc in QCoreApplication::notifyInternal (this=0x7fff74b34e20, receiver=0x1ca33d0, event=0xf20b20) at kernel/qcoreapplication.cpp:732
#23 0x00007f4dc231a3f5 in sendEvent (receiver=0x0, event_type=0, data=0xb0c540) at kernel/qcoreapplication.h:215
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xb0c540) at kernel/qcoreapplication.cpp:1373
#25 0x00007f4dc2341783 in sendPostedEvents (s=<value optimized out>) at kernel/qcoreapplication.h:220
#26 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:277
#27 0x00007f4dba9e2bd3 in g_main_dispatch (context=0xb71ce0) at gmain.c:2440
#28 g_main_context_dispatch (context=0xb71ce0) at gmain.c:3013
#29 0x00007f4dba9e33b0 in g_main_context_iterate (context=0xb71ce0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3091
#30 0x00007f4dba9e3650 in g_main_context_iteration (context=0xb71ce0, may_block=1) at gmain.c:3154
#31 0x00007f4dc234191f in QEventDispatcherGlib::processEvents (this=0xb12660, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#32 0x00007f4dc12f2d8e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x00007f4dc2316052 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#34 0x00007f4dc2316265 in QEventLoop::exec (this=0x7fff74b34c60, flags=...) at kernel/qeventloop.cpp:201
#35 0x00007f4dc231a6ab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#36 0x000000000068a42d in main (argc=11862272, argv=0x7fff74b35600) at /usr/src/debug/digikam2-1.9.92svn.rev1218712/core/digikam/main.cpp:232

This bug may be a duplicate of or related to bug 266632.

Possible duplicates by query: bug 266632, bug 262268.

Reported using DrKonqi
Comment 1 caulier.gilles 2011-03-15 09:07:41 UTC
Marcel, Why Queue Manager is the source of crash here ? Backtrace is corrupted ?

Bruno, try again and give us a new backtrace to see if info are reproducible

Gilles Caulier
Comment 2 caulier.gilles 2011-07-02 10:02:07 UTC
digiKam 2.0.0 RC is out. Please check if crash is reproducible with this version.

Thanks in advance

Gilles Caulier
Comment 3 caulier.gilles 2015-06-27 13:45:18 UTC
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles caulier
Comment 4 Bruno Friedmann 2015-06-30 20:02:24 UTC
From what I've seen in a quick test, those seems to have disappear.
If something similar happen, I will open a new bug report.