trackerd crashed with SIGSEGV

[Chris Halse Rogers]

Binary package hint: tracker

Trackerd crashed while indexing my $(HOME) for the first time.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Aug 31 09:09:21 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/trackerd
NonfreeKernelModules: nvidia
Package: tracker 0.6.1-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: trackerd
ProcCwd: /home/chris
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_AU.UTF-8
 SHELL=/bin/zsh
Signal: 11
SourcePackage: tracker
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: trackerd crashed with SIGSEGV
Uname: Linux Burninator 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm lpadmin mythtv netdev plugdev powerdev pulse-rt scanner users video

[Apport retracing service (apport)]

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

[Chris Halse Rogers (raof)]

Ok, so that backtrace is useless. I'll install some debug packages, get tracker to spew debug output, and see if I can reproduce.

[Pedro Villavicencio (pedro)]

That would be nice you can see instructions on how to get one here http://wiki.ubuntu.com/DebuggingProgramCrash . thanks in advance.

[Chris Halse Rogers (raof)]

Right. I have installed all the -dbgsym packages relating to tracker. Running trackerd under gdb results in a backtrace of 80 lots of "?? () in ??", and running valgrind on trackerd results in a SIGILL (bug 136538).

Is there anything more I can do?

[Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen)]

I can at least confirm this bug. Trackerd refuses to start: segmentation fault.
If i run trackerd --verbosity=3 i get these three lines at the very end:

...
Starting application indexing
Registering path /home/ralf/.local/share/applications as belonging to service Applications
Segmentatiefout (core dumped)
...

The last line translates to segmentation-fault. (weird to see partial translation within debug messages)

[Aurelien Naldi (aurelien.naldi)]

it may be related to bug #138399 and/or #136523

[Ralf Nieuwenhuijsen (ralf-nieuwenhuijsen)]

Thanks, Aurelien, you are right. The workaround of bug #138399 fixes the issue for me. (unsetting XDG_DATA_DIRS). Off course that's not the fix, but they claim it has been submitted.

Can the original bug-poster please check, if the following workaround makes it work:

  unset XDG_DATA_DIRS
  trackerd

If it doesn't crash, than this bug is a duplicate of bug #138399 of which the fix has been commited (though not yet in the repositories)

[Chris Halse Rogers (raof)]

Unsetting XDG_DATA_DIRS prevents a (new) segfault-on-startup. However, that is *not* bug that I filed. Now that I can get trackerd to start again, I'll see if I can reproduce my original bug with the new tracker.

[Chris Halse Rogers (raof)]

Ok. Tracker seems to have successfully indexed my emails and $HOME without segfaulting. It seems the 0.6.2 release fixed this. Marking this bug as closed. bug #138399 remains, of course!

[Pedro Villavicencio (pedro)]

Ok, thanks for let us know.