Summary: | Crash when saving picture as new nameafter resizing | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | John Carrick Smith <jcarricksmith> |
Component: | Portability-Runtime | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 0.9.4 | |
Sentry Crash Report: |
Description
John Carrick Smith
2008-04-07 20:06:55 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 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 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 John, what new about this entry ? any progress following comment #3 ? Gilles Caulier 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 Closing it myself. I didn't see the option last time. John |