tracker-miner-fs crashed with SIGSEGV in g_file_get_uri()

Bug #1324808 reported by Laurent Bonnaud
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

I get this crash (or bug #1327131) each time I log in.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: tracker-miner-fs 1.0.1-2ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.13.0-29.52-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: KDE
Date: Fri May 30 10:05:16 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/tracker/tracker-miner-fs
ProcCmdline: /usr/lib/tracker/tracker-miner-fs
SegvAnalysis:
 Segfault happened at: 0x7fc598cd181c <g_file_get_uri+28>: cmp %rax,0x0(%rbp)
 PC (0x7fc598cd181c) ok
 source "%rax" ok
 destination "0x0(%rbp)" (0x00000001) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 g_file_get_uri (file=0xd19620) at /build/buildd/glib2.0-2.40.0/./gio/gfile.c:546
 sparql_files_compose_query (files=<optimized out>, n_files=483) at tracker-file-notifier.c:740
 sparql_files_query_start (n_files=<optimized out>, files=<optimized out>, notifier=0x9f1130) at tracker-file-notifier.c:759
 crawler_finished_cb (crawler=<optimized out>, was_interrupted=<optimized out>, user_data=0x9f1130) at tracker-file-notifier.c:843
 g_cclosure_marshal_VOID__BOOLEANv (closure=<optimized out>, return_value=<optimized out>, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0xac0020) at /build/buildd/glib2.0-2.40.0/./gobject/gmarshal.c:188
Title: tracker-miner-fs crashed with SIGSEGV in g_file_get_uri()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip fuse libvirtd lpadmin plugdev sambashare staff sudo

Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :
Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :

The following environment variables might be needed to reproduce this bug:

MALLOC_CHECK_=3
MALLOC_PERTURB_=117

Revision history for this message
Ubuntu GNOME (ug-bot) wrote :

StacktraceTop:
 g_file_create_readwrite (file=0xd19620, flags=(G_FILE_CREATE_PRIVATE | G_FILE_CREATE_REPLACE_DESTINATION | unknown: 480), cancellable=0xc30630, error=0x9d3ce0) at /build/buildd/glib2.0-2.41.0~git20140523.570b27b9/./gio/gfile.c:1878
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Stacktrace.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : StacktraceSource.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
information type: Private → Public
description: updated
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.