file-roller crashed with SIGSEGV in syscall()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
file-roller (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Opened a tar.gz, double clicked a python file which should have been opened in my editor but instead crashed file-roller
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: file-roller 3.16.4-1ubuntu3
ProcVersionSign
Uname: Linux 4.4.0-17-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Apr 4 02:48:17 2016
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2015-08-20 (228 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: file-roller /home/username/
ProcEnviron:
LD_LIBRARY_
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
Registers: $8 = 0x4 <error: Cannot access memory at address 0x4>
SegvAnalysis: Failure: invalid literal for int() with base 16: '='
Signal: 11
SourcePackage: file-roller
StacktraceTop:
syscall () at ../sysdeps/
g_cond_wait_until (cond=cond@
g_async_
g_async_
g_thread_
ThreadStacktrace: $4 = 0x0
Title: file-roller crashed with SIGSEGV in syscall()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers
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 #1428619, 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.