file-roller crashed with SIGSEGV

Bug #1156549 reported by Stuart Bishop on 2013-03-18
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)
Undecided
Unassigned

Bug Description

Opened a rar file, informed rar not supported, clicked 'search for plugins', decided not enough information about the two found plugins to decide so closed the dialog. Crash.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: file-roller 3.6.3-1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Mon Mar 18 17:28:36 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2013-02-26 (20 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130225)
MarkForUpload: True
ProcCmdline: file-roller /home/username/Downloads/number_of_da_boots.rar
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
XsessionErrors:
 (process:2830): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
 (file-roller:3173): GLib-CRITICAL **: g_error_new_literal: assertion `message != NULL' failed

Stuart Bishop (stub) 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