Bug 156418 - Crash when rotating or geolocalizing image
Summary: Crash when rotating or geolocalizing image
Status: CLOSED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Orientation (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-22 22:55 UTC by Ron Lusk
Modified: 2021-05-05 01:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.3.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ron Lusk 2008-01-22 22:55:30 UTC
Version:           0.9.3 (using KDE 3.5.5)
Installed from:    SuSE RPMs
OS:                Linux

I start digiKam, select a photo, press Ctrl-Shift-Right to rotate it to the right, and look at the "Rotating images right" dialog.  Almost immediately after this, digiKam disappears with a crash.

In the shell, I get
  Found dcraw version: 8.77
  KCrash: Application 'digikam' crashing...

Now, originally I got this crash by attempting to geolocalize some photos using a GPX file derived from a Phototrackr Lite via a couple of Perl scripts, but I find that manually editing the location (using the map) crashes digiKam when I click the "Apply" button, just as it did when using a GPX file.  After this happened, I tried to find the minimum change that would crash it, and found rotating an image failed, too.

I have a few backtraces available (I installed the digiKam-debuginfo package to enhance the backtrace).  

System configuration startup check disabled.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1246005552 (LWP 7513)]
[New Thread -1348662384 (LWP 7539)]
[New Thread -1311089776 (LWP 7535)]
[New Thread -1302697072 (LWP 7534)]
[New Thread -1294304368 (LWP 7533)]
[New Thread -1248982128 (LWP 7532)]
[New Thread -1257374832 (LWP 7531)]
0xb7f6e410 in ?? ()
#0  0xb7f6e410 in ?? ()
#1  0xbff8c8b8 in ?? ()
#2  0x0808b204 in ?? ()
#3  0x0808b080 in ?? ()
#4  0xb6997a41 in ___newselect_nocancel () from /lib/libc.so.6
#5  0xb6d566e6 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#6  0xb6dbe0c0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0xb6dbdf56 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0xb6da6fef in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0x0804ac6a in main (argc=7, argv=0xbff8cbd4) at main.cpp:332


and, if it makes a difference, a second one from geolocalizing a single image:

System configuration startup check disabled.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1246239024 (LWP 7828)]
[New Thread -1320989808 (LWP 7859)]
[New Thread -1287418992 (LWP 7857)]
[New Thread -1249215600 (LWP 7848)]
[New Thread -1257608304 (LWP 7847)]
[KCrash handler]
#9  0xb709fb00 in QString::operator= () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb707d55a in QFileInfo::QFileInfo () from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0xb7ace2d9 in KExiv2Iface::KExiv2::load ()
   from /opt/kde3/lib/libkexiv2.so.3
#12 0xb4501e48 in KExiv2Iface::KExiv2::setGPSInfo ()
   from /opt/kde3/lib/libkexiv2.so.1
#13 0xb43ea5c9 in KIPIGPSSyncPlugin::GPSListViewItem::writeGPSInfoToFile ()
   from /opt/kde3/lib/kde3/kipiplugin_gpssync.so
#14 0xb43e3563 in KIPIGPSSyncPlugin::GPSSyncDialog::slotApply ()
   from /opt/kde3/lib/kde3/kipiplugin_gpssync.so
#15 0xb768cff3 in KDialogBase::qt_invoke () from /opt/kde3/lib/libkdeui.so.4
#16 0xb43e4bf3 in KIPIGPSSyncPlugin::GPSSyncDialog::qt_invoke ()
   from /opt/kde3/lib/kde3/kipiplugin_gpssync.so
#17 0xb6dcd311 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb6dcdfed in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb710e43c in QButton::clicked () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0xb6e60f6d in QButton::mouseReleaseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0xb6e06190 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb6d6e627 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb6d6f621 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb73f7a42 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#25 0xb6d0e0f7 in QETWidget::translateMouseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb6d0d01f in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0xb6d1d91a in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb6d850c0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0xb6d84f56 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0xb6d6dfef in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0x0804ac6a in main (argc=7, argv=0xbff90dc4) at main.cpp:332
Comment 1 caulier.gilles 2008-01-23 10:29:36 UTC
Ron,

Sound like a broken depedencies. The backtrace is a non-sence for me.

Can you recompile yourself digiKam & co and try again ?

Gilles Caulier
Comment 2 Ron Lusk 2008-01-23 13:12:35 UTC
I'll give it a try.  Thanks

On 23 Jan 2008 09:29:37 -0000, Gilles Caulier <caulier.gilles@gmail.com>
wrote:
[bugs.kde.org quoted mail]



I&#39;ll give it a try.&nbsp; Thanks<br><br>
<div><span class="gmail_quote">On 23 Jan 2008 09:29:37 -0000, <b class="gmail_sendername">Gilles Caulier</b> &lt;<a href="mailto:caulier.gilles@gmail.com">caulier.gilles@gmail.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter.
<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=156418">http://bugs.kde.org/show_bug.cgi?id=156418</a><br><br><br><br><br>------- Additional Comments From caulier.gilles gmail com&nbsp;&nbsp;2008-01-23 10:29 -------<br>Ron,<br>
<br>Sound like a broken depedencies. The backtrace is a non-sence for me.<br><br>Can you recompile yourself digiKam &amp; co and try again ?<br><br>Gilles Caulier<br></blockquote></div><br><br clear="all"><br>-- <br>Ron Lusk
<br><a href="mailto:ronlusk@alum.mit.edu">ronlusk@alum.mit.edu</a> 
Comment 3 reinhard.schwab 2008-02-13 11:34:26 UTC
i experience this crash too, if i try to rotate a foto right or left.
opensuse 10.2, digikam 0.9.3, kde 3.5.5

the kde crash manager shows this info

[Thread debugging using libthread_db enabled]
[New Thread 47854901842032 (LWP 31964)]
[New Thread 1098918208 (LWP 31982)]
[New Thread 1082132800 (LWP 31981)]
[New Thread 1090525504 (LWP 31980)]
0x00002b860f2f9997 in ioctl () from /lib64/libc.so.6
#0  0x00002b860f2f9997 in ioctl () from /lib64/libc.so.6
#1  0x00002b8611d528f7 in _XEventsQueued () from /usr/lib64/libX11.so.6
#2  0x00002b8611d4183d in XPending () from /usr/lib64/libX11.so.6
#3  0x00002b860e4f73ac in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#4  0x00002b860e555903 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#5  0x00002b860e5557b2 in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#6  0x000000000040316a in main ()

i have build the packman src rpm and installed the resulting binary packages too.

Comment 4 reinhard.schwab 2008-02-14 00:57:58 UTC
gdb shows this

Found dcraw version: 8.77
Exif Orientation: 1
[New Thread 1090525504 (LWP 11723)]
Exif Orientation: 1

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1090525504 (LWP 11723)]
0x00002b26f432b3be in QString::operator= () from /usr/lib/qt3/lib64/libqt-mt.so.3
(gdb) bt
#0  0x00002b26f432b3be in QString::operator= () from /usr/lib/qt3/lib64/libqt-mt.so.3
#1  0x00002b26f430b714 in QFileInfo::QFileInfo () from /usr/lib/qt3/lib64/libqt-mt.so.3
#2  0x00002b26f28c6d68 in KExiv2Iface::KExiv2::load ()
   from /opt/kde3/lib64/libkexiv2.so.3
#3  0x00002aaaac1cb709 in KExiv2Iface::KExiv2::setImageOrientation ()
   from /opt/kde3/lib64/libkexiv2.so.1
#4  0x00002aaaabfae96a in KIPIJPEGLossLessPlugin::transformJPEG ()
   from /opt/kde3/lib64/kde3/kipiplugin_jpeglossless.so
#5  0x00002aaaabfb2c45 in KIPIJPEGLossLessPlugin::ImageRotate::rotateJPEG ()
   from /opt/kde3/lib64/kde3/kipiplugin_jpeglossless.so
#6  0x00002aaaabfb33f7 in KIPIJPEGLossLessPlugin::ImageRotate::rotate ()
   from /opt/kde3/lib64/kde3/kipiplugin_jpeglossless.so
#7  0x00002aaaabfafb0e in KIPIJPEGLossLessPlugin::ActionThread::run ()
   from /opt/kde3/lib64/kde3/kipiplugin_jpeglossless.so
#8  0x00002b26f40448cb in QThreadInstance::start ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#9  0x00002b26f75ff09e in start_thread () from /lib64/libpthread.so.0
#10 0x00002b26f4e0a4cd in clone () from /lib64/libc.so.6
#11 0x0000000000000000 in ?? ()
(gdb) quit
Comment 5 reinhard.schwab 2008-02-14 01:34:37 UTC
i have now replaced the digikam packman package by a package from a suse repository and
rotating works again.

http://download.opensuse.org/repositories/KDE:/Backports/openSUSE_10.2/
Comment 6 Ron Lusk 2008-02-16 14:26:48 UTC
Managed to get most of digiKam working again with the help of someone else
who had the same problem and got rid of the Packman repositories.

The GPSSync plugin is great, and very useful.  I've geotagged the whole set
of my photos from  a recent India trip with it, and found it very good.

There is only one problem: India is one of the strange places that has a
timezone off by 30 minutes.  All of India is at UTC+5:30, so I couldn't
localize anything taken in that timezone.  (Since I also use a GiSTEQ
PhotoTrackr Lite, I took most of my pictures on US Eastern Standard, and
adjusted the time of the others.)

For those Indian users, however, you may want to drop in a +5:30 entry in
the dropdown.

Thanks,
ron

On 23 Jan 2008 09:29:37 -0000, Gilles Caulier <caulier.gilles@gmail.com>
wrote:

[bugs.kde.org quoted mail]



Managed to get most of digiKam working again with the help of someone else who had the same problem and got rid of the Packman repositories.<br><br>The GPSSync plugin is great, and very useful.&nbsp; I&#39;ve geotagged the whole set of my photos from&nbsp; a recent India trip with it, and found it very good.&nbsp; <br>
<br>There is only one problem: India is one of the strange places that has a timezone off by 30 minutes.&nbsp; All of India is at UTC+5:30, so I couldn&#39;t localize anything taken in that timezone.&nbsp; (Since I also use a GiSTEQ PhotoTrackr Lite, I took most of my pictures on US Eastern Standard, and adjusted the time of the others.)<br>
<br>For those Indian users, however, you may want to drop in a +5:30 entry in the dropdown.<br><br>Thanks,<br>ron<br><br><div class="gmail_quote">On 23 Jan 2008 09:29:37 -0000, Gilles Caulier &lt;<a href="mailto:caulier.gilles@gmail.com">caulier.gilles@gmail.com</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter.<br>
<br><a href="http://bugs.kde.org/show_bug.cgi?id=156418" target="_blank">http://bugs.kde.org/show_bug.cgi?id=156418</a><br><br><br><br><br>------- Additional Comments From caulier.gilles gmail com &nbsp;2008-01-23 10:29 -------<br>
Ron,<br><br>Sound like a broken depedencies. The backtrace is a non-sence for me.<br><br>Can you recompile yourself digiKam &amp; co and try again ?<br><font color="#888888"><br>Gilles Caulier<br></font></blockquote></div>
<br><br clear="all"><br>-- <br>Ron Lusk<br><a href="mailto:ronlusk@alum.mit.edu">ronlusk@alum.mit.edu</a>
Comment 7 Gerhard Kulzer 2008-02-16 14:50:59 UTC
Hi Ron, this has been fixed quite some time ago (11. dec 07), see here:
d->timeZoneCB->insertItem("GMT-12:00");
    d->timeZoneCB->insertItem("GMT-11:00");
    d->timeZoneCB->insertItem("GMT-10:00");
    d->timeZoneCB->insertItem("GMT-09:30");
    d->timeZoneCB->insertItem("GMT-09:00");
    d->timeZoneCB->insertItem("GMT-08:00");
    d->timeZoneCB->insertItem("GMT-07:00");
    d->timeZoneCB->insertItem("GMT-06:00");
    d->timeZoneCB->insertItem("GMT-05:30");
    d->timeZoneCB->insertItem("GMT-05:00");
    d->timeZoneCB->insertItem("GMT-04:30");
    d->timeZoneCB->insertItem("GMT-04:00");
    d->timeZoneCB->insertItem("GMT-03:30");
    d->timeZoneCB->insertItem("GMT-03:00");
    d->timeZoneCB->insertItem("GMT-02:00");
    d->timeZoneCB->insertItem("GMT-01:00");
    d->timeZoneCB->insertItem("GMT+00:00");
    d->timeZoneCB->insertItem("GMT+01:00");
    d->timeZoneCB->insertItem("GMT+02:00");
    d->timeZoneCB->insertItem("GMT+03:00");
    d->timeZoneCB->insertItem("GMT+03:30");
    d->timeZoneCB->insertItem("GMT+04:00");
    d->timeZoneCB->insertItem("GMT+05:00");
    d->timeZoneCB->insertItem("GMT+05:30");    // See B.K.O # 149491
    d->timeZoneCB->insertItem("GMT+05:45");
    d->timeZoneCB->insertItem("GMT+06:00");
    d->timeZoneCB->insertItem("GMT+06:30");
    d->timeZoneCB->insertItem("GMT+07:00");
    d->timeZoneCB->insertItem("GMT+08:00");
    d->timeZoneCB->insertItem("GMT+08:45");
    d->timeZoneCB->insertItem("GMT+09:00");
    d->timeZoneCB->insertItem("GMT+09:30");
    d->timeZoneCB->insertItem("GMT+10:00");
    d->timeZoneCB->insertItem("GMT+10:30");
    d->timeZoneCB->insertItem("GMT+11:00");
    d->timeZoneCB->insertItem("GMT+11:30");
    d->timeZoneCB->insertItem("GMT+12:00");
    d->timeZoneCB->insertItem("GMT+12:45");
    d->timeZoneCB->insertItem("GMT+13:00");
    d->timeZoneCB->insertItem("GMT+14:00");

Please check out or install the latest kipi-plugins

Gerhard
Comment 8 caulier.gilles 2008-03-18 12:54:15 UTC
Main subject of this entry is relevant of packaging. Others points are already fixed. I close it...

Gilles
Comment 9 caulier.gilles 2021-05-04 09:58:01 UTC
Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4
Comment 10 Ron Lusk 2021-05-05 01:28:47 UTC
Thanks. Sorry this has hung around so long.
Comment 11 Ron Lusk 2021-05-05 01:30:14 UTC
What might make you smile is I just for the first time in 15 years or so booted up the system I first reported this from. I need to make sure I have any archived files off of it, and then shut it down for the last time and move it out.

Thanks for your patience and your contributions to KDE (and, perhaps, elsewhere).