file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
file-roller (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
In a Saucy amd64 system I opened a .tar.xz archive (which I'd previously created myself on another system with "tar cf ..." followed by "xz -9v ...") and double-clicked on the single folder it contained, to view its contents in file-roller itself before performing any extractions. file-roller crashed.
I believe this is bug 723841 but I am not 100% sure without looking at a good symbolic trace, so I'm posting this just in case. I'll try to compare the trace as soon as there's a good one, unless someone else (or the Apport retracing service bot) does so first.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: file-roller 3.8.3-0ubuntu1
ProcVersionSign
Uname: Linux 3.10.0-4-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Sat Jul 20 22:21:49 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-07-17 (5 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130716)
MarkForUpload: True
ProcCmdline: file-roller file://
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x41cb30: mov (%rbx),%rsi
PC (0x0041cb30) ok
source "(%rbx)" (0x00000048) not located in a known VMA region (needed readable region)!
destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
?? ()
_gtk_marshal_
g_closure_invoke (closure=0x2998cb0, return_
signal_
g_signal_
Title: file-roller crashed with SIGSEGV in _gtk_marshal_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #723841, 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.