empathy crashed with SIGSEGV in individual_view_filter_visible_func()

[Fabio Duran Verdugo]

One contact talk me and empathy crash

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: empathy 3.1.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Thu Sep 22 22:54:29 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
ProcCmdline: empathy
SegvAnalysis:
 Segfault happened at: 0x80e36e1 <individual_view_filter_visible_func+65>: mov 0x34(%eax),%edx
 PC (0x080e36e1) ok
 source "0x34(%eax)" (0xaaaaaade) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 individual_view_filter_visible_func (model=0x963c6c8, iter=0xbfa0be90, user_data=0x9736130) at empathy-individual-view.c:1788
 gtk_tree_model_filter_real_visible (filter=0x965d308, child_model=0x963c6c8, child_iter=0xbfa0be90) at /build/buildd/gtk+3.0-3.1.92/./gtk/gtktreemodelfilter.c:1260
 gtk_tree_model_filter_visible (child_iter=0xbfa0be90, self=0x965d308) at /build/buildd/gtk+3.0-3.1.92/./gtk/gtktreemodelfilter.c:1290
 gtk_tree_model_filter_row_changed (c_model=0x963c6c8, c_path=0x96b9f80, c_iter=0x96b9fa0, data=0x965d308) at /build/buildd/gtk+3.0-3.1.92/./gtk/gtktreemodelfilter.c:2041
 _gtk_marshal_VOID__BOXED_BOXED (closure=0x974cf28, return_value=0x0, n_param_values=3, param_values=0x969b2d8, invocation_hint=0xbfa0bff0, marshal_data=0x5e33810) at /build/buildd/gtk+3.0-3.1.92/./gtk/gtkmarshalers.c:1310
Title: empathy crashed with SIGSEGV in individual_view_filter_visible_func()
UpgradeStatus: Upgraded to oneiric on 2011-07-31 (53 days ago)
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #817752, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.