telepathy-gabble crashed with SIGSEGV in stun_server_resolved_cb()

Bug #1237191 reported by Terry on 2013-10-09
88
This bug affects 10 people
Affects Status Importance Assigned to Milestone
telepathy-gabble
Fix Released
Medium
telepathy-gabble (Ubuntu)
High
Unassigned
Trusty
Undecided
Unassigned

Bug Description

* Impact
telepathy-gabble segfaults sometimes

* Test case
no specific testcase, watch reports on https://errors.ubuntu.com/problem/93026bff3a7b3efe53da33fcbdc6c6cb5c8282f3

* Regression potential
check that jabber keeps working fine with telepathy (change should be safe, it's just handling of a null case)

Terry (terry-burgess) wrote :

StacktraceTop:
 stun_server_resolved_cb (resolver=0x1296310, result=0x15aab60, user_data=0x18f4ce0) at wocky-jingle-info.c:277
 g_task_return_now (task=0x15aab60) at /build/buildd/glib2.0-2.38.0/./gio/gtask.c:1108
 g_task_return (task=0x15aab60, type=<optimized out>) at /build/buildd/glib2.0-2.38.0/./gio/gtask.c:1161
 _g_closure_invoke_va (closure=0x12ac070, return_value=0x0, instance=0x7f25c00079a0, args=0x7fffee1f2f48, n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.38.0/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=0x7f25c00079a0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fffee1f2f48) at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c:3238

Changed in telepathy-gabble (Ubuntu):
importance: Undecided → Medium
summary: - telepathy-gabble crashed with SIGSEGV in g_signal_emit_valist()
+ telepathy-gabble crashed with SIGSEGV in stun_server_resolved_cb()
tags: removed: need-amd64-retrace
tags: added: trusty
Launchpad Janitor (janitor) wrote :

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

Changed in telepathy-gabble (Ubuntu):
status: New → Confirmed
Download full text (13.1 KiB)

The bug has been reported on https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/1237191

The reports seem to have started with 0.18 in raring

Backtrace of the issue

"#0 stun_server_resolved_cb (resolver=0x1296310, result=0x15aab60, user_data=0x18f4ce0) at wocky-jingle-info.c:277
        data = 0x18f4ce0
        self = 0x0
        priv = <optimized out>
        e = 0x0
        address = <optimized out>
        entries = <optimized out>
        __func__ = "stun_server_resolved_cb"
#1 0x00007f25c98dae3b in g_task_return_now (task=0x15aab60) at /build/buildd/glib2.0-2.38.0/./gio/gtask.c:1108
No locals.
#2 0x00007f25c98db4a6 in g_task_return (task=0x15aab60, type=<optimized out>) at /build/buildd/glib2.0-2.38.0/./gio/gtask.c:1161
        source = 0x126c750
        type = <optimized out>
        task = 0x15aab60
#3 0x00007f25c96203b7 in _g_closure_invoke_va (closure=0x12ac070, return_value=0x0, instance=0x7f25c00079a0, args=0x7fffee1f2f48, n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.38.0/./gobject/gclosure.c:840
        marshal = 0x7f25c9621f10 <g_cclosure_marshal_VOID__VOIDv>
        marshal_data = 0x0
        in_marshal = 0
        real_closure = 0x12ac050
        __PRETTY_FUNCTION__ = "_g_closure_invoke_va"
#4 0x00007f25c9638e82 in g_signal_emit_valist (instance=0x7f25c00079a0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fffee1f2f48) at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c:3238
        return_accu = 0x0
        accu = {g_type = 0, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}}
        accumulator = 0x0
        emission = {next = 0x0, instance = 0x7f25c00079a0, ihint = {signal_id = 47, detail = 0, run_type = G_SIGNAL_RUN_FIRST}, state = EMISSION_RUN, chain_type = 19281632}
        signal_id = 47
        instance_type = <optimized out>
        emission_return = {g_type = 0, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}}
        rtype = 4
        static_scope = 0
        fastpath_handler = <optimized out>
        closure = 0x12ac070
        run_type = <optimized out>
        l = <optimized out>
        fastpath = <optimized out>
        instance_and_params = <optimized out>
        signal_return_type = <optimized out>
        param_values = <optimized out>
        i = <optimized out>
        n_params = <optimized out>
        __PRETTY_FUNCTION__ = "g_signal_emit_valist"
        __FUNCTION__ = "g_signal_emit_valist"
#5 0x00007f25c9639ae2 in g_signal_emit (instance=instance@entry=0x7f25c00079a0, signal_id=<optimized out>, detail=detail@entry=0) at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c:3386
        var_args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7fffee1f3020, reg_save_area = 0x7fffee1f2f60}}
#6 0x00007f25c98975f5 in g_cancellable_cancel (cancellable=0x7f25c...

Changed in telepathy-gabble (Ubuntu):
importance: Medium → High
information type: Private → Public
Changed in telepathy-gabble (Ubuntu):
status: Confirmed → Triaged
Changed in telepathy-gabble:
importance: Unknown → Medium
status: Unknown → Confirmed

Created attachment 98618
wocky-jingle-info: don't try using self if it's NULL

Fixed for 0.18.2 and 0.19.0 (which may actually be 1.0).

(In reply to comment #2)
> Fixed for 0.18.2 and 0.19.0 (which may actually be 1.0).

And I just released 0.18.3

Changed in telepathy-gabble:
status: Confirmed → Fix Released
Changed in telepathy-gabble (Ubuntu):
status: Triaged → Fix Committed
description: updated
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package telepathy-gabble - 0.18.3-0ubuntu1

---------------
telepathy-gabble (0.18.3-0ubuntu1) utopic; urgency=medium

  * New upstream version, don't segfault in stun_server_resolved_cb
    (lp: #1237191)
 -- Sebastien Bacher <email address hidden> Wed, 04 Jun 2014 11:45:17 +0200

Changed in telepathy-gabble (Ubuntu):
status: Fix Committed → Fix Released

Hello Terry, or anyone else affected,

Accepted telepathy-gabble into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/telepathy-gabble/0.18.3-0ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
Changed in telepathy-gabble (Ubuntu Trusty):
status: New → Fix Committed
Chris Halse Rogers (raof) wrote :

Just to note - pulling in a new upstream version turned a 5 line diff into a > 10K line diff. Grrr.

Sebastien Bacher (seb128) wrote :

@Chris: sorry about that :/

Changing to verification-done, the new version works correctly and e.u.c has no report with it

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package telepathy-gabble - 0.18.3-0ubuntu0.1

---------------
telepathy-gabble (0.18.3-0ubuntu0.1) trusty; urgency=medium

  * New upstream version, don't segfault in stun_server_resolved_cb
    (lp: #1237191)
 -- Sebastien Bacher <email address hidden> Wed, 04 Jun 2014 11:45:17 +0200

Changed in telepathy-gabble (Ubuntu Trusty):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for telepathy-gabble has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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.