baloo_file_extractor crashed with SIGSEGV

Bug #1761672 reported by Johannes Kalliauer
62
This bug affects 4 people
Affects Status Importance Assigned to Milestone
baloo-kf5 (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Just after startup

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: baloo-kf5 5.44.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 6 08:17:29 2018
ExecutablePath: /usr/bin/baloo_file_extractor
InstallationDate: Installed on 2017-04-07 (363 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcCmdline: /usr/bin/baloo_file_extractor
SegvAnalysis:
 Segfault happened at: 0x7f4b5322d498: mov 0x4(%rdx),%eax
 PC (0x7f4b5322d498) ok
 source "0x4(%rdx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: baloo-kf5
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libexiv2.so.14
 () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so
 () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kfilemetadata/kfilemetadata_exiv2extractor.so
 ()
 ()
Title: baloo_file_extractor crashed with SIGSEGV
UpgradeStatus: Upgraded to bionic on 2018-03-29 (7 days ago)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Johannes Kalliauer (jokalliauer1989) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 Exiv2::ValueType<std::pair<unsigned int, unsigned int> >::toFloat (this=0x564bc823a480, n=0) at ../include/exiv2/value.hpp:1695
 (anonymous namespace)::toVariantDouble (value=...) at ./src/extractors/exiv2extractor.cpp:98
 (anonymous namespace)::toVariant (type=QVariant::Double, value=...) at ./src/extractors/exiv2extractor.cpp:128
 KFileMetaData::Exiv2Extractor::add (this=this@entry=0x564bc806bd50, result=result@entry=0x7fff3dfab580, data=..., prop=prop@entry=KFileMetaData::Property::PhotoFocalLength, name=name@entry=0x7f4b5361c2e0 "Exif.Photo.FocalLength", type=type@entry=QVariant::Double) at ./src/extractors/exiv2extractor.cpp:225
 KFileMetaData::Exiv2Extractor::extract (this=0x564bc806bd50, result=0x7fff3dfab580) at ./src/extractors/exiv2extractor.cpp:182

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in baloo-kf5 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in baloo-kf5 (Ubuntu):
status: New → Confirmed
Revision history for this message
Michael Mess (michael-michaelmess) wrote :

Still happens after each startup.

uname -a
Linux thinkpad 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.