emacs24-x crashed with SIGSEGV in g_closure_invoke()

[Anders Kaseorg]

This seems to happen pretty often during apt upgrades.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: emacs24 24.2+1-1ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.8-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Jan 14 20:19:07 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/emacs24-x
InstallationDate: Installed on 2010-12-05 (771 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
MarkForUpload: True
ProcCmdline: emacs --daemon
Signal: 11
SourcePackage: emacs24
StacktraceTop:
 ?? ()
 g_closure_invoke (closure=0x240af40, return_value=0x0, n_param_values=2, param_values=0x7fff004cc230, invocation_hint=0x7fff004cc1d0) at /build/buildd/glib2.0-2.34.3/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x227c6a0, detail=detail@entry=102, instance=instance@entry=0x103bc00, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff004cc230) at /build/buildd/glib2.0-2.34.3/./gobject/gsignal.c:3551
 g_signal_emit_valist (instance=0x103bc00, signal_id=<optimized out>, detail=102, var_args=var_args@entry=0x7fff004cc488) at /build/buildd/glib2.0-2.34.3/./gobject/gsignal.c:3300
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.34.3/./gobject/gsignal.c:3356
Title: emacs24-x crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to raring on 2012-11-15 (60 days ago)
UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare sudo wireshark

[Apport retracing service (apport)]

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 #1028286, 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.