file-roller crashed with SIGSEGV in g_closure_invoke() on double-clicking a folder
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
file-roller (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
double clicking on a folder in a tar.bz2 file caused the crash
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: file-roller 3.10.2.1-0ubuntu4
ProcVersionSign
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 8 15:46:29 2014
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-11-26 (133 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: file-roller /tmp/lm-
SegvAnalysis:
Segfault happened at: 0x41c4f0: mov (%rbx),%rsi
PC (0x0041c4f0) ok
source "(%rbx)" (0x00000050) not located in a known VMA region (needed readable region)!
destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
?? ()
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: file-roller crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to trusty on 2014-01-22 (75 days ago)
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.