file-roller crashed with SIGSEGV in g_closure_invoke() when trying to open a .tar file from inside Files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
file-roller (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I was browsing a directory from inside Files v3.10.1. I double clicked on a .tar archive and instead of opening the Archive Manger to view the file I ended up at this crash report screen.
I have tried to access the same file again and this time I am able to access it and other files in the directory without an issue.
The suggested similar bugs were:
* bug 333007 - That specified a .tar.gz file under Gnome. I am running under Unity (which is similar).
* bug 350289 - This started under a Firefox plugin. I am using the default file browser.
* bug 723841 - This is about browsing inside a .7z archive. I was attempting to open a .tar from within a standard directory.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: file-roller 3.10.2.1-0ubuntu4.1
ProcVersionSign
Uname: Linux 3.16.0-70-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Thu Apr 28 14:01:40 2016
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2015-03-12 (412 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
ProcCmdline: file-roller --extract-here file://
SegvAnalysis:
Segfault happened at: 0x41c4f0: mov (%rbx),%rsi
PC (0x0041c4f0) ok
source "(%rbx)" (0x00000045) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin mock 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 #1502616, 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.