Yes, fixed - crash no-longer occurs.
--
trackerd crashed with signal 5 in pango_default_break()
https://bugs.launchpad.net/bugs/130728
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Bug was fixed in 0.6.1
** Changed in: tracker (Ubuntu)
Status: Incomplete = Fix Released
--
trackerd crashed with signal 5 in pango_default_break()
https://bugs.launchpad.net/bugs/130728
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
This should be fixed in 0.6.1 (which is now in gutsy)
can you confirm this is the case?
--
trackerd crashed with signal 5 in pango_default_break()
https://bugs.launchpad.net/bugs/130728
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem. a
valgrind log would be really helpful too please see
http://wiki.ubuntu.com/Valgrind , thanks
Valgrind output attached.
(Note: trackerd failed to terminate when valgrind issued a SIGILL. As a
result, it got stuck in a loop. It was necessary to kill -9 the
memcheck process; the log attached shows all the useful data.)
** Attachment added: Valgrind output
GDB backtrace attached.
(Note: STDOUT from trackerd process edited to remove private
information.)
** Attachment added: GDB backtrace.
http://launchpadlibrarian.net/8712664/gdb-trackerd.txt
--
trackerd crashed with signal 5 in pango_default_break()
https://bugs.launchpad.net/bugs/130728
You
It looks like invalid utf-8
what language was the email in?
GMime should always return valid utf-8 but theres a bug in it and non
utf-8 sometimes slip through
will fix at trackerd end shortly
--
trackerd crashed with signal 5 in pango_default_break()
https://bugs.launchpad.net/bugs/130728
You
