file-roller crashed with SIGSEGV in g_closure_invoke()

[Phil Corbett]

File roller just suddenly crashed when opening a folder inside a zip file.

phil@ubuntu:~$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

phil@ubuntu:~$ apt-cache policy file-roller
file-roller:
  Installed: 3.4.0-0ubuntu1
  Candidate: 3.4.0-0ubuntu1
  Version table:
 *** 3.4.0-0ubuntu1 0
        500 http://gb.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

Expected: The folder to open and display the contents.
Instead: File roller crashed.

Note that it later managed to open the folder fine, so I have no idea what happened as it seems to be working fine now...

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: file-roller 3.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
Date: Fri Apr 13 13:58:01 2012
ExecutablePath: /usr/bin/file-roller
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcCmdline: file-roller /home/username/Downloads/Roboto_Hinted_20111129.zip
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8061be0: mov (%esi),%eax
 PC (0x08061be0) ok
 source "(%esi)" (0x00000043) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-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.