empathy crashed with SIGSEGV in g_object_notify()

Bug #1221961 reported by Eduardo de Souza Pereira
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
New
Undecided
Unassigned

Bug Description

The error occurred as soon as I open the Empathy after the operating system loads.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: empathy 3.8.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
Date: Fri Sep 6 19:45:23 2013
ExecutablePath: /usr/bin/empathy
InstallationDate: Installed on 2013-07-21 (47 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANGUAGE=pt_BR:
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f4df28d7d0b <g_object_notify+27>: cmpq $0x50,(%rax)
 PC (0x7f4df28d7d0b) ok
 source "$0x50" ok
 destination "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_object_notify () 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_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_ptr_array_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: empathy crashed with SIGSEGV in g_object_notify()
UpgradeStatus: Upgraded to saucy on 2013-07-22 (46 days ago)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo

Revision history for this message
Eduardo de Souza Pereira (eduslack) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1196528, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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