Ubuntu
tracker-miners package

tracker-extract-3 crashed during a release upgrade

Bug #2015919 reported by Brian Murray
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tracker-miners (Ubuntu)
New
Undecided
Unassigned
ubuntu-release-upgrader (Ubuntu)
New
High
Unassigned
Ubuntu ubuntu-23.04

Bug Description

Every time I perform a release upgrade I receive a crash report from tracker-extract3 which is an unpleasant experience. If possible we should stop the tracker extract service so that a user is not presented with a crash during the upgrade process.

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: tracker-extract 3.4.3-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 11 11:15:59 2023
ExecutablePath: /usr/libexec/tracker-extract-3
ExecutableTimestamp: 1679659121
InstallationDate: Installed on 2023-04-10 (1 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018.1)
ProcCmdline: /usr/libexec/tracker-extract-3
ProcCwd: /home/bdmurray
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
 Segfault happened at: 0x7f9a86ec55b8: mov (%r15),%rbx
 PC (0x7f9a86ec55b8) ok
 source "(%r15)" (0xafe16f422d096c20) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: tracker-miners
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/tracker-miners-3.0/libtracker-miner-3.0.so
 ?? () from /lib/x86_64-linux-gnu/libffi.so.8
 ?? () from /lib/x86_64-linux-gnu/libffi.so.8
 ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8
 g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: tracker-extract-3 crashed with SIGSEGV in ffi_call()
UpgradeStatus: Upgraded to lunar on 2023-04-11 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]
separator:

Revision history for this message
Brian Murray (brian-murray) wrote :
information type: Private → Public
Revision history for this message
Brian Murray (brian-murray) wrote :

Here is the main log file from the upgrade.

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2012638, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
Revision history for this message
Brian Murray (brian-murray) wrote :

I wasn't sure if it was the new package causing an issue so modified my sources.list file to contain lunar instead of kinetic and then only upgraded tracker-extract and its dependencies. During this process I did *not* receive a crash report.

Brian Murray (brian-murray)
tags: added: cuqa-automated-testing
Changed in ubuntu-release-upgrader (Ubuntu):
milestone: none → ubuntu-23.04
importance: Undecided → High
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Let's merge this with bug 2012638 even if it is just for a workaround.

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

Other bug subscribers

Remote bug watches

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