file-roller crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
file-roller (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Unexpected closing after opening an archive
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: file-roller 3.6.3-1ubuntu4
ProcVersionSign
Uname: Linux 3.8.0-26-generic i686
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: i386
Date: Mon Jul 8 18:26:36 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2012-05-14 (419 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MarkForUpload: True
ProcCmdline: file-roller /home/username/
ProcEnviron:
LD_LIBRARY_
PATH=(custom, no user)
XDG_RUNTIME_
LANG=ru_RU.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x805e400: mov (%ebx),%edx
PC (0x0805e400) ok
source "(%ebx)" (0x00000070) not located in a known VMA region (needed readable region)!
destination "%edx" 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 raring on 2013-04-26 (73 days ago)
UserGroups: adm lpadmin nopasswdlogin 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.