telepathy-indicator crashed with SIGSEGV in g_simple_async_result_complete()

Bug #812445 reported by Ted Gould
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
telepathy-indicator (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Clicked on a item in the messaging menu.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: telepathy-indicator 0.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Jul 18 12:49:43 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/telepathy-indicator
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: telepathy-indicator
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fea78c8c396 <_IO_vfprintf_internal+7126>: repnz scas %es:(%rdi),%al
 PC (0x7fea78c8c396) ok
 source "%es:(%rdi)" (0x10538b4826740858) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-indicator
StacktraceTop:
 ?? ()
 g_simple_async_result_complete (simple=0x7fea70002f60) at /build/buildd/glib2.0-2.29.10/./gio/gsimpleasyncresult.c:749
 ?? () from /usr/lib/libtelepathy-glib.so.0
 tp_cli_channel_dispatch_operation_call_handle_with_time () from /usr/lib/libtelepathy-glib.so.0
 tp_channel_dispatch_operation_handle_with_time_async () from /usr/lib/libtelepathy-glib.so.0
Title: telepathy-indicator crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to oneiric on 2011-06-17 (31 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare tape video

Revision history for this message
Ted Gould (ted) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_simple_async_result_complete (simple=0x7fea70002f60) at /build/buildd/glib2.0-2.29.10/./gio/gsimpleasyncresult.c:749
 tp_cli_channel_dispatcher_call_create_channel (proxy=0x10538b4826740858, timeout_ms=4202934, in_Account=0x20 <Address 0x20 out of bounds>, in_Requested_Properties=0xffffffffffffffff, in_User_Action_Time=140735513050152, in_Preferred_Handler=0x0, callback=0x22418d0, user_data=0x0, destroy=0x7fea79d425b9 <get_dispatch_operation_prop_cb+521>, weak_object=0x6030f8) at ../telepathy-glib/_gen/tp-cli-channel-dispatcher-body.h:74
 tp_cli_channel_dispatcher_call_ensure_channel (proxy=<value optimized out>, timeout_ms=35920080, in_Account=0x7fea79ccb598 "\220\310\f", in_Requested_Properties=0x223a150, in_User_Action_Time=15371896, in_Preferred_Handler=0x7fea79d40f20 "t$\030H\307D$\020@", callback=0, user_data=0x2, destroy=0, weak_object=0x2259590) at ../telepathy-glib/_gen/tp-cli-channel-dispatcher-body.h:238
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in telepathy-indicator (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in telepathy-indicator (Ubuntu):
status: New → Confirmed
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.