telepathy-indicator crashed with SIGSEGV in g_simple_async_result_complete()

Bug #796661 reported by Cristian Aravena Romero
472
This bug affects 109 people
Affects Status Importance Assigned to Milestone
Telepathy Indicator
Fix Released
Undecided
Unassigned
telepathy-indicator (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Binary package hint: telepathy-indicator

Close windows of chat and open apport.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: telepathy-indicator 0.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-0.1-generic 3.0.0-rc2
Uname: Linux 3.0-0-generic x86_64
Architecture: amd64
Date: Mon Jun 13 11:29:17 2011
ExecutablePath: /usr/bin/telepathy-indicator
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: telepathy-indicator
ProcEnviron:
 LANGUAGE=es_ES:en
 PATH=(custom, no user)
 LANG=es_ES.utf8
 LC_MESSAGES=es_ES.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff188289386 <_IO_vfprintf_internal+7126>: repnz scas %es:(%rdi),%al
 PC (0x7ff188289386) 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=0x22c3ea0) at /build/buildd/glib2.0-2.29.6/./gio/gsimpleasyncresult.c:749
 handle_with_cb (self=<value optimized out>, error=0x22c8540, user_data=0x22c3ea0, weak_object=<value optimized out>) at channel-dispatch-operation.c:1091
 tp_cli_channel_dispatch_operation_call_handle_with_time (proxy=0x22b88d0, timeout_ms=-1, in_Handler=0x7ff189407975 "", in_UserActionTime=212988, callback=0x7ff18933f470 <handle_with_cb>, user_data=0x22c3ea0, destroy=0, weak_object=0x22b88d0) at ../telepathy-glib/_gen/tp-cli-channel-dispatch-operation-body.h:402
 tp_channel_dispatch_operation_handle_with_time_async (self=0x22b88d0, handler=<value optimized out>, user_action_time=212988, callback=<value optimized out>, user_data=0x7ff180008d80) at channel-dispatch-operation.c:1357
Title: telepathy-indicator crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _IO_vfprintf_internal (s=<value optimized out>, format=<value optimized out>, ap=<value optimized out>) at vfprintf.c:1620
 __vasprintf_chk (result_ptr=0x7fff9e2f8868, flags=1, format=0x402198 "Failed to handle operations: %s\n", args=0x7fff9e2f88d8) at vasprintf_chk.c:68
 g_vasprintf (string=0x7fff9e2f8868, format=0x4021b6 "s\n", args=0x20) at /build/buildd/glib2.0-2.29.8/./glib/gprintf.c:316
 g_strdup_printf (format=0x10538b4826740858 <Address 0x10538b4826740858 out of bounds>) at /build/buildd/glib2.0-2.29.8/./glib/gstrfuncs.c:274
 ?? ()

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
visibility: private → public
Changed in telepathy-indicator (Ubuntu):
status: New → Confirmed
Changed in telepathy-indicator:
status: New → Fix Committed
milestone: none → 0.0.5
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package telepathy-indicator - 0.0.5-0ubuntu1

---------------
telepathy-indicator (0.0.5-0ubuntu1) oneiric; urgency=low

  * New upstream release.
    - display the avatar in the messaging menu (LP: #837472)
    - Make sure we are cleaning up all occurances of GError and use
      GDesktopAppInfo instead of GAppInfo (LP: #796661) (LP: #825948)
    - Make sure GError gets freed (LP: #824207)
  * debian/control
    - Added build depends on libindicate-gtk-dev
 -- Ken VanDine <email address hidden> Fri, 02 Sep 2011 10:33:38 -0400

Changed in telepathy-indicator (Ubuntu):
status: Confirmed → Fix Released
Changed in telepathy-indicator:
status: Fix Committed → Fix Released
Revision history for this message
Ari Torres (kuvanito) wrote :

i removed empathy and still gives me errors,i hate this crap!
sudo apt-get remove empathy*
sudo apt-get purge empathy*
sudo apt-get autoremove
sudo apt-get autoclean

Revision history for this message
Laura Czajkowski (czajkowski) wrote :

Just upgraded from 12.04 to 12.10, launched the desktop after reboot and it crashed generated this crash report

Changed in telepathy-indicator (Ubuntu):
status: Fix Released → Confirmed
importance: Medium → High
tags: added: quantal regression-release
Revision history for this message
Tomasz Konefal (twkonefal-j) wrote :

I just upgraded from 12.04 to 12.10, too. Same result as Laura.

Revision history for this message
Robert Bruce Park (robru) wrote :

Just got this one on 12.10 today as well.

Revision history for this message
Andrew Stothard (9-andys) wrote :

I just got this on 12.10.

I'd just uninstalled empathy, installed pidgin and rebooted.

Revision history for this message
Andrew Stothard (9-andys) wrote :

I tried to restart telepathy-indicator from a terminal and got the following:
--------------------------------------------------------------------------------------------------------------------
** (telepathy-indicator:3497): WARNING **: could not find the desktop file for 'empathy.desktop'

** (telepathy-indicator:3497): CRITICAL **: messaging_menu_app_get_dbus_object_path: assertion `app->appinfo != NULL' failed

(telepathy-indicator:3497): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion `object_path != NULL && g_variant_is_object_path (object_path)' failed
Segmentation fault (core dumped)
---------------------------------------------------------------------------------------------------------------------

Considering I'd just removed empathy it's no surprise telepathy couldn't find the file.

Revision history for this message
Alexandre Amor (ralex32) wrote :

I noticed this issue after I'd uninstalled empathy and rebooted.

Revision history for this message
Julien-Charles Lévesque (jclevesque) wrote :

Same, after I uninstalled empathy and reboot.

Revision history for this message
Ian Ross (iankross) wrote :

12.10
Just started machine up and was check t'bird for mail and got the popup advising of problem.
Yesterday Pidgin would start but if if tried to start a conversation it would crash. I also tried Empathy and it sort of worked. Very slow signing on to accounts. Google accounts were the worst to get hooked up.
The OS was updated late yesterday and last night Pidgin was working again. I have not tried it yet today.

Revision history for this message
Brian Neltner (neltnerb) wrote :

This bug still exists in the latest version.

For what it's worth, this is a new bug as of a few weeks ago. Before that I never saw this happen, and I did not change my configuration (i.e. I did not suddenly uninstall epiphany to find it non-functional). I uninstalled epiphany in favor of pidgin over a month ago, and it worked fine then.

Revision history for this message
Stefan Heijnen (stfn) wrote :

Also got this after upgrading from 12.04 to 12.10 beta 2 and removing Empathy.

Revision history for this message
Tomas Hayes (tomyo) wrote :

This happend after I removed Empathy and installed Pidgin. The integration with the notification applet for Social Networks it's broken for pidgin as well, only gwibber showing.

Revision history for this message
Tomas Hayes (tomyo) wrote :

(updated from 12.04 to 12.10)

Revision history for this message
Brian Neltner (neltnerb) wrote :

Still present in 12.10's most recent update.

Revision history for this message
Simplehuman (simplehuman) wrote :

I have it also on 12.10 after booting.

Revision history for this message
Andrew Gunnerson (cxl) wrote :

I'm not sure if it's related, but Thunderbird is crashing with the same error for me: http://pastie.org/4900282

Revision history for this message
Andrew Gunnerson (cxl) wrote :

Indicator messages 12.10.4-0ubuntu1 seems to fix this :)

Revision history for this message
Pavel P. (zarjart) wrote :

I am using Ubuntu 12.10 beta 2 and I can confirm #17 - crash as described above, no notification area integration.

Beth Holt (nbethholt)
information type: Public → Private Security
information type: Private Security → Public
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.