Bug #1181

Casio.jpg exports crash darktable - suse leap 42.1

Added by Anonymous about 1 year ago. Updated about 1 year ago.

Status:ClosedStart date:27 Apr 2016
Priority:NormalDue date:
Assignee:Robin Mills% Done:

100%

Category:duplicateEstimated time:1.00 hour
Target version:0.26

Description

Hi,

I tried darktable and it crashed when I exported Casio JPGs.
System: Suse leap 42.1 Darktable 2.0.3-130.1
No crash with the same Casios in darktable 1.6.9 in my present opensuse 13.2 64bit.

Bugreport in darktable says:
https://www.darktable.org/redmine/issues/10864#change-29765
"The only solution I see is to upgrade exiv2 library. (and recompile dt against that new exiv2 lib) This is purely exiv2 bug, and it is a crash and not an exception so we can not even catch it."

There is one Casio.jpg attached.

Any help?

cu
Peter

CIMG4704.JPG (8.96 MB) Anonymous, 27 Apr 2016 13:45


Related issues

Related to Exiv2 - Bug #1106: Crash in exiv2 due to assertion when setting rating on jp... Closed 19 Aug 2015
Related to Exiv2 - Bug #1184: digikam crash when importing Casio jpeg Closed 16 May 2016

History

#1 Updated by Anonymous about 1 year ago

Ups:It seems the jpg wasn't attached.

#2 Updated by Robin Mills about 1 year ago

  • Category set to not-a-bug
  • Status changed from New to Resolved
  • Assignee set to Robin Mills
  • Target version set to 0.26
  • % Done changed from 0 to 100
  • Estimated time set to 1.00

Thanks, Peter. I think this is a duplicate of #1106 which has been resolved. For sure, your file is OK on the trunk:

640 rmills@rmillsmbp:~/gnu/exiv2/ttt $ exiv2 --verbose --version --grep svn
exiv2 0.25 001900 (64 bit build)
svn=4291
641 rmills@rmillsmbp:~/gnu/exiv2/ttt $ exiv2 -pa --grep date/i http://dev.exiv2.org/attachments/download/996/CIMG4704.JPG
Exif.Image.DateTime                          Ascii      20  2016:01:17 10:13:08
Exif.Photo.DateTimeOriginal                  Ascii      20  2016:01:17 10:13:08
Exif.Photo.DateTimeDigitized                 Ascii      20  2016:01:17 10:13:08
Exif.Casio2.FirmwareDate                     Ascii      18  2011:09:14 11:17
642 rmills@rmillsmbp:~/gnu/exiv2/ttt $ 

You can download daily/weekly/monthly builds from our buildserver. http://exiv2.dyndns.org:8080

Beware: when you replace the libexiv2 shared object, system/DarkTable updates might revert to the 'vanilla' v0.25 shared object. To determine the location of libexiv2 is platform dependant. On linux run $ lsof | grep -i darktable | grep libexiv while DarkTable is running. Stop DarkTable and update the shared object from our buildserver. Be sure to keep a copy of your system's original libexiv2 shared object.

There was a recent discussion about exception handlers/signal handlers in DigiKam: http://dev.exiv2.org/issues/1164#note-6 Nicolas found this article: http://angasule.blogspot.fr/2011/09/catching-null-pointer-exceptions-with.html It's not good that libexiv2 should crash. However, the host application (in this case DarkTable) should have a process signal handler to save the day. In the discussion on #1164, it was agreed that it is a very bad idea for a library to install a signal handler. Perhaps you could suggest to our friends at DarkTable that they install a signal handler.

#3 Updated by Robin Mills about 1 year ago

  • Category changed from not-a-bug to duplicate
  • Status changed from Resolved to Closed

#4 Updated by Anonymous about 1 year ago

Thank you for the quick answer.

I've sent a bug report to https://bugzilla.suse.com/show_bug.cgi?id=964344.
I think, I'll wait till suse moves from exiv2 v0.25 to exiv2 v0.26 in the appropriate repository as Darktable is presently not usable with Suse leap 42.1 and (my??) Casio.jpgs.
By the way, no problem with Olympus and Panasonic Raws.

cu
Peter

#5 Updated by Robin Mills about 1 year ago

Peter

I was not involved in the analysis or fixing of this issue - that honour goes to Andreas. Regrettably you are in trouble with Darktable/Casio/exiv2.

Patching your system using a build from our buildserver is a 5 minute job. If you'd like assistance to patching your machine from our buildserver, I know an Exiv2 user in The Netherlands who may be willing to assist you over Skype/Phone/etc.

Waiting for v0.26 will be effective. I expect to be code-complete for v0.26 in June. I don't know how long it takes the code to make its way through the various release and distribution processes.

Pascal de Brujin of the DarkTable project does maintain exiv2 v0.25 updates for distribution. I'll ask him to consider including the fix you require. So, a fix may arrive on your machine before v0.26.

#6 Updated by Anonymous about 1 year ago

Thank you very much for that offer.

A long time ago, I found out, that tweaking on one part of software soon may demand some other changes somewhere else. I like to avoid that. So, unless it is absolutely necessary, I'm willing to wait until updates/corrections find their way into the distribution.

Darktable is a pretty impressive piece of software and I have still a long way to go till I reach the limits of version 1.6.9 (casio support working, should be with exiv2 v0.24)).

So there is no real hurry. Well, let's say just some curiosity of how things work with Darktable 2.x.

cu
Peter

#7 Updated by Robin Mills about 1 year ago

Right. r3889 and r3890 are included in exiv2: 0.25-2.1pmjdebruijn1~xenial https://launchpad.net/~pmjdebruijn/+archive/ubuntu/darktable-unstable/+packages thanks to splendid work by Pascal.

This open-source stuff really works. It's not just the code, the support is much better. The community cooperates, corporations compete.

Also available in: Atom PDF

Redmine Appliance - Powered by TurnKey Linux