evince crashed with SIGSEGV in g_param_spec_pool_lookup()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evince (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Loading a pdf from a zip file.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evince 3.2.1-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sun Nov 6 00:01:48 2011
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
KernLog:
Nov 1 00:31:43 drowelf kernel: [ 1763.214539] type=1400 audit(132012550
Nov 1 00:31:43 drowelf kernel: [ 1763.215021] type=1400 audit(132012550
Nov 1 00:31:43 drowelf kernel: [ 1763.397525] type=1400 audit(132012550
Nov 1 00:31:43 drowelf kernel: [ 1763.399307] type=1400 audit(132012550
Nov 4 01:12:09 drowelf kernel: [262875.022237] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
ProcCmdline: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f96c2cb58f4: movdqa (%r8),%xmm0
PC (0x7f96c2cb58f4) ok
source "(%r8)" (0x000001b0) not located in a known VMA region (needed readable region)!
destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
?? () from /lib/x86_
g_param_
g_object_
g_object_set () from /usr/lib/
?? ()
Title: evince crashed with SIGSEGV in g_param_
UpgradeStatus: Upgraded to oneiric on 2011-10-21 (15 days ago)
UserGroups: Domain Admins Domain Users adm admin cdrom lpadmin sambashare video
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #880818, 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.