gmusicbrowser crashed with SIGSEGV in g_signal_emit_valist()

[Chris Hermansen]

Installed gmusicbrowser in 15.04 up to date as of 29 March, opened it, and closed it; while closing this happened.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: gmusicbrowser 1.1.13~ds0-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Mar 29 23:03:25 2015
ExecutablePath: /usr/bin/gmusicbrowser
InstallationDate: Installed on 2015-03-29 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150325)
InterpreterPath: /usr/bin/perl
PackageArchitecture: all
ProcCmdline: /usr/bin/perl /usr/bin/gmusicbrowser
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbe32fc6558: cmp 0x8(%rax),%rdx
 PC (0x7fbe32fc6558) ok
 source "0x8(%rax)" (0x267ec2088d) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gmusicbrowser
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gmusicbrowser crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1401609, 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.