GNOME Bugzilla – Bug 666284
empathy crashed with SIGSEGV in child_setup()
Last modified: 2012-01-05 17:07:17 UTC
Originally reported at: https://bugs.launchpad.net/bugs/902430 When I started Empathy from the messaging menu, it appeared to connect to my Gmail account just fine although it also displayed a connection error at the top of my contacts list. This crash occurred when I tried clicking the offered Edit button for the connection. As far as I can tell, Empathy is continuing to operate normally after the crash. I did not get a similar message regarding my Yahoo! account, and I haven't had this problem occur until just now. 4 duplicates at downstream and may be more these for are by the bot ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: empathy 3.3.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-2.6-generic 3.2.0-rc3 Uname: Linux 3.2.0-2-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Sat Dec 10 00:32:05 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1) ProcCmdline: empathy ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f3ce25216ab: mov %r9b,(%rax) PC (0x7f3ce25216ab) ok source "%r9b" ok destination "(%rax)" (0x7f3ce1b46e40) in non-writable VMA region: 0x7f3ce1b3c000-0x7f3ce1c2b000 r-xp /lib/x86_64-linux-gnu/libglib-2.0.so.0.3102.0 SegvReason: writing VMA /lib/x86_64-linux-gnu/libglib-2.0.so.0.3102.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-07 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Didn't you already file this bug? I'm sure I already saw this trace.
no i didn't filed i just show you the down stream.
*** This bug has been marked as a duplicate of bug 667279 ***