empathy crashed with SIGSEGV in listing_failed_cb()

Bug #1138829 reported by Nathan Williams
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Empathy
Fix Released
Critical
empathy (Ubuntu)
Medium
Unassigned

Bug Description

happened after setting status to offline

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: empathy 3.6.3-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.9-0ubuntu2
Architecture: amd64
Date: Fri Mar 1 16:05:14 2013
ExecutablePath: /usr/bin/empathy
InstallationDate: Installed on 2013-03-01 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130227.1)
MarkForUpload: True
ProcCmdline: empathy
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x425309: mov 0x80(%rdx),%rdi
 PC (0x00425309) ok
 source "0x80(%rdx)" (0xaaaaaaaaaaaaab2a) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__BOXEDv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXEDv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Nathan Williams (nathwill-deactivatedaccount-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 listing_failed_cb (room_list=<optimized out>, error=<optimized out>, self=0x2d74510) at empathy-new-chatroom-dialog.c:409
 g_cclosure_marshal_VOID__BOXEDv (closure=0x29029e0, return_value=<optimized out>, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x2c9cbb0) at /build/buildd/glib2.0-2.35.8/./gobject/gmarshal.c:1160
 _g_closure_invoke_va (closure=0x29029e0, return_value=0x0, instance=0x2ba7ad0, args=0x7fff318538c8, n_params=1, param_types=0x2c9cbb0) at /build/buildd/glib2.0-2.35.8/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=0x2ba7ad0, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fff318538c8) at /build/buildd/glib2.0-2.35.8/./gobject/gsignal.c:3225
 g_signal_emit (instance=instance@entry=0x2ba7ad0, signal_id=<optimized out>, detail=detail@entry=0) at /build/buildd/glib2.0-2.35.8/./gobject/gsignal.c:3370

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in empathy (Ubuntu):
importance: Undecided → Medium
summary: - empathy crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXEDv()
+ empathy crashed with SIGSEGV in listing_failed_cb()
tags: removed: need-amd64-retrace
Revision history for this message
Bilal Shahid (s9iper1) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in empathy (Ubuntu):
status: New → Incomplete
information type: Private → Public
Revision history for this message
Bilal Shahid (s9iper1) wrote :

upstreamed

Changed in empathy (Ubuntu):
status: Incomplete → New
status: New → Triaged
Changed in empathy:
importance: Unknown → Critical
status: Unknown → New
Changed in empathy:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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