trackerd crashed with SIGSEGV in index_mail_messages_by_summary_file

[Michael Brunton-Spall]

Binary package hint: tracker

Ubuntu Hardy Heron - Updated as of 17 March 12:00

Automatic bug reporting tool, I ahve no idea what happened, it just popped up that trackerd had crashed

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Mar 17 13:15:47 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/trackerd
Package: tracker 0.6.6-0ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/bin/trackerd
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: tracker
Stacktrace:
 #0 0x08072e14 in ?? ()
 #1 0x08163d08 in ?? ()
 #2 0x0840d9f8 in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: trackerd crashed with SIGSEGV
Uname: Linux 2.6.24-12-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:index_mail_messages_by_summary_file (db_con=0x8163d08, mail_type=<value optimized out>,
evolution_index_file (db_con=0x8163d08, info=0x8231d70) at tracker-email-evolution.c:459
tracker_email_index_file (db_con=0x8163d08, info=0x8231d70,
process_files_thread () at trackerd.c:963
?? () from /usr/lib/libglib-2.0.so.0

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 or 9.04?

[Brian J. Murrell (brian-interlinx)]

On Wed, 2008-12-03 at 06:29 +0000, Daniel T Chen wrote:
> Is this symptom still reproducible in 8.10 or 9.04?

I would not know about 9.04. That's not a final release. That's not to
say that I don't run the development releases, but I jumped into
Intrepid before it was done and have been regretting it ever since so
I'm not so eager to jump into Jaunty.

TBH I don't really use tracker. I use beagle instead. Not even sure
how I registered a crash of tracker.

b.

[Jonathan Thomas (echidnaman)]

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!