trackerd crashed with SIGSEGV

Bug #180220 reported by Johannes Rohr
This bug report is a duplicate of:  Bug #182712: trackerd crashed with SIGSEGV. Edit Remove
10
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Fix Committed
Medium
Unassigned

Bug Description

Binary package hint: tracker

trackerd crashed in the background, when I started evolution

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Jan 4 00:26:04 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/trackerd
NonfreeKernelModules: cdrom
Package: tracker 0.6.4-1ubuntu1
PackageArchitecture: i386
ProcCmdline: trackerd
ProcCwd: /home/jr
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: tracker
Stacktrace:
 #0 0x08071cc4 in ?? ()
 #1 0x0812a4b0 in ?? ()
 #2 0x081a9258 in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: trackerd crashed with SIGSEGV
Uname: Linux hardy 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
Johannes Rohr (jorohr) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:index_mail_messages_by_summary_file (db_con=0x812a4b0,
evolution_index_file (db_con=0x812a4b0, info=0x81a7520)
tracker_email_index_file (db_con=0x812a4b0, info=0x81a7520,
process_files_thread () at trackerd.c:909
?? () from /usr/lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in tracker:
importance: Undecided → Medium
Revision history for this message
Bigbiz (markozz) wrote :

I too, I started Evolution and trackerd cashes

Revision history for this message
Jamie McCracken (jamiemcc-blueyonder) wrote :

I believe this is fixed in 0.6.5 but am not 100% as I cant replicate bug

Please reopen if propblem persists with 0.6.5

Changed in tracker:
status: New → Fix Committed
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.