file-roller crashed with SIGSEGV

Bug #1161504 reported by theghost
This bug report is a duplicate of:  Bug #1101096: file-roller crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
New
Undecided
Unassigned

Bug Description

Steps to reproduce:

1. Try to export a rar file without rar packages installed
2. Abort installation dialog with recommended rar packages

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: file-roller 3.6.3-1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
Uname: Linux 3.8.0-14-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Thu Mar 28 17:55:54 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2013-03-14 (13 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130314)
MarkForUpload: True
ProcCmdline: file-roller --extract-here file:///home/username/Arbeitsfl%C3%A4che/ab13s.rar
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x41dfb0: mov 0x18(%rdi),%rax
 PC (0x0041dfb0) 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
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: file-roller crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
theghost (theghost) 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 #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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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