Version: (using KDE KDE 3.5.6) Installed from: Fedora RPMs OS: Linux I am using my Canon EOS Digital, when I get the immage dowloaded I try to save in my albums & it crashes. I have a crash handler log but don't see where to attach it !! thanks in advance Des Cavin.
Des, Can you attach a GDB backtrace to this file (http://www.digikam.org/?q=contrib). Without that, we cannot do anything. Thanks in advance. Gilles Caulier
Des, Can you give us a gdb backtrace please, else we cannot hack anything and we will close this report... Gilles
BTW, which version of digikam are you using?
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffcc" text="#000099"> I am using Ver 0.9.2, KDE 3.5.7-20, Fedora 7................ thanks <br> <br> Arnd Baecker wrote: <blockquote cite="mid:20070831072533.18751.qmail@ktown.kde.org" type="cite"> <pre wrap="">------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. <a class="moz-txt-link-freetext" href="http://bugs.kde.org/show_bug.cgi?id=149364">http://bugs.kde.org/show_bug.cgi?id=149364</a> ------- Additional Comments From arnd.baecker web de 2007-08-31 09:25 ------- BTW, which version of digikam are you using? </pre> </blockquote> </body> </html>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffcc" text="#000099"> Can you please advise GDB is, sorry for my ignorance but in this Linux world you come accross something new everyday... DesC........<br> <br> Gilles Caulier wrote: <blockquote cite="mid:20070830041533.18983.qmail@ktown.kde.org" type="cite"> <pre wrap="">------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. <a class="moz-txt-link-freetext" href="http://bugs.kde.org/show_bug.cgi?id=149364">http://bugs.kde.org/show_bug.cgi?id=149364</a> caulier.gilles gmail com changed: What |Removed |Added ---------------------------------------------------------------------------- Component|general |Camera GUI ------- Additional Comments From caulier.gilles gmail com 2007-08-30 06:15 ------- Des, Can you attach a GDB backtrace to this file (<a class="moz-txt-link-freetext" href="http://www.digikam.org/?q=contrib">http://www.digikam.org/?q=contrib</a>). Without that, we cannot do anything. Thanks in advance. Gilles Caulier </pre> </blockquote> </body> </html>
Thanks for the updated information, 0.9.2 is the latest stable release. Could you please reply in your e-mail without html code (See http://bugs.kde.org/show_bug.cgi?id=149364 why html reply does not look good ;-) If you want to attach the crash handler log you can do this via above link (under "Create Attachment"). What Gilles would like to have is a proper gdb backtrace. For this you will have to compile digikam with debug information. See http://www.digikam.org/?q=contrib under "If you are experiencing crashes with digiKam". The bugtrace is the only way to know where the programm crashes! If you have never compiled anything under linux, this might be a bit of a ride, but we will try to help (either here or maybe better on the digikam-users mailing list).
Arnd, here is an embedded bug report, hope this is what you need..... (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) ditto many times... (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209148544 (LWP 3494)] [New Thread -1221071984 (LWP 3696)] (no debugging symbols found) ditto many times (no debugging symbols found) ditto many times (no debugging symbols found) [KCrash handler] #6 0x03436c37 in Digikam::AlbumManager::albumDB () from /usr/lib/libdigikam.so.0 #7 0x034ba1ae in Digikam::MetadataHub::load () from /usr/lib/libdigikam.so.0 #8 0x036a2b08 in Digikam::ImageWindow::saveAs () from /usr/lib/libdigikam.so.0 #9 0x036a0bfb in Digikam::EditorWindow::qt_invoke () from /usr/lib/libdigikam.so.0 #10 0x036a10d3 in Digikam::ImageWindow::qt_invoke () from /usr/lib/libdigikam.so.0 #11 0x023f3d1a in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #12 0x023f470d in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #13 0x007eb329 in KAction::activated () from /usr/lib/libkdeui.so.4 #14 0x00824a52 in KAction::slotActivated () from /usr/lib/libkdeui.so.4 #15 0x008ecefd in KAction::slotPopupActivated () from /usr/lib/libkdeui.so.4 #16 0x008ed1c1 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4 #17 0x023f3d1a in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #18 0x02781fce in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #19 0x024122e7 in QSignal::activate () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #20 0x02514195 in QPopupMenu::mouseReleaseEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #21 0x007f4baf in KPopupMenu::mouseReleaseEvent () from /usr/lib/libkdeui.so.4 #22 0x024303b5 in QWidget::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #23 0x0238a53b in QApplication::internalNotify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #24 0x0238bd09 in QApplication::notify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #25 0x00c14692 in KApplication::notify () from /usr/lib/libkdecore.so.4 #26 0x02322360 in QETWidget::translateMouseEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #27 0x02320766 in QApplication::x11ProcessEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #28 0x0233238b in QEventLoop::processEvents () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #29 0x023a3e30 in QEventLoop::enterLoop () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #30 0x023a3ce6 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #31 0x0238a17f in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #32 0x0804ab9d in main () Please advise if this is OK, regards DesC........................ Arnd Baecker wrote: [bugs.kde.org quoted mail]
Des, "(no debugging symbols found)" ==> this resume the situation. You need to recompile shared like like Exiv2, libkexiv2, and digiKam with full debug infos and try to reproduce the backtrace. Other question : which version of Exiv2 / libkexiv2 you use ? Gilles
Gillles, Exiv2 = ver 0.14-1.FC7 Libkexiv2 = ver 0.1.5-1.FC7 Digikam = ver 0.9.2-1.FC7 Regards DesC............... Gilles Caulier wrote: [bugs.kde.org quoted mail]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#cccccc" text="#000066"> Des Cavin wrote: <blockquote cite="mid:20070902230023.4757.qmail@ktown.kde.org" type="cite"> <pre wrap="">------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. <a class="moz-txt-link-freetext" href="http://bugs.kde.org/show_bug.cgi?id=149364">http://bugs.kde.org/show_bug.cgi?id=149364</a> ------- Additional Comments From des.cavin sympatico ca 2007-09-03 01:00 ------- Gillles, Exiv2 = ver 0.14-1.FC7 Libkexiv2 = ver 0.1.5-1.FC7 Digikam = ver 0.9.2-1.FC7 Regards DesC............... Gilles Caulier wrote: [bugs.kde.org quoted mail] </pre> </blockquote> Gilles,<br> thanks for all your assistance but I have since removed Fedora and installed PCLOS, once again thanks and regards, DesCavin.....................<br> <br> </body> </html>
Could you please reply in your e-mail without html code (See http://bugs.kde.org/show_bug.cgi?id=149364 why html reply makes it nearly impossible to find the contents of your message! Does your last e-mail mean that you do not observe the problem anymore? If you still observe the problem, a proper backtrace is needed to find the source of the problem. This means that you will have to recompile digikam, libkexiv, exiv2, ... and so with debugging enabled. See http://www.digikam.org/?q=contrib under "If you are experiencing crashes with digiKam" and for installation instructions "http://www.digikam.org/?q=download/svn" under "Install digiKam in your Home Directory". Arnd
Closing this bug, because without additional information nothing can be done. If you still experience a crash, please provide a proper backtrace and re-open this bug. Thanks a lot for your understanding, Arnd Baecker