empathy crashed with SIGSEGV in child_setup()

Bug #902430 reported by Christopher Kyle Horton
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Empathy
New
Medium
empathy (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

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.

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

Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 child_setup (user_data=0x7fff40b3f2f0) at /build/buildd/glib2.0-2.31.2/./gio/gdesktopappinfo.c:1150
 do_exec (child_err_report_fd=20, stdin_fd=-1, stdout_fd=-1, stderr_fd=-1, working_directory=<optimized out>, argv=0x1bca9a0, envp=0x1a8b670, close_descriptors=1, search_path=1, stdout_to_null=0, stderr_to_null=0, child_inherits_stdin=0, file_and_argv_zero=0, child_setup=0x7f3ce2521620 <child_setup>, user_data=0x7fff40b3f2f0) at /build/buildd/glib2.0-2.31.2/./glib/gspawn.c:1129
 fork_exec_with_pipes (intermediate_child=1, working_directory=0x0, argv=0x1bca9a0, envp=0x1a8b670, close_descriptors=1, search_path=1, stdout_to_null=0, stderr_to_null=0, child_inherits_stdin=0, file_and_argv_zero=0, child_setup=0x7f3ce2521620 <child_setup>, user_data=0x7fff40b3f2f0, child_pid=0x7fff40b3f31c, standard_input=0x0, standard_output=0x0, standard_error=0x0, error=0x7fff40b3f3c8) at /build/buildd/glib2.0-2.31.2/./glib/gspawn.c:1324
 g_spawn_async_with_pipes (working_directory=<optimized out>, argv=<optimized out>, envp=<optimized out>, flags=<optimized out>, child_setup=<optimized out>, user_data=<optimized out>, child_pid=0x7fff40b3f31c, standard_input=0x0, standard_output=0x0, standard_error=0x0, error=0x7fff40b3f3c8) at /build/buildd/glib2.0-2.31.2/./glib/gspawn.c:653
 g_spawn_async (working_directory=<optimized out>, argv=<optimized out>, envp=<optimized out>, flags=<optimized out>, child_setup=<optimized out>, user_data=<optimized out>, child_pid=0x7fff40b3f31c, error=0x7fff40b3f3c8) at /build/buildd/glib2.0-2.31.2/./glib/gspawn.c:138

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.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_spawn_async_with_pipes()
+ empathy crashed with SIGSEGV in child_setup()
tags: removed: need-amd64-retrace
Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :

The connection error displayed again at the top of my contacts list this morning, and this time I was able to click the Edit button and noticed my gmail account had somehow gotten added twice without my knowledge. One showed the error, while the other showed me as Away. I removed the former and that might solve the issue for me...still not sure where it came from, though.

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
visibility: private → public
Revision history for this message
Bilal Shahid (s9iper1) wrote :

thanks for the bug report it looks like the accounts are crashing would be good to start manually
/usr/bin/empathy-accounts -- select-account=gabble/jabber/goa_google_account_1322816355
and get a trace from that?

Revision history for this message
Stuart Langridge (sil) wrote : Re: [Bug 902430] Re: empathy crashed with SIGSEGV in child_setup()

Running that command works fine; the accounts window from Empathy opens
correctly.

On 14/12/11 11:49, Muhammad bilal shahid wrote:
> thanks for the bug report it looks like the accounts are crashing would be good to start manually
> /usr/bin/empathy-accounts -- select-account=gabble/jabber/goa_google_account_1322816355
> and get a trace from that?
>

Revision history for this message
Bilal Shahid (s9iper1) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:https://bugzilla.gnome.org/show_bug.cgi?id=666284

Changed in empathy:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Ian Nicholson (imnichol) wrote :

Occurred when I clicked "edit" -> "accounts"

tags: added: bugpattern-needed
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.