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

Bug #1387217 reported by Laurent Bonnaud
810
This bug affects 277 people
Affects Status Importance Assigned to Milestone
Tracker
Invalid
High
Ubuntu GNOME
Fix Released
Undecided
Unassigned
Fedora
Fix Released
Undecided

Bug Description

This crash happened while I was logging in.

The following environment variables may help to reproduce the crash:

  MALLOC_CHECK_=3
  MALLOC_PERTURB_=117

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: tracker-miner-fs 1.2.3-0ubuntu1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Oct 29 15:43:32 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/tracker/tracker-miner-fs
ProcCmdline: /usr/lib/tracker/tracker-miner-fs
SegvAnalysis:
 Segfault happened at: 0x7fb7f6ca4f8f <g_type_check_instance_is_a+63>: testb $0x4,0x16(%rax)
 PC (0x7fb7f6ca4f8f) ok
 source "$0x4" ok
 destination "0x16(%rax)" (0x5320545245534e5e) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 g_type_check_instance_is_a (type_instance=type_instance@entry=0x1a8f840, iface_type=iface_type@entry=16758528) at /build/buildd/glib2.0-2.42.0/./gobject/gtype.c:3969
 g_file_get_uri (file=0x1a8f840) at /build/buildd/glib2.0-2.42.0/./gio/gfile.c:546
 sparql_files_compose_query (files=<optimized out>, n_files=1227) at tracker-file-notifier.c:770
 sparql_files_query_start (n_files=<optimized out>, files=<optimized out>, notifier=0x117d8f0) at tracker-file-notifier.c:789
 crawler_finished_cb (crawler=<optimized out>, was_interrupted=<optimized out>, user_data=0x117d8f0) at tracker-file-notifier.c:879
Title: tracker-miner-fs crashed with SIGSEGV in g_type_check_instance_is_a()
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
In , Pedro (pedro-redhat-bugs) wrote :

Version-Release number of selected component:
tracker-1.0.1-2.fc21

Additional info:
reporter: libreport-2.2.2
backtrace_rating: 4
cmdline: /usr/libexec/tracker-miner-fs
crash_function: g_type_check_instance_is_a
executable: /usr/libexec/tracker-miner-fs
kernel: 3.16.0-0.rc1.git4.1.fc21.x86_64
runlevel: unknown
type: CCpp
uid: 1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 g_type_check_instance_is_a at gtype.c:3972
 #1 g_file_get_uri at gfile.c:546
 #2 sparql_files_compose_query at tracker-file-notifier.c:740
 #3 sparql_files_query_start at tracker-file-notifier.c:759
 #4 crawler_finished_cb at tracker-file-notifier.c:843
 #5 g_cclosure_marshal_VOID__BOOLEANv at gmarshal.c:188
 #6 _g_closure_invoke_va at gclosure.c:831
 #9 process_func at tracker-crawler.c:539

Revision history for this message
In , Pedro (pedro-redhat-bugs) wrote :

Created attachment 911146
File: backtrace

Revision history for this message
In , Pedro (pedro-redhat-bugs) wrote :

Created attachment 911147
File: cgroup

Revision history for this message
In , Pedro (pedro-redhat-bugs) wrote :

Created attachment 911148
File: core_backtrace

Revision history for this message
In , Pedro (pedro-redhat-bugs) wrote :

Created attachment 911149
File: dso_list

Revision history for this message
In , Pedro (pedro-redhat-bugs) wrote :

Created attachment 911150
File: environ

Revision history for this message
In , Pedro (pedro-redhat-bugs) wrote :

Created attachment 911151
File: exploitable

Revision history for this message
In , Pedro (pedro-redhat-bugs) wrote :

Created attachment 911152
File: limits

Revision history for this message
In , Pedro (pedro-redhat-bugs) wrote :

Created attachment 911153
File: maps

Revision history for this message
In , Pedro (pedro-redhat-bugs) wrote :

Created attachment 911154
File: open_fds

Revision history for this message
In , Pedro (pedro-redhat-bugs) wrote :

Created attachment 911155
File: proc_pid_status

Revision history for this message
In , Pedro (pedro-redhat-bugs) wrote :

Created attachment 911156
File: var_log_messages

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.

Revision history for this message
In , Nils (nils-redhat-bugs) wrote :

I got this crash for the first time after updating to tracker-1.1.4-2.fc21.x86_64, right after logging in.

Revision history for this message
In , Alexei (alexei-redhat-bugs) wrote :

I have this bug with tracker-1.2.2-2.fc21

Revision history for this message
In , Ankur (ankur-redhat-bugs) wrote :

Happening quite often. Reporting upstream.

Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :
Revision history for this message
Ubuntu GNOME (ug-bot) wrote :

StacktraceTop:
 ?? () at /build/buildd/glib2.0-2.40.2/./gobject/gtype.c:709 from /home/darkxst/gnome3-amd64/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 g_drive_stop (drive=0x1a8f840, flags=(unknown: 28421952), mount_operation=0x4cb, cancellable=0x117faf0, callback=0x1a89270, user_data=0xffb700) at /build/buildd/glib2.0-2.40.2/./gio/gdrive.c:853
 ?? ()
 ?? ()

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Stacktrace.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
Changed in tracker:
importance: Unknown → High
status: Unknown → New
Revision history for this message
LuoZheng (htfy96) wrote :

It's the same with my UBUNTU Gnome 14.10

Changed in tracker:
status: New → Invalid
Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

tracker-1.2.4-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/tracker-1.2.4-1.fc21

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Package tracker-1.2.4-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tracker-1.2.4-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-14449/tracker-1.2.4-1.fc21
then log in and leave karma (feedback).

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

tracker-1.2.4-2.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/tracker-1.2.4-2.fc21

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

This bug is fixed in tracker 1.2.4, so could you please update the package ?

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

tracker-1.2.4-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

Updated to 1.2.4. Issue still present.

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

This bug pops up randomly with logins after the computer is locked for more than 30min.

Revision history for this message
gronki (gronki) wrote :

Affects me in Ubuntu 14.04 .2 with GNOME.

LuoZheng (htfy96)
Changed in ubuntu-gnome:
status: New → Confirmed
Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :

I am closing this bug because I never saw it again in more recent tracker versions (1.5 and 1.6).

Changed in ubuntu-gnome:
status: Confirmed → Fix Released
Revision history for this message
HC (as1566436) wrote :

This is a bug I have since Ubuntu 12.04 LTS !!
It happens in my laptop, and my 2 PCS !
Now in version 14.04.3 Xubuntu is happen agai and again !

Revision history for this message
Tomas (sheirys2) wrote :

Every time i reboot, and login i get this error. ubuntu-gnome 14.04

Changed in fedora:
importance: Unknown → Undecided
status: Unknown → Fix Released
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.