Bug 190612 - showfoto crash
Summary: showfoto crash
Status: CLOSED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: Showfoto-Core (show other bugs)
Version: 0.9.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-25 12:46 UTC by Wolfhard Langer
Modified: 2017-07-11 04:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 1.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfhard Langer 2009-04-25 12:46:50 UTC
Version:            (using KDE 3.5.10)
OS:                Linux
Installed from:    SuSE RPMs

Hello,

 the applications "digikam" and "showfoto" are crashing since a few days ago I performed the regular software update for the software repositories with "zypper". 

There is no problem to open "digikam" and "showfoto". In "digikam" it is possible to open a video with kaffeine or to use the DIA-mode for the pictures in a folder. But as soon as "digikam" tries to show the picture information ("meta data") when the cursor is over the picture icon in the picture window and changes from the "arrow" symbol to the the "hand" - symbol, digikam will crash. Only if I click as soon as possible on the picture icon, then the picture is shown in "digikam" but cannot be modified. The crash report show the following messages:

Überprüfung der Systemkonfiguration beim Start deaktiviert.

[?1034h(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 0xb66416d0 (LWP 5255)]
[New Thread 0xb6117b90 (LWP 5257)]
(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)
(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)
(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)
[KCrash handler]
#6  0xbc09e8f4 in ?? ()
#7  0xb18187a9 in KJpegPlugin::readInfo ()
   from /opt/kde3/lib/kde3/kfile_jpeg.so
#8  0xb7cbde9a in KFileMetaInfo::init () from /opt/kde3/lib/libkio.so.4
#9  0xb7cbdf82 in KFileMetaInfo::KFileMetaInfo ()
   from /opt/kde3/lib/libkio.so.4
#10 0xb7cbe04f in KFileItem::metaInfo () from /opt/kde3/lib/libkio.so.4
#11 0x080a647a in ?? ()
#12 0x08094a83 in ?? ()
#13 0x08094c15 in ?? ()
#14 0x0807c6bf in ?? ()
#15 0x0807f9cb in ?? ()
#16 0xb707f98a in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb7081ecb in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x0813f0bc in ?? ()
#19 0x0813f711 in ?? ()
#20 0x08142cb0 in ?? ()
#21 0xb707f98a in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb7081ecb in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x0813366c in ?? ()
#24 0x081336a5 in ?? ()
#25 0x08135152 in ?? ()
#26 0x08137869 in ?? ()
#27 0xb707f98a in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0x080daf61 in ?? ()
#29 0x080dc87e in ?? ()
#30 0x080da94b in ?? ()
#31 0xb707fae6 in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0xb701a5bd in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0xb701b5f6 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0xb76fe882 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#35 0xb701c6da in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0xb701c836 in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#37 0xb6fc4cc5 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#38 0xb7032f00 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#39 0xb7032d96 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#40 0xb701ac4f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#41 0x08079819 in ?? ()
#42 0xb6a0b5f5 in __libc_start_main () from /lib/libc.so.6
#43 0x08078b11 in ?? ()

And here are some installation information for "digikam" on my laptop:

Information for package digikam:

Repository: Update-11.0
Name: digikam
Version: 0.9.3-70.2
Arch: i586
Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany
Installed: Yes
Status: up-to-date

Betriebssystem:  Linux 2.6.25.20-0.1-default i686
  System:  openSUSE 11.0 (i586)
  KDE:  3.5.10 "release 46" 

Can you please give me a hint to solve this problem?

Thank you in advance for your support and for your help.

Kind regards

Wolfhard Langer
Comment 1 caulier.gilles 2009-04-25 12:57:29 UTC
You use a very old release 0.9.3 !!! It's not maintained.

Last stable for KDE3 is 0.9.5... Please use right version.

Also your backtrace is unsuitable. Debug messages are missing.

Andi, your viewpoint. For me the file is not Valid

Gilles Caulier
Comment 2 Andi Clemens 2009-04-25 13:09:21 UTC
I'd say that digiKam 0.9.3 is linked against some lib that has been updated now, but digiKam is not able to use it correctly.
It seems to work as long as no image is opened, but if an image is loaded, it crashes.
So this is definitely no digikam problem but a distribution issue, so marking this as DOWNSTREAM or closing it as INVALID is ok. You / the distribution either needs to recompile or you need to upgrade digiKam to a higher version. I'm pretty sure openSUSE has newer versions than 0.9.3
Comment 3 Wolfhard Langer 2009-04-25 13:52:19 UTC
Hello,

 thank you very much for your hints and for your immediate answer. I will look for a higher version of digiKam that will work together with the updated library of distribution openSUSE.

Have a nice day.

Wolfhard Langer