Ubuntu
file-roller package

file-roller crashed with SIGSEGV in fr_archive_create()

Bug #1059992 reported by Carlos Donizete Froes on 2012-10-02

30

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	File Roller	New	Undecided	Unassigned
	file-roller (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

When trying to extract a compressed file, clicking over the file right click and then clicking on "Extract here" simply does not extract.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: file-roller 3.6.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic i686
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Tue Oct 2 02:16:22 2012
ExecutablePath: /usr/bin/file-roller
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120929)
ProcCmdline: file-roller --extract-to file:///home/username/Downloads /home/username/Downloads/Video\ Aula\ -\ Python.part1.rar
ProcEnviron:
LANGUAGE=pt_BR:en
PATH=(custom, no user)
LANG=pt_BR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x8061625: mov 0xc(%ebx),%edi
PC (0x08061625) ok
source "0xc(%ebx)" (0x0000000c) not located in a known VMA region (needed readable region)!
destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
Title: file-roller crashed with SIGSEGV in ffi_call_SYSV()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Carlos Donizete Froes (coringao) wrote on 2012-10-02:

#1

bug-extract.png Edit (532.6 KiB, image/png)
Dependencies.txt Edit (5.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (531 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (24.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (800 bytes, text/plain; charset="utf-8")
Registers.txt Edit (467 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-02:

#2

StacktraceTop:
fr_archive_create (file=file@entry=0xa034380, mime_type=<optimized out>, mime_type@entry=0x0) at fr-archive.c:593
fr_window_archive_new (window=0x9fac080, file=0xa034380, mime_type=0x0) at fr-window.c:5919
fr_window_exec_batch_action (window=0x9fac080, action=<error reading variable: Unhandled dwarf expression opcode 0xfa>, action=<error reading variable: Unhandled dwarf expression opcode 0xfa>) at fr-window.c:9220
fr_application_command_line (application=0x9ef3000, command_line=0x9f5c718) at main.c:821
ffi_call_SYSV () at ../src/x86/sysv.S:64

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-02: Stacktrace.txt

#3

Stacktrace.txt Edit (5.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-02: StacktraceSource.txt

#4

StacktraceSource.txt Edit (5.0 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-02: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (12.1 KiB, text/plain)

Changed in file-roller (Ubuntu):
importance:	Undecided → Medium
summary:	- file-roller crashed with SIGSEGV in ffi_call_SYSV() + file-roller crashed with SIGSEGV in fr_archive_create()
tags:	removed: need-i386-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-10-05:

#6

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in file-roller (Ubuntu):
status:	New → Confirmed

Revision history for this message

Sebastien Bacher (seb128) wrote on 2012-10-05:

#7

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

visibility:

private → public

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #1064892

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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