file-roller crashed with SIGSEGV in g_closure_invoke()

[EvilSupahFly]

Release: Ubuntu 15.04
apt-cache policy file-roller:
  Installed: 3.14.2-0ubuntu5
  Candidate: 3.14.2-0ubuntu5
  Version table:
 *** 3.14.2-0ubuntu5 0
        500 http://ca.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
        100 /var/lib/dpkg/status

I expected file-roller to unzip and standard .ZIP file downloaded from GitHub, and instead it crashed with the noted error.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: file-roller 3.14.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Sun Sep 13 08:44:21 2015
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2015-09-04 (9 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: file-roller /home/username/mcedit2-master.zip
SegvAnalysis:
 Segfault happened at: 0x419c88: mov (%rbx),%rsi
 PC (0x00419c88) ok
 source "(%rbx)" (0x0000006c) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () 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
Title: file-roller crashed with SIGSEGV in g_closure_invoke()
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 #723841, 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.