springlobby crashed with SIGSEGV in g_main_context_dispatch()

[Guybrush88]

I got this crash while searching a random string using the "Search for maps and games" window from the "Downloads" tab. It's very likely to be related to this: https://bugs.launchpad.net/ubuntu/+source/springlobby/+bug/1440342

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: springlobby 0.210-2
ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
Uname: Linux 3.19.0-20-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 10 23:20:53 2015
ExecutablePath: /usr/games/springlobby
InstallationDate: Installed on 2014-10-16 (237 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
LocalLibraries: /home/davide/.spring/engine/98.0/libunitsync.so
ProcCmdline: springlobby
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=it_IT.UTF-8
 LANGUAGE=it_IT
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f878b67ccb9: cmpb $0x48,(%rax)
 PC (0x7f878b67ccb9) ok
 source "$0x48" ok
 destination "(%rax)" (0x00000002) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: springlobby
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: springlobby crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to vivid on 2015-04-25 (46 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for libalure1
no debug symbol package found for libk5crypto3
no debug symbol package found for libkrb5-3
no debug symbol package found for libharfbuzz0b
no debug symbol package found for libflac8
no debug symbol package found for librtmp1
no debug symbol package found for libthai0
no debug symbol package found for libstdc++6
no debug symbol package found for libuuid1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!