Summary: | digiKam crashes while renaming several files | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Bitta Jam <bittajam> |
Component: | AdvancedRename-engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | basosergiou, caulier.gilles, cfeck, dantou, eiapopeia13, freekdekruijf, Julien, petri.damsten, roland.schmalenberg, romain.pub, royhug, samuel.gilbert, thomas.vergnaud, vikimaus, Vojtech.Zeisek, volker27, w4bx |
Priority: | NOR | ||
Version: | 1.5.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.7.0 | |
Sentry Crash Report: | |||
Attachments: |
Folder containing 2 JPEG files that will make digiKam crash when using the Rename feature
Stdout and stderr of a debug build of digiKam when the crash occurs New crash information added by DrKonqi |
Description
Bitta Jam
2010-05-14 16:57:56 UTC
I can confirm the exact same issue with digiKam 1.2.0 on KDE 4.4.3 using Archlinux. It's 100% reproducible. Here is what you get when running digiKam from a terminal and trying to rename multiple images : $ digikam Time elapsed: 13 ms Time elapsed: 4 ms Model: Time elapsed: 27 ms TextureColorizer: Time elapsed: 6 ms Time elapsed: 5 ms Time elapsed: 4 ms Model: Time elapsed: 13 ms digikam(12120)/digikam (core): ThumbnailLoadThread::load: No thumbnail size specified. Refusing to load thumbnail. digikam(12120)/digikam (core): ThumbnailLoadThread::load: No thumbnail size specified. Refusing to load thumbnail. digikam(12120)/digikam (core): ThumbnailLoadThread::load: No thumbnail size specified. Refusing to load thumbnail. Enchant dict for "en_US" 0x6b86370 KCrash: Application 'digikam' crashing... sock_file=/home/prozzaks/.kde4/socket-shinny/kdeinit4__0 [1]+ Stopped digikam Hmm can not confirm this, 1.2.0 from the Archlinux repos as well as digiKam trunk are running fine here. Created attachment 43778 [details]
Folder containing 2 JPEG files that will make digiKam crash when using the Rename feature
Extract the content of the archive in a one of your digiKam collections and than use the digiKam rename feature. Even clicking "Cancel" in the rename window will cause the crash.
Created attachment 43779 [details]
Stdout and stderr of a debug build of digiKam when the crash occurs
Hmm looks much more like a database problem to me, at least when I take a look at the log file you attached here. Andi, if any database error messages as in the log above appear after the application crashed, then it's due to the crash. Sometimes a thread seems to continue to run, but the application is dead. It's not a database problem until the error messages appear before the crash. Samuel: Is your backtrace identical to the one posted by Olga above? Created attachment 47620 [details]
New crash information added by DrKonqi
I confirm the reproducable crashes, after successful renaming of hundreds of jpeg-files I tried to rename multiple files of RAW type, too. No way to do that, only renaming raw-file by raw-file will work.
Andi, this one is for you: #5 QBasicAtomicInt::ref (this=0x4d92000, settings=...) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #6 QList (this=0x4d92000, settings=...) at /usr/include/qt4/QtCore/qlist.h:114 #7 QForeachContainer (this=0x4d92000, settings=...) at /usr/include/qt4/QtCore/qglobal.h:2231 #8 Digikam::Parser::parse (this=0x4d92000, settings=...) at /build/buildd/digikam-1.2.0/utilities/advancedrename/common/parser.cpp:168 #9 0x000000000075f1e4 in Digikam::Parser::invalidModifiers (this=0x7fffc1a45c40, settings=...) at /build/buildd/digikam-1.2.0/utilities/advancedrename/common/parser.cpp:135 #10 0x0000000000758317 in Digikam::Highlighter::highlightBlock (this=0x6409c60, text=<value optimized out>) at /build/buildd/digikam-1.2.0/utilities/advancedrename/common/highlighter.cpp:95 Already fixed in trunk? Hm this backrace is rather old, the line mentioned in there doesn't contain any qlist related code. So I would say it is fixed, but to be sure a new backtrace should be made. *** Bug 249148 has been marked as a duplicate of this bug. *** Andy, Can we close this file as fixed for 1.5.0 ? Gilles Caulier *** Bug 256314 has been marked as a duplicate of this bug. *** See #256314. It can be reproduced with 1.5.0 release Gilles Caulier I still can not confirm this, there must be something wrong on the target systems. I tried this with debug and release builds, with official packages (from Archlinux) etc... no crash. I have same problem. openSUSE 11.3 (64b), KDE 4.4.4 release 3, digiKam 1.5.0. When I select more than 1 file to rename, the program always crashes. Application: digiKam (digikam), signal: Segmentation fault [Current thread is 1 (Thread 0x7f2ba5e657c0 (LWP 8081))] Thread 13 (Thread 0x7f2b91c47710 (LWP 8082)): #0 0x00007f2b9ddb539c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f2ba05bb2bb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x00000000006b5a0d in ?? () #3 0x00007f2ba05babf5 in ?? () from /usr/lib64/libQtCore.so.4 #4 0x00007f2b9ddb0a4f in start_thread () from /lib64/libpthread.so.0 #5 0x00007f2b9f8c682d in clone () from /lib64/libc.so.6 #6 0x0000000000000000 in ?? () Thread 12 (Thread 0x7f2b91446710 (LWP 8085)): #0 0x00007f2b9911e52e in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #1 0x00007f2b9911fde5 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f2b99120510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f2ba06ca6d6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #4 0x00007f2ba06a1292 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #5 0x00007f2ba06a1495 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #6 0x00007f2ba05b82cf in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x00007f2ba05babf5 in ?? () from /usr/lib64/libQtCore.so.4 #8 0x00007f2b9ddb0a4f in start_thread () from /lib64/libpthread.so.0 #9 0x00007f2b9f8c682d in clone () from /lib64/libc.so.6 #10 0x0000000000000000 in ?? () Thread 11 (Thread 0x7f2b90a38710 (LWP 8086)): #0 0x00007f2ba06cb346 in ?? () from /usr/lib64/libQtCore.so.4 #1 0x00007f2ba06c9f0c in ?? () from /usr/lib64/libQtCore.so.4 #2 0x00007f2ba06c9fb5 in ?? () from /usr/lib64/libQtCore.so.4 #3 0x00007f2b9911ef7f in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #4 0x00007f2b9911fe69 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x00007f2b99120510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x00007f2ba06ca6d6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #7 0x00007f2ba06a1292 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #8 0x00007f2ba06a1495 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #9 0x00007f2ba05b82cf in QThread::exec() () from /usr/lib64/libQtCore.so.4 #10 0x00007f2ba05babf5 in ?? () from /usr/lib64/libQtCore.so.4 #11 0x00007f2b9ddb0a4f in start_thread () from /lib64/libpthread.so.0 #12 0x00007f2b9f8c682d in clone () from /lib64/libc.so.6 #13 0x0000000000000000 in ?? () Thread 10 (Thread 0x7f2b8d251710 (LWP 8087)): #0 0x00007f2b9ddb539c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f2ba05bb2bb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x00007f2ba33b8d38 in ?? () from /usr/lib64/libdigikamcore.so.1 #3 0x00007f2ba05babf5 in ?? () from /usr/lib64/libQtCore.so.4 #4 0x00007f2b9ddb0a4f in start_thread () from /lib64/libpthread.so.0 #5 0x00007f2b9f8c682d in clone () from /lib64/libc.so.6 #6 0x0000000000000000 in ?? () Thread 9 (Thread 0x7f2b8ca50710 (LWP 8088)): #0 0x00007f2b9ddb468e in __pthread_mutex_unlock_usercnt () from /lib64/libpthread.so.0 #1 0x00007f2b9911ef72 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f2b9911fe69 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f2b99120510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x00007f2ba06ca6d6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #5 0x00007f2ba06a1292 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #6 0x00007f2ba06a1495 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #7 0x00007f2ba05b82cf in QThread::exec() () from /usr/lib64/libQtCore.so.4 #8 0x00007f2ba05babf5 in ?? () from /usr/lib64/libQtCore.so.4 #9 0x00007f2b9ddb0a4f in start_thread () from /lib64/libpthread.so.0 #10 0x00007f2b9f8c682d in clone () from /lib64/libc.so.6 #11 0x0000000000000000 in ?? () Thread 8 (Thread 0x7f2b87fff710 (LWP 8089)): #0 0xffffffffff600177 in ?? () #1 0x00007fff169707a1 in ?? () #2 0x00007f2b975582a3 in clock_gettime () from /lib64/librt.so.1 #3 0x00007f2ba06c75ff in ?? () from /usr/lib64/libQtCore.so.4 #4 0x00007f2ba06caf4d in ?? () from /usr/lib64/libQtCore.so.4 #5 0x00007f2ba06cb2d5 in ?? () from /usr/lib64/libQtCore.so.4 #6 0x00007f2ba06c9f0c in ?? () from /usr/lib64/libQtCore.so.4 #7 0x00007f2ba06c9fb5 in ?? () from /usr/lib64/libQtCore.so.4 #8 0x00007f2b9911ef7f in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #9 0x00007f2b9911fe69 in ?? () from /usr/lib64/libglib-2.0.so.0 #10 0x00007f2b99120510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #11 0x00007f2ba06ca6d6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #12 0x00007f2ba06a1292 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #13 0x00007f2ba06a1495 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #14 0x00007f2ba05b82cf in QThread::exec() () from /usr/lib64/libQtCore.so.4 #15 0x00007f2ba05babf5 in ?? () from /usr/lib64/libQtCore.so.4 #16 0x00007f2b9ddb0a4f in start_thread () from /lib64/libpthread.so.0 #17 0x00007f2b9f8c682d in clone () from /lib64/libc.so.6 #18 0x0000000000000000 in ?? () Thread 7 (Thread 0x7f2b7fdf9710 (LWP 8090)): #0 0x00007f2b9ddb5709 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f2b85add951 in metronom_sync_loop () from /usr/lib64/libxine.so.1 #2 0x00007f2b9ddb0a4f in start_thread () from /lib64/libpthread.so.0 #3 0x00007f2b9f8c682d in clone () from /lib64/libc.so.6 #4 0x0000000000000000 in ?? () Thread 6 (Thread 0x7f2b7e9bc710 (LWP 8091)): #0 0x00007f2b9ddb5709 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f2b85aeb98f in video_out_loop () from /usr/lib64/libxine.so.1 #2 0x00007f2b9ddb0a4f in start_thread () from /lib64/libpthread.so.0 #3 0x00007f2b9f8c682d in clone () from /lib64/libc.so.6 #4 0x0000000000000000 in ?? () Thread 5 (Thread 0x7f2b7e1bb710 (LWP 8092)): #0 0xffffffffff600177 in ?? () #1 0x00007fff169707a1 in ?? () #2 0x00007f2b975582a3 in clock_gettime () from /lib64/librt.so.1 #3 0x00007f2ba06c75ff in ?? () from /usr/lib64/libQtCore.so.4 #4 0x00007f2ba06caf4d in ?? () from /usr/lib64/libQtCore.so.4 #5 0x00007f2ba06cb2d5 in ?? () from /usr/lib64/libQtCore.so.4 #6 0x00007f2ba06c9f0c in ?? () from /usr/lib64/libQtCore.so.4 #7 0x00007f2b9911ef7f in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #8 0x00007f2b9911fe69 in ?? () from /usr/lib64/libglib-2.0.so.0 #9 0x00007f2b99120510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #10 0x00007f2ba06ca6d6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #11 0x00007f2ba06a1292 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #12 0x00007f2ba06a1495 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #13 0x00007f2ba05b82cf in QThread::exec() () from /usr/lib64/libQtCore.so.4 #14 0x00007f2b85d3b3b4 in ?? () from /usr/lib64/kde4/plugins/phonon_backend/phonon_xine.so #15 0x00007f2ba05babf5 in ?? () from /usr/lib64/libQtCore.so.4 #16 0x00007f2b9ddb0a4f in start_thread () from /lib64/libpthread.so.0 #17 0x00007f2b9f8c682d in clone () from /lib64/libc.so.6 #18 0x0000000000000000 in ?? () Thread 4 (Thread 0x7f2b7d7b0710 (LWP 8095)): #0 0x00007f2b9f8bd6b3 in poll () from /lib64/libc.so.6 #1 0x00007f2b7d7b59d7 in ao_alsa_handle_event_thread () from /usr/lib64/xine/plugins/1.29/xineplug_ao_out_alsa.so #2 0x00007f2b9ddb0a4f in start_thread () from /lib64/libpthread.so.0 #3 0x00007f2b9f8c682d in clone () from /lib64/libc.so.6 #4 0x0000000000000000 in ?? () Thread 3 (Thread 0x7f2b7cfaf710 (LWP 8096)): #0 0x00007f2b9ddb539c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f2b85aef96b in ao_loop () from /usr/lib64/libxine.so.1 #2 0x00007f2b9ddb0a4f in start_thread () from /lib64/libpthread.so.0 #3 0x00007f2b9f8c682d in clone () from /lib64/libc.so.6 #4 0x0000000000000000 in ?? () Thread 2 (Thread 0x7f2b79d19710 (LWP 8157)): #0 0x00007f2b9ddb539c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f2ba05bb2bb in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x00000000006ff72a in ?? () #3 0x00007f2ba05babf5 in ?? () from /usr/lib64/libQtCore.so.4 #4 0x00007f2b9ddb0a4f in start_thread () from /lib64/libpthread.so.0 #5 0x00007f2b9f8c682d in clone () from /lib64/libc.so.6 #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f2ba5e657c0 (LWP 8081)): [KCrash Handler] #5 0x00000000006fc9b2 in ?? () #6 0x00000000006fcfa4 in ?? () #7 0x00000000006f775c in ?? () #8 0x00007f2ba12748e3 in ?? () from /usr/lib64/libQtGui.so.4 #9 0x00007f2ba1274aa0 in ?? () from /usr/lib64/libQtGui.so.4 #10 0x00007f2ba1274de2 in QSyntaxHighlighter::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtGui.so.4 #11 0x00007f2ba06b5a1f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #12 0x00007f2ba162447a in QTextDocument::contentsChange(int, int, int) () from /usr/lib64/libQtGui.so.4 #13 0x00007f2ba12374ca in ?? () from /usr/lib64/libQtGui.so.4 #14 0x00007f2ba1273dc8 in QSyntaxHighlighter::setDocument(QTextDocument*) () from /usr/lib64/libQtGui.so.4 #15 0x00007f2ba1273ebd in QSyntaxHighlighter::~QSyntaxHighlighter() () from /usr/lib64/libQtGui.so.4 #16 0x00007f2ba1ca7599 in Sonnet::Highlighter::~Highlighter() () from /usr/lib64/libkdeui.so.5 #17 0x00007f2ba1bc913d in KTextEdit::~KTextEdit() () from /usr/lib64/libkdeui.so.5 #18 0x00000000006f01f9 in ?? () #19 0x00007f2ba06b28b4 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #20 0x00007f2ba1024535 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #21 0x00000000006f1b10 in ?? () #22 0x00007f2ba06b28b4 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #23 0x00007f2ba1024535 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #24 0x00000000006f1149 in ?? () #25 0x00007f2ba06b28b4 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #26 0x00007f2ba1024535 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #27 0x00000000006f4d29 in ?? () #28 0x00007f2ba06b28b4 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #29 0x00007f2ba1024535 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #30 0x00007f2ba1024789 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #31 0x00007f2ba06b28b4 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #32 0x00007f2ba1024535 in QWidget::~QWidget() () from /usr/lib64/libQtGui.so.4 #33 0x00000000006eed79 in ?? () #34 0x00000000006721f4 in ?? () #35 0x000000000067c955 in ?? () #36 0x00007f2ba06b5a1f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #37 0x00007f2ba0fcad12 in QAction::triggered(bool) () from /usr/lib64/libQtGui.so.4 #38 0x00007f2ba0fcaf0a in QAction::activate(QAction::ActionEvent) () from /usr/lib64/libQtGui.so.4 #39 0x00007f2ba0fcb087 in QAction::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #40 0x00007f2ba1d5980d in KAction::event(QEvent*) () from /usr/lib64/libkdeui.so.5 #41 0x00007f2ba0fd04d4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #42 0x00007f2ba0fd8aca in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #43 0x00007f2ba1bf4c06 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #44 0x00007f2ba06a1e4c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #45 0x00007f2ba1001f00 in ?? () from /usr/lib64/libQtGui.so.4 #46 0x00007f2ba10033f8 in ?? () from /usr/lib64/libQtGui.so.4 #47 0x00007f2ba0fda715 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #48 0x00007f2ba1bf4c06 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #49 0x00007f2ba06a1e4c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #50 0x00007f2ba106deea in ?? () from /usr/lib64/libQtGui.so.4 #51 0x00007f2ba106e36f in ?? () from /usr/lib64/libQtGui.so.4 #52 0x00007f2ba104abd4 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4 #53 0x00007f2ba1071492 in ?? () from /usr/lib64/libQtGui.so.4 #54 0x00007f2b9911fa93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #55 0x00007f2b99120270 in ?? () from /usr/lib64/libglib-2.0.so.0 #56 0x00007f2b99120510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #57 0x00007f2ba06ca67f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #58 0x00007f2ba107114e in ?? () from /usr/lib64/libQtGui.so.4 #59 0x00007f2ba06a1292 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #60 0x00007f2ba06a1495 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #61 0x00007f2ba06a588b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #62 0x0000000000722fd5 in ?? () #63 0x00007f2b9f814b7d in __libc_start_main () from /lib64/libc.so.6 #64 0x000000000047bf89 in _start () digiKam 1.6.0 is out: http://www.digikam.org/drupal/node/550 Please update and check if this entry still valid. Thanks in advance Gilles Caulier I tested with digiKam 1.6.0 (Archlinux packages) and the crash still occurs. I develop on Archlinux, but I've never seen any crash. This crash is driving me crazy, I was never able to reproduce it. Are you using an 64bit architecture? Yes, I'm running on x86_64. The crash depends on the files being renamed. Did you try with the sample pictures I joined to this bug report? Reproducibility is 100% on my system with the sample I provided. Yes, I did, but it doesn't crash here. Maybe it is the architecture...? Gilles, Marcel, don't you have a x64 system and if so, test the attached images? Andi No 64 bits here : Mac OS-X : 362 bits. Mandriva : 32 bits. Win7 : 32 bits. Gilles I downloaded the two JPEGs, selected them, click Rename, select something like [file]# , rename. No crash. 64bit. (In reply to comment #22) > No 64 bits here : > > Mac OS-X : 362 bits. > Wow, that much? :-) I can't reproduce it either on Fedora 14 x86_64. Renaming two files at once and no crash at all. Hello Again, As all of you, I don't like bugs especially the ones that only affect me. Following Marcel Wiesweg comment, I tried renaming the files from my sample using the file naming scheme he used ([file]#) and it worked! This means that this bugs depends on the naming scheme used. Here is the one that causes a systematic crash : "[date:"yyyy-MM-dd_hh-mm-ss"]_Adam". I hope that you will now be able to reproduce the crash. Thank you for your help! When renaming files with date pattern (as comment above or similar), it crashes EVERY time... openSUSE 11.3 64b (In reply to comment #26) > Hello Again, > > As all of you, I don't like bugs especially the ones that only affect me. > Following Marcel Wiesweg comment, I tried renaming the files from my sample > using the file naming scheme he used ([file]#) and it worked! > > This means that this bugs depends on the naming scheme used. Here is the one > that causes a systematic crash : "[date:"yyyy-MM-dd_hh-mm-ss"]_Adam". > > I hope that you will now be able to reproduce the crash. > > Thank you for your help! And again, it doesn't crash here with [date:"yyyy-MM-dd_hh-mm-ss"]_Adam I'm sorry but I can not fix something that doesn't produce errors on my machine. I hope some other developer can create the crash once. Since only Qt functions are used (and no pointers are involved when using the date rename option), I still believe that the installed Qt version is broken (on x64?)... Another problem: All backtraces I get are rather old, I need some fresh report from current SVN, otherwise I can not detect the bug either. The lines in the above backtraces are not in sync with trunk. So please could all of you who can reproduce the crash compile the latest code from subversion? Thanks. Andi I can not repoduce the crash. I am using a 32bits system, KDE 4.4.2 and Digikam 1.6.0 rev1198069. Julien Samuel, does valgrind give you more information before or when the crash happens? For me, no crash and everything is clean in valgrind. I can't crash it either with the exact same string as Samuel provided, Qt 4.7.1 & KDE 4.5.3, all 64bit. So maybe it really is a Qt bug and was resolved in 4.7. Although I tried with the GSoC branch, but this component should be the same, right? Yes, it is the same component (if syncing with trunk didn't fail) *** Bug 252557 has been marked as a duplicate of this bug. *** *** Bug 257099 has been marked as a duplicate of this bug. *** *** Bug 257676 has been marked as a duplicate of this bug. *** *** Bug 257788 has been marked as a duplicate of this bug. *** *** Bug 258045 has been marked as a duplicate of this bug. *** This crash is caused by some QTextDocument that gets created as a child of a widget and gets deleted before the KTextEdit ("ProxyLineEdit") gets deleted. Please check where you are creating a QTextDocument. It is also possible that this is a bug in Sonnet (spell checking), as the document is still referred by the Sonnet syntax highlighter. But after checking bugzilla, I only found duplicates from Digikam. But why is it crashing now? And only on some machines? But I will take a look, thanks for the comment. Andi *** Bug 233987 has been marked as a duplicate of this bug. *** Possibly because the system wide default for spell checking changed from disabled to enabled in KDE. Anyone who can reproduce the crash should try disabling spell checking in system settings. Yep, that's it! Enabling spell-checking crashes digiKam. SVN commit 1201406 by aclemens: Implement createHighlighter() with an empty body, to avoid the creation of a default highlighter object. I would prefer a way where we can disable the SpellChecking completely, but this doesn't seem to be possible. Another solution might be to convert the class to QTextEdit instead. CCBUG:237642 M +6 -1 advancedrenameinput.cpp M +7 -0 advancedrenameinput.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1201406 Try KTextEdit::setCheckSpellingEnabled(false); You can also listen to the checkSpellingChanged signal, in case the user tries to trick you :) SVN commit 1201408 by aclemens: Better yet, use a QTextEdit as the base class, to avoid the hack that has been committed before. Although we break with the layout here (not using K* classes whenever possible), I like this version a lot better. If there is a way to disable spell checking (I have not found one), we should revert to the KTextEdit class again... BUG:237642 M +3 -7 advancedrenameinput.cpp M +2 -9 advancedrenameinput.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1201408 (In reply to comment #45) > Try KTextEdit::setCheckSpellingEnabled(false); > > You can also listen to the checkSpellingChanged signal, in case the user tries > to trick you :) I did this, but it still crashed. So I guess I will keep the QTextEdit as the base class. For "auto spell checking" to work, misspelled words need to be highlighted (the red, curly line). But I guess I'm not able to combine my highlighter with this default one? *** Bug 248882 has been marked as a duplicate of this bug. *** *** Bug 255830 has been marked as a duplicate of this bug. *** I read this thread and in contrary to what I reported in Bug 248882 the problem is still there, in openSUSE 11.4 Milestone 4 with Digikam 1.6.0, when I enable spell checking in System Settings. In case you need more information, please let me know. Yes, this was fixed only recently in svn. This fix will be included in next release in three weeks. *** Bug 264019 has been marked as a duplicate of this bug. *** |