trackerd crashed with SIGSEGV in index_mail_messages_by_summary_file()

Bug #148938 reported by Ryan Zeigler
6
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: tracker

This is the output from the terminal right before trackerd crashed.

** (trackerd:16481): CRITICAL **: check_directory: assertion `tracker_is_directory (uri)' failed
ERROR: execution of prepared query CreateService failed due to constraint failed with return code 19
ERROR: CreateService uri is email://1190665330.5917.20@tassadar/INBOX;uid=16015
ERROR: failed to save email email://1190665330.5917.20@tassadar/INBOX;uid=16015
Segmentation fault (core dumped)

ProblemType: Crash
Architecture: i386
Date: Thu Oct 4 08:34:00 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/trackerd
NonfreeKernelModules: nvidia
Package: tracker 0.6.3-0ubuntu2
PackageArchitecture: i386
ProcCmdline: trackerd
ProcCwd: /home/ryan
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/ryan/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: tracker
StacktraceTop:
 index_mail_messages_by_summary_file (db_con=0x81061f0,
 evolution_index_file (db_con=0x81061f0, info=0xb4f45e68)
 tracker_email_index_file (db_con=0x81061f0,
 process_files_thread () at trackerd.c:799
 ?? () from /usr/lib/libglib-2.0.so.0
Title: trackerd crashed with SIGSEGV in index_mail_messages_by_summary_file()
Uname: Linux tassadar 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:index_mail_messages_by_summary_file (db_con=0x81061f0, mail_type=MAIL_TYPE_IMAP,
evolution_index_file (db_con=0x81061f0, info=0xb4f45e68) at tracker-email-evolution.c:464
tracker_email_index_file (db_con=0x81061f0, info=0xb4f45e68, service=0xb653df50 "EvolutionEmails")
process_files_thread () at trackerd.c:799
g_thread_create_proxy (data=0xb65006d8) at /build/buildd/glib2.0-2.14.1/glib/gthread.c:635

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
Paulo J. S. Silva (pjssilva) wrote :

I have the same problem here. Tracker never finishes to index my email and crashes always in the same message, with the following output:

ERROR: failed to save email email://1176775387.8352.20@trinity/INBOX/Antigos/2003;uid=2947
ERROR: execution of prepared query CreateService failed due to constraint failed with return code 19
ERROR: CreateService uri is email://1176775387.8352.20@trinity/INBOX/Antigos/2003;uid=2948
ERROR: failed to save email email://1176775387.8352.20@trinity/INBOX/Antigos/2003;uid=2948

(before that it prints tons of "failed to save email" messages)

Paulo

Revision history for this message
Paulo J. S. Silva (pjssilva) wrote :

I have tried tracker 0.6.4 version from Emilio Pozuelo PPA:

https://launchpad.net/~pochu/+archive

And it still crashes with the same problem.

(If I re-index all my files it crashes in a different message, but it still crashes)

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote : Re: [Bug 148938] Re: trackerd crashed with SIGSEGV in index_mail_messages_by_summary_file()

Paulo J. S. Silva wrote:
> *** This bug is a duplicate of bug 151637 ***
> https://bugs.launchpad.net/bugs/151637
>
> I have tried tracker 0.6.4 version from Emilio Pozuelo PPA:
>
> https://launchpad.net/~pochu/+archive
>
> And it still crashes with the same problem.
>
> (If I re-index all my files it crashes in a different message, but it
> still crashes)
>

Well if it's a different message it's likely a different crash. Have you looked
for it? Maybe it's been already reported.

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

not necessarily

the crash looks more subtle - maybe inavlid utf-8 - so would be random at which point it crashes

can you confirm the emails have non-ascii chars?

Revision history for this message
Paulo J. S. Silva (pjssilva) wrote :

I don't believe that in my case the crash is related to bug 151637. The emails don't have long lists of recipients as described in that bug.

I don't believe that it is a different crash either for two reasons:

1) After upgrading to 0.6.4 it crashed in exactly the same message. It only crashed in different message after I had wiped out the old indexes and started it over.

2) The new message is very close to the old one. The old one stopped in message 2948, the new one in message 2950.

As for the UTF-8 question. I am Brazilian and we speak Portuguese here. I receive many messages in UTF-8 and iso-8859-1 encodings. Message 2948 (first crash with 0.6.3 and 0.6.4 before re-indexing) had the headers:

Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

But i did not find any non-ASCII character in the message.

The message 2950 (new crash with 0.6.4 after re-indexing) is also iso-8859-1 and have special characters in the sender:

From: =?ISO-8859-1?Q?Jes=FAs_Mena?= <email address hidden>

and in the body (with headers):

Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE

If want a copy of the messages, I can send it to you. However, I would not feel comfortable with adding them to the bug report as attachments.

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Paulo J. S. Silva wrote:
> *** This bug is a duplicate of bug 151637 ***
> https://bugs.launchpad.net/bugs/151637
>
> I don't believe that in my case the crash is related to bug 151637. The
> emails don't have long lists of recipients as described in that bug.
>
> I don't believe that it is a different crash either for two reasons:
>
> 1) After upgrading to 0.6.4 it crashed in exactly the same message. It
> only crashed in different message after I had wiped out the old indexes
> and started it over.
>
> 2) The new message is very close to the old one. The old one stopped in
> message 2948, the new one in message 2950.
>
> As for the UTF-8 question. I am Brazilian and we speak Portuguese here.
> I receive many messages in UTF-8 and iso-8859-1 encodings. Message 2948
> (first crash with 0.6.3 and 0.6.4 before re-indexing) had the headers:
>
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 8bit
>
> But i did not find any non-ASCII character in the message.
>
> The message 2950 (new crash with 0.6.4 after re-indexing) is also
> iso-8859-1 and have special characters in the sender:
>
> From: =?ISO-8859-1?Q?Jes=FAs_Mena?= <email address hidden>
>
> and in the body (with headers):
>
> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
> Content-Transfer-Encoding: QUOTED-PRINTABLE
>
> If want a copy of the messages, I can send it to you. However, I would
> not feel comfortable with adding them to the bug report as attachments.
>

It has been reported as
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/182712. Let's follow up
there.

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

Paulo,
can you send suspect email files that you believe are crashing tracker to :

<email address hidden>

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.