telepathy-gabble crashed with signal 5 in g_simple_async_result_complete()

Bug #867682 reported by Arun Prasad on 2011-10-04
260
This bug affects 53 people
Affects Status Importance Assigned to Milestone
telepathy-gabble
Incomplete
Critical
telepathy-gabble (Ubuntu)
Medium
Unassigned

Bug Description

empathy crashed once network connection went down

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: telepathy-gabble 0.13.5-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Tue Oct 4 22:18:37 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/telepathy-gabble
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111001)
ProcCmdline: /usr/lib/telepathy/telepathy-gabble
Signal: 5
SourcePackage: telepathy-gabble
StacktraceTop:
 ?? ()
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: telepathy-gabble crashed with signal 5 in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Arun Prasad (arunshankerprasad) wrote :

StacktraceTop:
 close_sent_cb (source=0xfef160, res=0x12c1920, user_data=<optimized out>) at wocky-c2s-porter.c:1377
 g_simple_async_result_complete (simple=0x12c1920) at /build/buildd/glib2.0-2.30.0/./gio/gsimpleasyncresult.c:749
 wocky_xmpp_connection_write_cb (source=0xa1a900, res=0x12c18c0, user_data=<optimized out>) at wocky-xmpp-connection.c:338
 async_ready_callback_wrapper (source_object=<optimized out>, res=0x12c18c0, user_data=0xfef160) at /build/buildd/glib2.0-2.30.0/./gio/goutputstream.c:592
 g_simple_async_result_complete (simple=0x12c18c0) at /build/buildd/glib2.0-2.30.0/./gio/gsimpleasyncresult.c:749

Changed in telepathy-gabble (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in telepathy-gabble (Ubuntu):
status: New → Confirmed
Bilal Shahid (s9iper1) wrote :

any body can provide the steps to reproduce it ?
i guess stacktrace has enough info for developers. but i need somebody who can upstream it or answer it at upstream..

visibility: private → public
JG (jdogzz-g5) wrote :

When it happened to me, it was several minutes after a system resume.

iMac (imac-netstatz) wrote :

In my case, 12.04, current beta, upon suspend resume 0.16.0-0ubuntu1

Andrew Austin (andrewaclt) wrote :

Occurred to me on 12.04 beta2 after network connection went down.

Fahmy (fahmi) wrote :

Occured to me when resume...using Ubuntu 12.04 Beta

Jiri Vaclavovic (jvaclavovic) wrote :

12.04, 64bit, occured usualy several seconds after system resume (ThinkPad 420)

Bilal Shahid (s9iper1) wrote :

filing the bug in upstream you people just subscribe to that one bug.

empathy crashed once network connection went down

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: telepathy-gabble 0.13.5-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
people also having this bug in ubuntu 12.04
with 0.16 version of telepathy gabble in precise ubuntu

Download full text (7.2 KiB)

#0 g_logv (log_domain=0x7f15362dd561 "GLib-GIO", log_level=<optimized out>, format=0x7f153570f712 "%s: assertion `%s' failed", args1=0x7fff91fbc2c8) at /build/buildd/glib2.0-2.30.0/./glib/gmessages.c:577
        depth = 0
        domain = 0x0
        data = 0x0
        log_func = 0x432030 <log_handler>
        domain_fatal_mask = <optimized out>
        masquerade_fatal = <optimized out>
        test_level = <optimized out>
        was_fatal = 0
        was_recursion = 0
        i = <optimized out>
#1 0x00007f15356ca6a2 in g_log (log_domain=<optimized out>, log_level=<optimized out>, format=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gmessages.c:591
        args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7fff91fbc3a0, reg_save_area = 0x7fff91fbc2e0}}
#2 0x000000000045753a in close_sent_cb (source=0xfef160, res=0x12c1920, user_data=<optimized out>) at wocky-c2s-porter.c:1377
        self = 0xff6950
        priv = 0xff6970
        error = 0x9bd0c0
#3 0x00007f1536261c17 in g_simple_async_result_complete (simple=0x12c1920) at /build/buildd/glib2.0-2.30.0/./gio/gsimpleasyncresult.c:749
        current_source = 0x0
        current_context = 0x0
        __PRETTY_FUNCTION__ = "g_simple_async_result_complete"
#4 0x0000000000453f1e in wocky_xmpp_connection_write_cb (source=0xa1a900, res=0x12c18c0, user_data=<optimized out>) at wocky-xmpp-connection.c:338
        r = 0x12c1920
        self = <optimized out>
        priv = 0xfef180
        written = <optimized out>
        error = 0x9bd140
#5 0x00007f153625d679 in async_ready_callback_wrapper (source_object=<optimized out>, res=0x12c18c0, user_data=0xfef160) at /build/buildd/glib2.0-2.30.0/./gio/goutputstream.c:592
        stream = 0xa1a900
#6 0x00007f1536261c17 in g_simple_async_result_complete (simple=0x12c18c0) at /build/buildd/glib2.0-2.30.0/./gio/gsimpleasyncresult.c:749
        current_source = 0x0
        current_context = 0x0
        __PRETTY_FUNCTION__ = "g_simple_async_result_complete"
#7 0x00000000004cb946 in wocky_tls_job_result_gssize (job=<optimized out>, result=-10) at wocky-tls.c:378
        simple = 0x12c18c0
#8 0x00007f153625d469 in g_output_stream_write_async (stream=0xa1a900, buffer=0x510c6c, count=17, io_priority=0, cancellable=0x0, callback=0x453e70 <wocky_xmpp_connection_write_cb>, user_data=0xfef160) at /build/buildd/glib2.0-2.30.0/./gio/goutputstream.c:768
        class = 0x7f152c009200
        simple = <optimized out>
        error = 0x0
        __PRETTY_FUNCTION__ = "g_output_stream_write_async"
#9 0x0000000000453724 in wocky_xmpp_connection_do_write (self=0xfef160) at wocky-xmpp-connection.c:352
        priv = 0xfef180
        output = <optimized out>
#10 0x0000000000456cb4 in send_close (self=0xff6950) at wocky-c2s-porter.c:1405
        priv = 0xff6970
#11 close_if_waiting (self=0xff6950) at wocky-c2s-porter.c:667
No locals.
#12 close_if_waiting (self=0xff6950) at wocky-c2s-porter.c:659
        priv = <optimized out>
#13 0x0000000000457454 in send_stanza_cb (source=0xfef160, res=<optimized out>, user_data=<optimized out>) at wocky-c2s-porter.c:709
        self = 0xff6950
        priv = 0xff6970
        error = 0x9bd120
#14 0x00007f1536261c...

Read more...

Changed in telepathy-gabble (Ubuntu):
status: Confirmed → Incomplete
status: Incomplete → Confirmed
status: Confirmed → Triaged
Changed in telepathy-gabble:
importance: Unknown → Critical
status: Unknown → Confirmed

I don't get this. The line where an assertion is clearly not satisfied is wocky-c2s-porter.c:1377. Yet, in gabble 0.13.5 this is the line:

1374 if (!wocky_xmpp_connection_send_close_finish (WOCKY_XMPP_CONNECTION (source),
1375 res, &error))
1376 {
1377 g_simple_async_result_set_from_error (priv->close_result, error);
1378 g_error_free (error);
1379
1380 goto out;
1381 }

So g_simple_async_result_set_from_error, but that's a real symbol (not inline or a macro) and we don't get a frame for g_simple_async_result_set_from_error in the backtrace so it seems to be failing in close_sent_cb?

However, there's no typecheck there? so I don't understand what's actually failing here. If we could see what assertion is actually being logged failing that would be useful. Perhaps look in xsession-errors?

Changed in telepathy-gabble:
status: Confirmed → Incomplete
tags: added: precise

quantal added

tags: added: quantal
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.