tracker-indexer crashed with SIGSEGV in g_closure_invoke()

[Noel J. Bergman]

Binary package hint: tracker

Reproducible. Automatically generated crash report.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/tracker/tracker-indexer
NonfreeKernelModules: nvidia
Package: tracker 0.6.92-1ubuntu1
ProcCmdline: /usr/lib/tracker/tracker-indexer
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: tracker
StacktraceTop:
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit_by_name ()
Title: tracker-indexer crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()
IA__g_closure_invoke (closure=0x15c86d0,
signal_emit_unlocked_R (node=0x15a8740, detail=0,
IA__g_signal_emit_valist (instance=0x14ad060,
IA__g_signal_emit_by_name (instance=0x14ad060,

[Tim Frost (timfrost)]

Apport has just reported an occurrence of this crash on my system. Jaunty/AMD64.
I note a duplicate entry in my full stack trace: g-closure_invoke is on stack at # 1 and #5, both at the same address.

I am uploading the apport report, and will link to this bug when it completes

[Tim Frost (timfrost)]

New bug # 356097 created by apport, which has attacghed its files to that bug. I have explicitly marked that as a duplicate of this bug.

[Tim Frost (timfrost)]

Just before tracker crashed on my sytem, I had a file system hit 99% used, as I was copying files to it from a USB stick:

tim@zaphod:~$ df -h /vol/archives/
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VG0-vg0--archives
                       99G 93G 1.4G 99% /vol/archives

I don't know if tracker is indexing that filesystem, as I haven't tuned its settings.

[Martyn Russell (martyn-lanedo)]

Tracker will stop indexing if the file system becomes too full. You can set the percentage in the config (and tracker-preferences). Usually 1% left is where it stops.

It certainly shouldn't crash.

[Laryllan (laryllan)]

Try reproduce the error:

Mount a filesystem (in my case it was a internal HDD partition) via gnome and unmount it.
Tracker crashed a few minutes after unmounting.

[Chris Coulson (chrisccoulson)]

Can you recreate this with the latest version of tracker (0.6.92-1ubuntu2)?

[José Ernesto Dávila Pantoja (josernestodavila)]

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!