empathy crashed with SIGSEGV in new_chatroom_dialog_model_selection_changed()

Bug #1108604 reported by shankao
34
This bug affects 3 people
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Happened while asking for chat rooms on freenode

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: empathy 3.6.3-0ubuntu2
Uname: Linux 3.7.0-030700-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Tue Jan 29 14:42:59 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/empathy
InstallationDate: Installed on 2012-11-25 (65 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
MarkForUpload: True
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_SG:en
 LANG=en_SG.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fdefe7590ba: movdqa (%rdi),%xmm0
 PC (0x7fdefe7590ba) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? () 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_signal_emit_valist()
UpgradeStatus: Upgraded to raring on 2012-11-25 (65 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
shankao (shankao) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 new_chatroom_dialog_model_selection_changed (selection=<optimized out>, self=0x316a080) at empathy-new-chatroom-dialog.c:238
 _g_closure_invoke_va (closure=0x16d8420, return_value=0x0, instance=0x1ed3050, args=0x7fffbd4c6198, n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.35.4/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=0x1ed3050, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fffbd4c6198) at /build/buildd/glib2.0-2.35.4/./gobject/gsignal.c:3225
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=detail@entry=0) at /build/buildd/glib2.0-2.35.4/./gobject/gsignal.c:3370
 _gtk_tree_selection_internal_select_node (selection=<optimized out>, node=<optimized out>, tree=<optimized out>, path=path@entry=0x4419ca0, mode=<optimized out>, override_browse_mode=override_browse_mode@entry=0) at /build/buildd/gtk+3.0-3.6.4/./gtk/gtktreeselection.c:1604

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_signal_emit_valist()
+ empathy crashed with SIGSEGV in
+ new_chatroom_dialog_model_selection_changed()
tags: removed: need-amd64-retrace
Revision history for this message
Bilal Shahid (s9iper1) wrote :

thanks for taking time in filing the bug to make ubuntu better
can you reproduce it ?
if so than define the steps tp reproduce it?

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

You need to have the IRC plugin installed.

Asked for the roomlist for freenode and navigated around the list a bit, click on one of the rooms, navigate again... nothing unusual.

I get this in dmesg too:

[11049.351428] empathy[4474]: segfault at 0 ip 00007f47e33010ba sp 00007fff659d1968 error 4 in libc-2.17.so[7f47e3279000+1be000]

Changed in empathy (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in empathy (Ubuntu):
status: New → Confirmed
tags: added: saucy
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

Changed in empathy (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for empathy (Ubuntu) because there has been no activity for 60 days.]

Changed in empathy (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
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.