file-roller crashed with SIGSEGV

Bug #1318731 reported by LAZA
24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Fix Committed
Medium
Unassigned

Bug Description

May a problem cause it is a .rar file

~$ lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04

~$ apt-cache policy file-roller
file-roller:
  Installiert: 3.10.2.1-0ubuntu4
  Installationskandidat: 3.10.2.1-0ubuntu4
  Versionstabelle:
 *** 3.10.2.1-0ubuntu4 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: file-roller 3.10.2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
Date: Mon May 12 17:59:48 2014
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2014-03-16 (57 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140225)
ProcCmdline: file-roller --extract-to=/home/username/Downloads/2014.04\ Indie\ Cindy --extract-here --force /home/username/Downloads/2014.04\ Indie\ Cindy/Pixies\ -\ Indie\ Cindy\ [2014\ ALBUM].rar
SegvAnalysis:
 Segfault happened at: 0x42eea5: cmpb $0x2f,0x0(%rbp)
 PC (0x0042eea5) ok
 source "$0x2f" ok
 destination "0x0(%rbp)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: file-roller crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare sudo tape vboxusers video

Revision history for this message
LAZA (laza74) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 parse_name_field (line=<optimized out>, rar_comm=0x234d3d0) at fr-command-rar.c:149
 process_line (line=<optimized out>, data=<optimized out>) at fr-command-rar.c:213
 fr_channel_data_read (channel=channel@entry=0x2838058) at fr-process.c:141
 check_child (data=0x27cd9a0, data@entry=<error reading variable: value has been optimized out>) at fr-process.c:799
 g_timeout_dispatch (source=0x2598710, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.40.0/./glib/gmain.c:4472

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in file-roller (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :
information type: Private → Public
Changed in file-roller (Ubuntu):
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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