file-roller crashed with SIGSEGV

Bug #1440063 reported by LAZA on 2015-04-03
This bug report is a duplicate of:  Bug #1101096: file-roller crashed with SIGSEGV. Edit Remove
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)

Bug Description

File-Roller crashed while extracting a *.rar file - rar/unrar was not installed.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: file-roller 3.14.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Apr 3 15:22:42 2015
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2015-03-29 (5 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
ProcCmdline: file-roller --extract-to=/home/username/Downloads/Mule --extract-here --force /home/username/Downloads/Mule/Finanztest\ 04-2015.rar
 Segfault happened at: 0x41f3d0: mov 0x18(%rdi),%rax
 PC (0x0041f3d0) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: file-roller crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

LAZA (laza74) wrote :

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 #1101096, 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  Edit
Everyone can see this information.

Other bug subscribers