file-roller crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()

[Cysioland]

This happened when I tried to drag an audio file from File Roller to VLC Media Player.

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
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Sep 21 21:50:39 2015
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2014-10-14 (342 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: file-roller /media/hdd/Zakamarki\ twardego\ dysku/K-On\ Music\ Collection/[Nipponsei]\ K-ON!!\ ED2\ Single\ -\ NO,\ Thank\ You!\ [Various].zip
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/usr/bin/fish
 LANGUAGE=pl_PL
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
SegvAnalysis:
 Segfault happened at: 0x43b963: mov 0x10(%rdx),%rdi
 PC (0x0043b963) ok
 source "0x10(%rdx)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__STRINGv () 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
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: file-roller crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()
UpgradeStatus: Upgraded to vivid on 2015-05-23 (121 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers 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 #1062401, 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.