digiKam › digikam-users

digiKam-0.8.1 crashes when advanced search is selected from the tools menu

Classic

List

Threaded

12 messages Options

Graeme Nichols

digiKam-0.8.1 crashes when advanced search is selected from the tools menu

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, probably due to my
ignorance, I cannot find what the resolution was. Maybe it was to
upgrade to the next release, 0.8.2, or maybe something else.

My system is FC4, KDE 3.4.0-6 Red Hat. The digiKam, KIPI-Plugins and
digiKamimage-plugins were all from the FC4 Extras repository as were
some needed dependencies.

If someone can let me know what the resolution was I would appreciate
it; or point me in the right direction to find the resolution.

Thank you.

--

----------------------------------------------------------------------
Kind regards,

Graeme.
----------------------------------------------------------------------
Download my GnuPG public key from:-
http://www.users.tpg.com.au/gnichols/graemenichols.pub
----------------------------------------------------------------------

You can't get there from here.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Gilles Caulier-2

Re: digiKam-0.8.1 crashes when advanced search is selected from the tools menu

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

> probably due to my
> ignorance, I cannot find what the resolution was. Maybe it was to
> upgrade to the next release, 0.8.2, or maybe something else.
>
> My system is FC4, KDE 3.4.0-6 Red Hat. The digiKam, KIPI-Plugins and
> digiKamimage-plugins were all from the FC4 Extras repository as were
> some needed dependencies.
>
> If someone can let me know what the resolution was I would appreciate
> it; or point me in the right direction to find the resolution.
>
> Thank you.

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Graeme Nichols

Re: digiKam-0.8.1 crashes when advanced search is selected from the tools menu

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?

Thanks.

Graeme.

>
>
>>probably due to my
>>ignorance, I cannot find what the resolution was. Maybe it was to
>>upgrade to the next release, 0.8.2, or maybe something else.
>>
>>My system is FC4, KDE 3.4.0-6 Red Hat. The digiKam, KIPI-Plugins and
>>digiKamimage-plugins were all from the FC4 Extras repository as were
>>some needed dependencies.
>>
>>If someone can let me know what the resolution was I would appreciate
>>it; or point me in the right direction to find the resolution.
>>
>>Thank you.
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
> .
>

--

----------------------------------------------------------------------
Kind regards,

Graeme.
----------------------------------------------------------------------
Download my GnuPG public key from:-
http://www.users.tpg.com.au/gnichols/graemenichols.pub
----------------------------------------------------------------------

The truth you speak has no past and no future. It is, and that's all it
needs to be.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Gilles Caulier-2

Re: digiKam-0.8.1 crashes when advanced search is selected from the tools menu

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

>
> Thanks.
>
> Graeme.
>
> >>probably due to my
> >>ignorance, I cannot find what the resolution was. Maybe it was to
> >>upgrade to the next release, 0.8.2, or maybe something else.
> >>
> >>My system is FC4, KDE 3.4.0-6 Red Hat. The digiKam, KIPI-Plugins and
> >>digiKamimage-plugins were all from the FC4 Extras repository as were
> >>some needed dependencies.
> >>
> >>If someone can let me know what the resolution was I would appreciate
> >>it; or point me in the right direction to find the resolution.
> >>
> >>Thank you.
> >
> > _______________________________________________
> > Digikam-users mailing list
> > [hidden email]
> > https://mail.kde.org/mailman/listinfo/digikam-users
> >
> > .

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Graeme Nichols

Re: digiKam-0.8.1 crashes when advanced search is selected from the tools menu

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@barney ~]$ man gdb
[graeme@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?

>
>
>>Thanks.
>>
>>Graeme.
>>
>>
>>>>probably due to my
>>>>ignorance, I cannot find what the resolution was. Maybe it was to
>>>>upgrade to the next release, 0.8.2, or maybe something else.
>>>>
>>>>My system is FC4, KDE 3.4.0-6 Red Hat. The digiKam, KIPI-Plugins and
>>>>digiKamimage-plugins were all from the FC4 Extras repository as were
>>>>some needed dependencies.
>>>>
>>>>If someone can let me know what the resolution was I would appreciate
>>>>it; or point me in the right direction to find the resolution.
>>>>
>>>>Thank you.
>>>
>>>_______________________________________________
>>>Digikam-users mailing list
>>>[hidden email]
>>>https://mail.kde.org/mailman/listinfo/digikam-users
>>>
>>>.
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users
>
> .
>

--

----------------------------------------------------------------------
Kind regards,

Graeme.
----------------------------------------------------------------------
Download my GnuPG public key from:-
http://www.users.tpg.com.au/gnichols/graemenichols.pub
----------------------------------------------------------------------

Suffering alone exists, none who suffer;
The deed there is, but no doer thereof;
Nirvana is, but no one is seeking it;
The Path there is, but none who travel it.
-- "Buddhist Symbolism", Symbols and Values
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Gilles Caulier-2

Re: digiKam-0.8.1 crashes when advanced search is selected from the tools menu

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@barney ~]$ man gdb
> [graeme@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
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Graeme Nichols

Re: digiKam-0.8.1 crashes when advanced search is selected from the tools menu

Gilles Caulier wrote:

> 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@barney ~]$ man gdb
>>[graeme@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

OK Gilles, not a problem. I have to go away for a couple of weeks so
will do it when I return and send you the output.

Thank you for all your help.

--

----------------------------------------------------------------------
Kind regards,

Graeme.
----------------------------------------------------------------------
Download my GnuPG public key from:-
http://www.users.tpg.com.au/gnichols/graemenichols.pub
----------------------------------------------------------------------

Don't go to bed with no price on your head.
-- Baretta
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Gilles Caulier-2

Re: digiKam-0.8.1 crashes when advanced search is selected from the tools menu

On Wednesday 21 June 2006 03:32, Graeme Nichols wrote:

> Gilles Caulier wrote:
> > 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@barney ~]$ man gdb
> >>[graeme@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
>
> OK Gilles, not a problem. I have to go away for a couple of weeks so
> will do it when I return and send you the output.
>
> Thank you for all your help.

I recommend you to re-open the file in B.K.O and put all report in this way.
It's better than ML to store informations for a long time

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Graeme Nichols

Re: digiKam-0.8.1 crashes when advanced search is selected from the tools menu

Gilles Caulier wrote:

> On Wednesday 21 June 2006 03:32, Graeme Nichols wrote:
>
>>Gilles Caulier wrote:
>>
>>>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@barney ~]$ man gdb
>>>>[graeme@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
>>
>>OK Gilles, not a problem. I have to go away for a couple of weeks so
>>will do it when I return and send you the output.
>>
>>Thank you for all your help.
>
>
> I recommend you to re-open the file in B.K.O and put all report in this way.
> It's better than ML to store informations for a long time
>
> Gilles

OK. Will do.

--

----------------------------------------------------------------------
Kind regards,

Graeme.
----------------------------------------------------------------------
Download my GnuPG public key from:-
http://www.users.tpg.com.au/gnichols/graemenichols.pub
----------------------------------------------------------------------

[Wisdom] is a tree of life to those laying
hold of her, making happy each one holding her fast.
-- Proverbs 3:18, NSV
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Rex Dieter

Re: digiKam-0.8.1 crashes when advanced search is selected from the tools menu

In reply to this post by Graeme Nichols

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.

You would get more usable backtrace if you:
$ yum install digikam-debuginfo

-- Rex

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Graeme Nichols

Re: digiKam-0.8.1 crashes when advanced search is selected from the tools menu

Rex Dieter wrote:

> 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.
>
>
> You would get more usable backtrace if you:
> $ yum install digikam-debuginfo
>
> -- Rex

Thank you Rex. Will do.

--

----------------------------------------------------------------------
Kind regards,

Graeme.
----------------------------------------------------------------------
Download my GnuPG public key from:-
http://www.users.tpg.com.au/gnichols/graemenichols.pub
----------------------------------------------------------------------

"The chain which can be yanked is not the eternal chain."
-- G. Fitch
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Graeme Nichols

Re: digiKam-0.8.1 crashes when advanced search is selected from the tools menu

In reply to this post by Rex Dieter

Rex Dieter wrote:

OK Rex, I have done that but nothing seems to have changed in the
backtrace which is below. Any ideas?

(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 -1209010496 (LWP 3630)]
[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 ()

Maybe I am not using it correctly. Is there a command line way of using
digikam-debuginfo or does one simply start digikam and it links into
digikam-debuginfo automatically? Could you give me instructions on how
to correctly use digikam-debuginfo please?

--

----------------------------------------------------------------------
Kind regards,

Graeme.
----------------------------------------------------------------------
Download my GnuPG public key from:-
http://www.users.tpg.com.au/gnichols/graemenichols.pub
----------------------------------------------------------------------

Reality is just a crutch for people who can't handle science fiction.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users