tracker-extract crashed with SIGSEGV in g_simple_async_result_complete()

Bug #1309073 reported by Cristian Aravena Romero
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
Invalid
Undecided
Unassigned

Bug Description

Crash.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: tracker-extract 1.0.0-1ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging]
Uname: Linux 3.14.1-031401-lowlatency x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Thu Apr 17 12:36:27 2014
ExecutablePath: /usr/lib/tracker/tracker-extract
InstallationDate: Installed on 2014-01-23 (84 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
ProcCmdline: /usr/lib/tracker/tracker-extract
SegvAnalysis:
 Segfault happened at: 0x7f287b435fb7: mov 0x8(%r12),%eax
 PC (0x7f287b435fb7) ok
 source "0x8(%r12)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libtracker-miner-1.0.so.0
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libtracker-sparql-1.0.so.0
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libtracker-sparql-1.0.so.0
Title: tracker-extract crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Ubuntu GNOME (ug-bot) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Stacktrace.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : ThreadStacktrace.txt
Changed in ubuntu-gnome:
status: New → Invalid
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

package libtracker-miner-1.0-0 does not exist, ignoring
tracker-miner-fs version 1.0.0-1ubuntu1~trusty1 required, but 0.16.4-0ubuntu1~saucy2 is available
tracker-utils version 1.0.0-1ubuntu1~trusty1 required, but 0.16.4-0ubuntu1~saucy2 is available
package libtracker-sparql-1.0-0 does not exist, ignoring
tracker version 1.0.0-1ubuntu1~trusty1 required, but 0.16.4-0ubuntu1~saucy2 is available
package libtracker-control-1.0-0 does not exist, ignoring
package libupower-glib2 does not exist, ignoring
gsettings-desktop-schemas version 3.12.0-0ubuntu1~trusty1 required, but 3.10.1-0ubuntu1 is available
libsoup2.4-1 version 2.46.0-1~trusty1 required, but 2.44.2-1ubuntu2 is available
tracker-extract version 1.0.0-1ubuntu1~trusty1 required, but 0.16.4-0ubuntu1~saucy2 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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