[Digikam-users] digiKam-0.8.1 crashes when advanced search is selected from the tools menu

[Gilles Caulier]

On Tuesday 20 June 2006 04:38, Graeme Nichols wrote:
> Gilles Caulier wrote:
> > On Monday 19 June 2006 07:14, Graeme Nichols wrote:
> >>Caulier Gilles wrote:
> >>>Le Dimanche 18 Juin 2006 07:47, Graeme Nichols a écrit :
> >>>>Hello Folks,
> >>>>
> >>>>I am a new digiKam user and very impressed. Unfortunately I get the
> >>>>above when I select the advanced search.
> >>>>
> >>>>The bug is shown as resolved on bugs.kde.org but,
> >>>
> >>>what is the file in B.K.O relevant ?
> >>>
> >>>Gilles
> >>
> >>I'm not sure what you mean. The bug is:
> >>
> >>Bug 120922 - Clicking on Advanced search crashes application.
> >>
> >>It is shown as 'RESOLVED' but apparently it hasn't been resolved because
> >>there was no backtrace information when the bug was first reported. From
> >>what I can gather the bug would be re-opened if the original reporter
> >>could re-compile and get a proper backtrace. I don't get any backtrace
> >>information either and I installed from Fedora Extras RPM.
> >>
> >>My question is; Has the bug indeed been resolved and what was the
> >>resolution?
> >
> > Nothing have be done into implementation. Please I think there is another
> > file in B.K.O about advanced search crash. Please take a look if it's the
> > same. If no, re-open the file and give me full (and suitable) backtrace
> > with gdb and valgrind. Thanks in advance
> >
> > Gilles
>
> Hello Gilles,
>
> I could only find the one hit using the search 'advanced search crash'.
> Sorry.
>
> Now, you are taking me into areas where I have absolutely no skills or
> knowledge but if you are prepared to guide me I will attempt to do what
> you require.
>
> Valgrind is not installed on my system but gdb is.
>
> Running gdb digikam as me gives the following results:
>
> [graeme at barney ~]$ man gdb
> [graeme at barney ~]$ gdb digikam
> GNU gdb Red Hat Linux (6.3.0.0-1.21rh)
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-redhat-linux-gnu"...
> (no debugging symbols found)
> Using host libthread_db library "/lib/libthread_db.so.1".
>
> (gdb) quit
>
> su to root and run the same command gives the same results.
>
> The backtrace when digikam crashes is as follows:
>
> (no debugging symbols found)
> Using host libthread_db library "/lib/libthread_db.so.1".
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> [New Thread -1209043264 (LWP 3858)]
> [KCrash handler]
> #4  0x02bf43a4 in QScrollView::viewport ()
>     from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #5  0x03ab42da in SqueezedComboBox::SqueezedComboBox ()
>     from /usr/lib/libdigikam.so.0
> #6  0x03aa3a5b in SearchAdvancedRule::setValueWidget ()
>     from /usr/lib/libdigikam.so.0
> #7  0x03aa3d1b in SearchAdvancedRule::slotKeyChanged ()
>     from /usr/lib/libdigikam.so.0
> #8  0x03aa5006 in SearchAdvancedRule::SearchAdvancedRule ()
>     from /usr/lib/libdigikam.so.0
> #9  0x03a9da92 in SearchAdvancedDialog::slotAddRule ()
>     from /usr/lib/libdigikam.so.0
> #10 0x03aa0453 in SearchAdvancedDialog::SearchAdvancedDialog ()
>     from /usr/lib/libdigikam.so.0
> #11 0x03a9617d in SearchFolderView::extendedSearchNew ()
>     from /usr/lib/libdigikam.so.0
> #12 0x03a460e2 in DigikamView::slotNewAdvancedSearch ()
>     from /usr/lib/libdigikam.so.0
> #13 0x03a48afe in DigikamView::qt_invoke () from /usr/lib/libdigikam.so.0
> #14 0x02ad1db4 in QObject::activate_signal ()
>     from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #15 0x02ad2274 in QObject::activate_signal ()
>     from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #16 0x0342694f in KAction::activated () from /usr/lib/libkdeui.so.4
> #17 0x03426a74 in KAction::slotActivated () from /usr/lib/libkdeui.so.4
> #18 0x03429010 in KAction::slotPopupActivated () from
> /usr/lib/libkdeui.so.4 #19 0x0342929a in KAction::qt_invoke () from
> /usr/lib/libkdeui.so.4 #20 0x02ad1db4 in QObject::activate_signal ()
>     from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #21 0x02e46796 in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #22 0x02aef633 in QSignal::activate () from
> /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #23 0x02be6582 in QPopupMenu::mouseReleaseEvent ()
>     from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #24 0x03416a80 in KPopupMenu::mouseReleaseEvent () from
> /usr/lib/libkdeui.so.4
> #25 0x02b10127 in QWidget::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #26 0x02a6d08d in QApplication::internalNotify ()
>     from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #27 0x02a6dfef in QApplication::notify ()
>     from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #28 0x00aa6661 in KApplication::notify () from /usr/lib/libkdecore.so.4
> #29 0x02a04b0d in QETWidget::translateMouseEvent ()
>     from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #30 0x02a02eb3 in QApplication::x11ProcessEvent ()
>     from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #31 0x02a16fc8 in QEventLoop::processEvents ()
>     from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #32 0x02a8574b in QEventLoop::enterLoop ()
>     from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #33 0x02a85656 in QEventLoop::exec () from
> /usr/lib/qt-3.3/lib/libqt-mt.so.3 #34 0x02a6ca59 in QApplication::exec ()
> from
> /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #35 0x0804a495 in main ()
>
>
> There are no debugging symbols found in both cases.
>
> How can I overcome this for you or is the above of any use?

You need to recompile digiKam runing "./configure --enable-debug=full".

Gilles