Bug 155023

Your backtrace is not suitable. There is no debug info available. You need to recompile kipi-plugins using full debug info...

Gilles Caulier

Thanks for  your help.
After recompiling kipi-plugins using full debug info I got this:
System configuration startup check disabled.

(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)
[Thread debugging using libthread_db enabled]
[New Thread -1246103856 (LWP 4624)]
[New Thread -1256977520 (LWP 4639)]
0xb68aebc9 in sqlite3_value_text () from /usr/lib/libsqlite3.so.0
#0  0xb68aebc9 in sqlite3_value_text () from /usr/lib/libsqlite3.so.0
#1  0xb68aebff in sqlite3_column_text () from /usr/lib/libsqlite3.so.0
#2  0xb7c2ca9c in Digikam::AlbumDB::execSql ()
   from /opt/kde3/lib/libdigikam.so.0
#3  0xb7c3230c in Digikam::AlbumDB::getItemCaption ()
   from /opt/kde3/lib/libdigikam.so.0
#4  0xb7c90d16 in Digikam::ImageInfo::caption ()
   from /opt/kde3/lib/libdigikam.so.0
#5  0xb7c3b441 in Digikam::AlbumIconItem::paintItem ()
   from /opt/kde3/lib/libdigikam.so.0
#6  0xb7c8a928 in Digikam::IconView::viewportPaintEvent ()
   from /opt/kde3/lib/libdigikam.so.0
#7  0xb6ef415f in QScrollView::eventFilter ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0xb6ddeccc in QObject::activate_filters ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0xb6dded3b in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb6e17e3c in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0xb6d80647 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0xb6d814f9 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0xb74091f2 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#14 0xb6d152e9 in QETWidget::translatePaintEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0xb6d1f3fc in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb6d2f91a in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb6d970e0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb6d96f76 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb6d8000f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x0804ac6a in main ()

-----Urspr

hmm are you sure, you've compiled kipi-plugins and used the ones compiled? If so this is a digikam problem, all i can see in this bt is about digikam:
[...]
0xb68aebc9 in sqlite3_value_text () from /usr/lib/libsqlite3.so.0 
 #0  0xb68aebc9 in sqlite3_value_text () from /usr/lib/libsqlite3.so.0 
 #1  0xb68aebff in sqlite3_column_text () from /usr/lib/libsqlite3.so.0 
 #2  0xb7c2ca9c in Digikam::AlbumDB::execSql () 
    from /opt/kde3/lib/libdigikam.so.0 
 #3  0xb7c3230c in Digikam::AlbumDB::getItemCaption () 
    from /opt/kde3/lib/libdigikam.so.0 
 #4  0xb7c90d16 in Digikam::ImageInfo::caption () 
    from /opt/kde3/lib/libdigikam.so.0 
 #5  0xb7c3b441 in Digikam::AlbumIconItem::paintItem () 
    from /opt/kde3/lib/libdigikam.so.0 
 #6  0xb7c8a928 in Digikam::IconView::viewportPaintEvent () 
    from /opt/kde3/lib/libdigikam.so.0
[...]

let#s say, i am not sure about the meaning of "compile" (I am a user and I have no idea about soft or hardware). Digikam says that I have all kipi-plugins and it seems that everything runs smooth, apart of my problem. 
-----Urspr

Ok try to find the debug or debuginfo package provided by Suse
for instance digikam-debuginfo--0.9.2-1.rpm  or similar
and the one for kipi-plugins and after installing retry.

Angelo

I have now installed digikam and its debuginfo 0.9.3, as well as the kipi plugins and its debuginfo 0.1.4
I t still doesn't work and I got the following as Backtrace, everything worked well until the upgrade to 0.9.3:

System configuration startup check disabled.

(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)
[Thread debugging using libthread_db enabled]
[New Thread -1245944112 (LWP 4954)]
[New Thread -1256817776 (LWP 4969)]
0xb7f6f410 in ?? ()
#0  0xb7f6f410 in ?? ()
#1  0xbfdeeb58 in ?? ()
#2  0x080966dc in ?? ()
#3  0x08096558 in ?? ()
#4  0xb69a3a41 in ___newselect_nocancel () from /lib/libc.so.6
#5  0xb6d566e6 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#6  0xb6dbe0e0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0xb6dbdf76 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0xb6da700f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0x0804ac6a in main ()

-----Urspr

Thanks for your patience, but unfortunately again the bt is not suitable :/

Let's try to reproduce it here so...
Please provide the following output commands:
1) rpm -qa | grep kipi
2) rpm -qa | grep exiv2
3) rpm -qa | grep dcraw
4) rpm -qa | grep digikam

then please provide which mail client are you using for the failing test.
TIA,
	Angelo
P.S. are you able to compile (i mean developer stuff) from source? in the case we can follow you
to build all and try to understand what happens...

Thanks for YOUR patience, but I think I can not compile from source.

But here I have done what you were asking for:

user@linux-0ad8:~> rpm -qa | grep kipi
libkipi-debuginfo-0.1.5-100.pm.2
libkipi-0.1.5-100.pm.2
kipi-plugins-0.1.4-100.pm.2
libkipi-devel-0.1.5-100.pm.2
kipi-plugins-debuginfo-0.1.4-100.pm.2

user@linux-0ad8:~> rpm -qa | grep exiv2
libexiv2-0.12-101.pm.1
libkexiv2-0.1.6-0.pm.1

user@linux-0ad8:~> rpm -qa | grep dcraw
libkdcraw2-0.1.2-0.pm.0
libkdcraw0-0.1.1-0.pm.0
dcraw-1.353-12

user@linux-0ad8:~> rpm -qa | grep digikam
digikam-0.9.3-0.pm.2
digikamimageplugins-superimpose-0.9.3-0.pm.2
digikam-debuginfo-0.9.3-0.pm.2
digikamimageplugins-0.9.3-0.pm.2
user@linux-0ad8:~>

I am using kmail as mailclient

Thanks for your help

Jens


-----Urspr

After reading this, I have exactly the same problem (#158585) with the same package installed. I got the first error messages also, but after installing the  debuginfo-package, I got no usefull information  any longer.  

marin@noname:~> rpm -qa | grep kipi
libkipi-0.1.5-100.pm.2
kipi-plugins-0.1.4-100.pm.2
marin@noname:~> rpm -qa | grep exiv2
libexiv2-0.12-101.pm.1
libexiv2-devel-0.12-101.pm.1
libkexiv2-devel-0.1.6-0.pm.1
libkexiv2-0.1.6-0.pm.1
marin@noname:~> rpm -qa | grep dcraw
dcraw-1.353-12
libkdcraw0-0.1.1-0.pm.0
libkdcraw2-0.1.2-0.pm.0
marin@noname:~> rpm -qa | grep digikam
digikam-0.9.3-0.pm.2
digikam-debuginfo-0.9.3-0.pm.2
libdigikam-devel-0.9.3-0.pm.2
digikamimageplugins-0.9.3-0.pm.2
digikamimageplugins-superimpose-0.9.3-0.pm.2
marin@noname:~>

*** Bug 158585 has been marked as a duplicate of this bug. ***

As there seems to be no solution to this problem, I went back to Digikam 0.8.2.
at least, this one works. 
Marin 

Marin, there can't be any solution to this problem until
there is a proper backtrace showing the source of the crash.
It seems, that none of the developers was able to reproduce the bug, 
so here your help is needed, see 
   http://www.digikam.org/drupal/contrib
under "If you are experiencing crashes with digiKam"

Best, Arnd

Jens,

This file still valid using digiKam 0.9.4 and kipi-plugins 0.1.6 ?

Gilles Caulier

Cannot confirm for 0.9.5.svn and kipi-plugins from svn.

Thanks. I close this file now.

Gilles Caulier