file-roller crashed with SIGSEGV in dlg_package_installer()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
File Roller |
Fix Released
|
Medium
|
|||
file-roller (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Quantal |
Fix Released
|
High
|
Unassigned |
Bug Description
file-roller crashed with SIGSEGV in g_simple_
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: file-roller 3.5.4-0ubuntu3
ProcVersionSign
Uname: Linux 3.5.0-10-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CrashCounter: 1
Date: Wed Aug 15 00:01:03 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
ProcCmdline: file-roller /home/username/
ProcEnviron:
PATH=(custom, no user)
LANG=es_ES.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x419903: mov 0x20(%rax),%rdi
PC (0x00419903) ok
source "0x20(%rax)" (0x00000020) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
g_simple_
Title: file-roller crashed with SIGSEGV in g_simple_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip disk lpadmin plugdev sambashare sudo
tags: | added: bugpattern-needed |
Changed in file-roller (Ubuntu Quantal): | |
status: | In Progress → Fix Committed |
Changed in file-roller: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
This crash has the same stack trace characteristics as bug #1035912. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.