[frameworks-kfilemetadata] [Bug 406229] baloo_file_extractor crashes in Exiv2::Internal::TiffReader::readTiffEntry() on a specific TIFF file

2019-05-20 Thread Иван Туманов
https://bugs.kde.org/show_bug.cgi?id=406229

Иван Туманов  changed:

   What|Removed |Added

 CC||tu4manj...@yandex.ru

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kfilemetadata] [Bug 406229] baloo_file_extractor crashes in Exiv2::Internal::TiffReader::readTiffEntry() on a specific TIFF file

2019-04-06 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=406229

--- Comment #8 from Nicolas Fella  ---
Sorry, I don't

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kfilemetadata] [Bug 406229] baloo_file_extractor crashes in Exiv2::Internal::TiffReader::readTiffEntry() on a specific TIFF file

2019-04-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=406229

--- Comment #7 from Nate Graham  ---
Do you have a link to the commit handy? Then I can see about prodding the
discrete release distros to patch their Exiv packages.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kfilemetadata] [Bug 406229] baloo_file_extractor crashes in Exiv2::Internal::TiffReader::readTiffEntry() on a specific TIFF file

2019-04-06 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=406229

--- Comment #6 from Nicolas Fella  ---
Looks like the issue is resolved in exiv master

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kfilemetadata] [Bug 406229] baloo_file_extractor crashes in Exiv2::Internal::TiffReader::readTiffEntry() on a specific TIFF file

2019-04-06 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=406229

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #5 from Nate Graham  ---
Relevant part of the backtrace:

#17 0x7fd23bcada06 in Exiv2::TiffParser::decode(Exiv2::ExifData&,
Exiv2::IptcData&, Exiv2::XmpData&, unsigned char const*, unsigned int) () from
/usr/lib/x86_64-linux-gnu/libexiv2.so.26
#18 0x7fd23bc29330 in Exiv2::ExifParser::decode(Exiv2::ExifData&, unsigned
char const*, unsigned int) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26
#19 0x7fd23bc43170 in Exiv2::JpegBase::readMetadata() () from
/usr/lib/x86_64-linux-gnu/libexiv2.so.26
#20 0x7fd24004d208 in KFileMetaData::Exiv2Extractor::extract
(this=0x5639d84966f0, result=0x7ffece28b320) at
./src/extractors/exiv2extractor.cpp:163
#21 0x5639d6eb022f in Baloo::App::index (this=this@entry=0x7ffece28bac0,
tr=0x5639d8abbc80, url=..., id=id@entry=5642697968715777) at
./src/file/extractor/app.cpp:192
#22 0x5639d6eb0b8e in Baloo::App::processNextFile (this=0x7ffece28bac0) at
./src/file/extractor/app.cpp:112


So Exiv2 first (correctly) tries the JPEG extractor, then switches to the TIFF
extractor for some reason, then crashes.

At this point it feels like the issue is in Exiv2 itself, not Baloo or
KFileMetadata, both of which have done their part as much as they're able. Can
you file a bug with the Exiv2 folks? The fully symbolicated backtrace you
attached will probably be very useful for them. Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kfilemetadata] [Bug 406229] baloo_file_extractor crashes in Exiv2::Internal::TiffReader::readTiffEntry() on a specific TIFF file

2019-04-06 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=406229

Nicolas Fella  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #4 from Nicolas Fella  ---
Still happens with Neon unstable

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kfilemetadata] [Bug 406229] baloo_file_extractor crashes in Exiv2::Internal::TiffReader::readTiffEntry() on a specific TIFF file

2019-04-06 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=406229

Nicolas Fella  changed:

   What|Removed |Added

 Attachment #119243|0   |1
is obsolete||

--- Comment #3 from Nicolas Fella  ---
Created attachment 119273
  --> https://bugs.kde.org/attachment.cgi?id=119273=edit
Backtrace with debug symbols

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kfilemetadata] [Bug 406229] baloo_file_extractor crashes in Exiv2::Internal::TiffReader::readTiffEntry() on a specific TIFF file

2019-04-05 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=406229

Nate Graham  changed:

   What|Removed |Added

Summary|baloo-file-extractor|baloo_file_extractor
   |crashes |crashes in
   ||Exiv2::Internal::TiffReader
   ||::readTiffEntry() on a
   ||specific TIFF file
 CC||n...@kde.org
 Status|REPORTED|NEEDSINFO
  Component|Baloo File Daemon   |general
 Resolution|--- |WAITINGFORINFO
Product|frameworks-baloo|frameworks-kfilemetadata
   Assignee|baloo-bugs-n...@kde.org |pinak.ah...@gmail.com
Version|unspecified |5.56.0

--- Comment #2 from Nate Graham  ---
Crashing in Exiv2::Internal::TiffReader::readTiffEntry. It's interesting that
you say it crashes on a JPEG file, because KFileMetadata was trying to open it
as a TIFF. It's possible this is fixed in git master/5.57 due to improvements
in file type detection; can you test?

-- 
You are receiving this mail because:
You are watching all bug changes.