Summary: | digikam batch raw converter | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Marco Nolden <temp1> |
Component: | BatchQueueManager-RAWProcessing | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andresbajotierra, caulier.gilles |
Priority: | NOR | ||
Version: | 1.0.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.1.0 | |
Sentry Crash Report: |
Description
Marco Nolden
2009-10-18 21:15:30 UTC
Too bad the crash is not reproducible as the backtrace is not really complete. The functions from kipiplugins (rawbatch plugin) are missing: Thread 2 (Thread 0xa8fffb90 (LWP 25168)): [KCrash Handler] #6 QUrl (this=0xa4deca44, other=@0xa8fff240) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:120 #7 0xb58b9239 in KUrl (this=0xa4deca44, _u=@0xa8fff240) at /build/buildd/kde4libs-4.3.2/kdecore/io/kurl.cpp:468 #8 0x081f432c in ?? () #9 0xb5693425 in QMetaType::construct (type=316, copy=0xa8fff234) at kernel/qmetatype.cpp:1096 #10 0xb569a484 in queued_activate (sender=0xbecff78, signal=12, c=@0xd92f600, argv=0xa8fff02c, semaphore=0x0) at kernel/qobject.cpp:3008 #11 0xb569e0d7 in QMetaObject::activate (sender=0xbecff78, from_signal_index=12, to_signal_index=12, argv=0xa8fff02c) at kernel/qobject.cpp:3086 #12 0xb569ee42 in QMetaObject::activate (sender=0xbecff78, m=0xa040fad4, local_signal_index=1, argv=0xa8fff02c) at kernel/qobject.cpp:3187 #13 0xa03fa113 in ?? () from /usr/lib/kde4/kipiplugin_rawconverter.so #14 0xa03fc6f4 in ?? () from /usr/lib/kde4/kipiplugin_rawconverter.so #15 0xb5594132 in QThreadPrivate::start (arg=0xa8fff240) at thread/qthread_unix.cpp:188 #16 0xb52aa4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #17 0xb53a149e in clone () from /lib/tls/i686/cmov/libc.so.6 In any case it seems that Ubuntu doesn't provide debug information for kipiplugins. Closing as NEEDSINFO. Reopen if you find a way to reproduce the crash in a reliable way. Regards New digiKam 4.11.0 is available. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier |