| Summary: | Digikam crash when saving edited picture | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Thomas <kheops46230> |
| Component: | Metadata-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, geza, McFiddich, nils.pooth, wmey |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.11.0 | ||
| Target Milestone: | --- | ||
| Platform: | Mint (Ubuntu based) | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.3.0 | |
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Thomas
2015-07-19 09:55:34 UTC
It crash in Exiv2 shared lib in TIFF file parser. Please report this problem to Exiv2 library bugzilla with exiv2 version used (look in digiKam Help/Components Info dialog for details). http://dev.exiv2.org/projects/exiv2/wiki Also image edited where you can reproduce the problem. Gilles Caulier Thank you for your very quick answer. As requested I report the bug to exiv2 dev team, see link below. http://dev.exiv2.org/issues/1094 Thomas Created attachment 94155 [details]
New crash information added by DrKonqi
gwenview (4.14.0 pre) on KDE Platform 4.14.10 using Qt 4.8.7
- What I was doing when the application crashed:
I know this bug is closed. I also followed the bug report from Thomas at exiv2. The exiv2-guys closed his bug as well because they said they can't reproduse it.
I still have the same problem as Thomas. When I edit any JPG from my CASIO EX-Z300 with Gwenview or Digikam and try to save, both programs will crash immeditaley without saving the JPG. This happens every time.
This happens never when I edit JPGs from my CANON EOS 500D. Before Tumbleweed I used 13.1 and had not this problem.
When I load this CASIO JPG in Gimp and remove any metadata and reopen it with Gwenview and edit and save again: Everything works fine.
When you're still convinced it's an exiv-problem - sorry for my report. I will try to reopen it at exiv as well.
Nils
-- Backtrace (Reduced):
#6 0x00007f81c7617fbb in Exiv2::Internal::TiffComponent::addPath(unsigned short, std::stack<Exiv2::Internal::TiffPathItem, std::deque<Exiv2::Internal::TiffPathItem, std::allocator<Exiv2::Internal::TiffPathItem> > >&, Exiv2::Internal::TiffComponent*, std::auto_ptr<Exiv2::Internal::TiffComponent>) () from /usr/lib64/libexiv2.so.14
#7 0x00007f81c761d8cf in Exiv2::Internal::TiffMnEntry::doAddPath(unsigned short, std::stack<Exiv2::Internal::TiffPathItem, std::deque<Exiv2::Internal::TiffPathItem, std::allocator<Exiv2::Internal::TiffPathItem> > >&, Exiv2::Internal::TiffComponent*, std::auto_ptr<Exiv2::Internal::TiffComponent>) () from /usr/lib64/libexiv2.so.14
#8 0x00007f81c7617fd2 in Exiv2::Internal::TiffComponent::addPath(unsigned short, std::stack<Exiv2::Internal::TiffPathItem, std::deque<Exiv2::Internal::TiffPathItem, std::allocator<Exiv2::Internal::TiffPathItem> > >&, Exiv2::Internal::TiffComponent*, std::auto_ptr<Exiv2::Internal::TiffComponent>) () from /usr/lib64/libexiv2.so.14
#9 0x00007f81c76186df in Exiv2::Internal::TiffDirectory::doAddPath(unsigned short, std::stack<Exiv2::Internal::TiffPathItem, std::deque<Exiv2::Internal::TiffPathItem, std::allocator<Exiv2::Internal::TiffPathItem> > >&, Exiv2::Internal::TiffComponent*, std::auto_ptr<Exiv2::Internal::TiffComponent>) () from /usr/lib64/libexiv2.so.14
#10 0x00007f81c7617fd2 in Exiv2::Internal::TiffComponent::addPath(unsigned short, std::stack<Exiv2::Internal::TiffPathItem, std::deque<Exiv2::Internal::TiffPathItem, std::allocator<Exiv2::Internal::TiffPathItem> > >&, Exiv2::Internal::TiffComponent*, std::auto_ptr<Exiv2::Internal::TiffComponent>) () from /usr/lib64/libexiv2.so.14
Problem is into Exiv2 shared library when TIFF structure is parsed. report this problem to Exiv2 team. Gilles Caulier *** Bug 351638 has been marked as a duplicate of this bug. *** (In reply to Gilles Caulier from comment #4) > Problem is into Exiv2 shared library when TIFF structure is parsed. report > this problem to Exiv2 team. > > Gilles Caulier I do report the bug to Exiv2 dev team but they close it as "not a bug". I don't have the knowledge to dig further and help the Exiv2 spot the bug. Maybe you are someone else can help them to do so ? As reference the ticket in Exiv2 bug tracking system: http://dev.exiv2.org/issues/1094 (In reply to Thomas from comment #6) > > (In reply to Gilles Caulier from comment #4) > > Problem is into Exiv2 shared library when TIFF structure is parsed. report > > this problem to Exiv2 team. > > > > Gilles Caulier > > I do report the bug to Exiv2 dev team but they close it as "not a bug". I > don't have the knowledge to dig further and help the Exiv2 spot the bug. > Maybe you are someone else can help them to do so ? > > As reference the ticket in Exiv2 bug tracking system: > http://dev.exiv2.org/issues/1094 Sorry for my terrible english. I meant "Maybe you OR someone else can help them to do so ?" Well, it simple. Look well the original trace : #20 0x00007fd990ab7bde in Exiv2::ExifParser::encode (blob=..., pData=0x0, size=0, byteOrder=Exiv2::littleEndian, exifData=...) at exif.cpp:719 #21 0x00007fd990ad1f29 in Exiv2::JpegBase::doWriteMetadata (this=this@entry=0x7fd8e804bf50, outIo=...) at jpgimage.cpp:837 #22 0x00007fd990ad36ca in Exiv2::JpegBase::writeMetadata (this=0x7fd8e804bf50) at jpgimage.cpp:662 #23 0x00007fd99827b7d6 in KExiv2Iface::KExiv2::Private::saveOperations (this=this@entry=0x7fd8e8002420, finfo=..., image=...) at ../../libkexiv2/kexiv2_p.cpp:312 This happen when a metadata is writtent o a jpeg file, into TIFF metadata structure. As i can see, the test done by Exiv2 team is just to read metadata with your JPEG image, through exiv2 CLI tool, not to write something into it... So the test in Exiv2 report is not valid to said int's not a bug... Re-open it please... Gilles Caulier According to this ticket : http://dev.exiv2.org/issues/1106 They solve the issue andan user have been able to test it positively. As I don't know how to recompile everything I will wait for the next release of exiv2. HI there, i have the same problem. it will be solved in exiv2 version 0.26. Until this release i changed my dk settings, so no data will be written in the metadat of the pictures, just in the dk dtabase. so it works without problem. with the new exiv2 version i hope to save these again in the metadata. Thanks to you for your patience and help *** Bug 357340 has been marked as a duplicate of this bug. *** *** Bug 359674 has been marked as a duplicate of this bug. *** Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4 |