empathy crashed with SIGSEGV in g_spawn_async_with_pipes()

Bug #904774 reported by Paulo Pernomian
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
New
Undecided
Unassigned

Bug Description

After Ubuntu upgrade, Empathy gives this error, but apparently the application is Ok. I can add some accounts and use it anyways.
The last update was done in December, 15th, 2011 14UT.
Empathy version is 3.3.1-0ubuntu2. It is running on top of Unity-2D 4.12.0-0ubuntu2.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic 3.2.0-rc5
Uname: Linux 3.2.0-4-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Thu Dec 15 12:16:47 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: empathy
SegvAnalysis:
 Segfault happened at: 0x7f5bdb258c5b: mov %r9b,(%rax)
 PC (0x7f5bdb258c5b) ok
 source "%r9b" ok
 destination "(%rax)" (0x7f5bda87b3a0) in non-writable VMA region: 0x7f5bda870000-0x7f5bda960000 r-xp /lib/x86_64-linux-gnu/libglib-2.0.so.0.3104.0
SegvReason: writing VMA /lib/x86_64-linux-gnu/libglib-2.0.so.0.3104.0
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_spawn_async_with_pipes () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_spawn_async () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: empathy crashed with SIGSEGV in g_spawn_async_with_pipes()
UpgradeStatus: Upgraded to precise on 2011-12-15 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Paulo Pernomian (paulopernomian) 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 #902430, 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.

visibility: private → public
visibility: 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.

Other bug subscribers

Remote bug watches

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