Bug 160523 - Crash when saving picture as new nameafter resizing
Summary: Crash when saving picture as new nameafter resizing
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-07 20:06 UTC by John Carrick Smith
Modified: 2017-08-08 10:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 0.9.4
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Carrick Smith 2008-04-07 20:06:55 UTC
Version:           0.9.2 final (using Devel)
Installed from:    Compiled sources
OS:                Linux

Had trouble getting DigiKam to recognise the camera (Canon A720) but repeated attempts resulted in eventual success. Reduced the pixel dimensions prior to saving before e-mailing and when saving the edited picture as a new name the following crash occurred. I had to download the picture and edit with Gimp to get a result.

This is the crash diagnostic:-

System configuration startup check disabled.

 [?1034h(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)
[Thread debugging using libthread_db enabled]
[New Thread 0xb68c66d0 (LWP 7366)]
(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)
(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  0xb75dc2e9 in QGDict::hashKeyString () from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0xb75dd329 in QGDict::look_string () from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0xb7d15a22 in KMJobManager::removePrinter ()
   from /opt/kde3/lib/libkdeprint.so.4
#9  0xb7e19d5a in KMJobViewer::removeFromManager ()
   from /opt/kde3/lib/libkdeprint_management.so.4
#10 0xb7e1bd4c in KMJobViewer::~KMJobViewer ()
   from /opt/kde3/lib/libkdeprint_management.so.4
#11 0xb7f9a56e in QDict<KMJobViewer>::deleteItem ()
   from /opt/kde3/lib/libkdeinit_kjobviewer.so
#12 0xb75dd2b9 in QGDict::remove_string () from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0xb7f99734 in KJobViewerApp::slotJobsShown ()
   from /opt/kde3/lib/libkdeinit_kjobviewer.so
#14 0xb7f99840 in KJobViewerApp::qt_invoke ()
   from /opt/kde3/lib/libkdeinit_kjobviewer.so
#15 0xb732d90d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb7dec077 in KMJobViewer::jobsShown ()
   from /opt/kde3/lib/libkdeprint_management.so.4
#17 0xb7e35cc2 in KMJobViewer::refresh ()
   from /opt/kde3/lib/libkdeprint_management.so.4
#18 0xb7f9930d in KJobViewerApp::slotTimer ()
   from /opt/kde3/lib/libkdeinit_kjobviewer.so
#19 0xb7f9981b in KJobViewerApp::qt_invoke ()
   from /opt/kde3/lib/libkdeinit_kjobviewer.so
#20 0xb732d871 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0xb732e4ad in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb7663929 in QTimer::timeout () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb735096f in QTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb72cf10c in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb72cfef6 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb7978ee2 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#27 0xb72c43e4 in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb727e403 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0xb72e5c90 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0xb72e5b26 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0xb72cec7f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0xb7f9a3fc in kdemain () from /opt/kde3/lib/libkdeinit_kjobviewer.so
#33 0x08048502 in ?? ()
#34 0x00000002 in ?? ()
#35 0xbfcfae44 in ?? ()
#36 0xbfcfadb8 in ?? ()
#37 0x08048539 in ?? ()
#38 0xb7fc0f60 in ?? () from /lib/ld-linux.so.2
#39 0xbfcfadc0 in ?? ()
#40 0xbfcfae18 in ?? ()
#41 0xb7e75fe0 in __libc_start_main () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC
Comment 1 caulier.gilles 2008-04-07 20:21:35 UTC
John,

The backtrace mean... nothing. This is a non-sense. It's ound like a broken package installed or a broken dependency.

Please, try to update to last stable 0.9.3, and try again.

Gilles Caulier

Comment 2 John Carrick Smith 2008-04-13 16:46:31 UTC
Hello Gilles,

Thank you for your prompt response. It has taken me time to do what you asked as I have had to install all the dependencies, starting with gcc! As you can tell I am relatively new to Linux.

I installed the following packages and dependencies using Yast2 on my openSuse 10.3 installation:
gcc/gcc++ 4.2.1
xorg-devel
qt-devel
kde-devel

I have run 
./configure --prefix=/opt/kde3/bin
make
sudo make install

No errors were apparent but I cannot find the executable code? It isn't where I expect to find it. (I had renamed the existing digikam version first.)  Please can you help?

Thank you in advance. John
Comment 3 Arnd Baecker 2008-04-24 11:35:31 UTC
Hi John,
when you specify --prefix=/opt/kde3/bin
all the stuff will be installed below that directory.
I.e. this should contain /opt/kde3/bin/bin /opt/kde3/bin/lib etc.

I would recommend to follow http://www.digikam.org/?q=download/svn
under "Install digiKam for KDE3 in your Home Directory"

Otherwise, there are debug packages for ubuntu gutsy
http://www.mpe.mpg.de/~ach/kubuntu/gutsy/

Good luck, Arnd
Comment 4 caulier.gilles 2008-05-19 18:01:37 UTC
John, what new about this entry ? any progress following comment #3 ?

Gilles Caulier
Comment 5 John Carrick Smith 2008-05-19 20:02:03 UTC
Hello Gilles, Sorry for the delay. I have had to re-build my Linux machine following a catastrophic failure (Couldn't get into grub on boot!). I have today managed to test Digikam again and the problem can no longer be reproduced! So the rebuild has solved the problem. Thank-you for your attention to this report and apologise for taking up your time unnecessarily. Please close the report. Best wishes. John
Comment 6 John Carrick Smith 2008-05-19 20:03:49 UTC
Closing it myself. I didn't see the option last time. John