file-roller crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()

Bug #1434730 reported by Kari Pietarinen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu 15.04
File roller (archieve manager) crashed during unpacking and exit. Unpacking was succesfull.

file-roller 3.14.2, Copyright © 2001-2012 Free Software Foundation, Inc.

Linux Newton 3.19.0-9-generic #9-Ubuntu SMP Wed Mar 11 17:50:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: file-roller 3.14.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 20 23:57:47 2015
ExecutablePath: /usr/bin/file-roller
ProcCmdline: file-roller --extract-here file:///mnt02/Downloads/Bullhead-2011-720p/rundskop.(2011).eng.1cd.(4441114).zip
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: No upgrade log present (probably fresh install)
UserGroups: multimedia sudo

Revision history for this message
Kari Pietarinen (kej-pietarinen) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.