Bug 407525

Summary: baloo_file_extr crashes on photos edited by Google Photos
Product: [Frameworks and Libraries] frameworks-baloo Reporter: Ondrej Machulda <ondrej.machulda>
Component: Baloo File DaemonAssignee: baloo-bugs-null
Status: RESOLVED WORKSFORME    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 5.57.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Example photo causing baloo to crash
Another photo crashing baloo

Description Ondrej Machulda 2019-05-14 14:10:47 UTC
Created attachment 120059 [details]
Example photo causing baloo to crash

SUMMARY
Specific photos - see attachment, which were edited and downloaded from Google Photos causes baloo_file_extr to always crash and never gets indexed.

Probably Google Photos does some changes in the file or its metadata, which cannot be handled by baloo_file_extr, as other photos from the same camera gets indexed without an issue.

I have multiple photos downloaded from Google Photos which causes baloo to crash.


STEPS TO REPRODUCE
1. Have any of attached files indexed by baloo

Or let the file be indexed manually:
$ balooctl index example-1.jpg 
Indexing example-1.jpg
Segmentation fault (core dumped)


OBSERVED RESULT
systemd-coredump[19612]: Process 16897 (baloo_file_extr) of user 1000 dumped core.

EXPECTED RESULT
File gets indexed.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.3
Kernel Version: 5.0.13-arch1-1-ARCH
OS Type: 64-bit
Processors: 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz
Memory: 19,5 GiB

ADDITIONAL INFORMATION
Opening the file in GIMP and just re-saving it as jpeg gets the indexing fixed.
Comment 1 Ondrej Machulda 2019-05-14 14:11:16 UTC
Created attachment 120060 [details]
Another photo crashing baloo
Comment 2 Nate Graham 2019-05-21 19:56:25 UTC
Thank you very much for attaching the photo. Any chance you can also attach a backtrace of the crash too?

https://community.kde.org/Get_Involved/Bug_Reporting#Crash_reports_must_include_backtraces
Comment 3 Bug Janitor Service 2019-06-05 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2019-06-20 04:33:10 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!