empathy-auth-client crashed with SIGSEGV in g_value_array_free()

Bug #808645 reported by Chad A Davis
This bug report is a duplicate of:  Edit Remove
114
This bug affects 2 people
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Release of Ubuntu: Ubuntu oneiric (development branch)
Package Version: 3.1.3-1ubuntu1
Expected Results: Delete an IRC account (after disconnecting it)
Actual Results: Account was deleted, then empathy-auth-client crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: empathy 3.1.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Mon Jul 11 09:23:57 2011
ExecutablePath: /usr/lib/empathy/empathy-auth-client
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110622)
ProcCmdline: /usr/lib/empathy/empathy-auth-client
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7ff2a012cb42 <g_value_array_free+50>: cmpq $0x0,(%rdi)
 PC (0x7ff2a012cb42) ok
 source "$0x0" ok
 destination "(%rdi)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_value_array_free () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
 g_closure_invoke () 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
Title: empathy-auth-client crashed with SIGSEGV in g_value_array_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Chad A Davis (chadadavis) wrote :
visibility: private → public
visibility: public → private
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in empathy (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Bilal Shahid (s9iper1)
visibility: private → public
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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #804574, 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.

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.