evince crashed with SIGSEGV in g_param_spec_pool_lookup()

Bug #886851 reported by Helge Jung on 2011-11-06
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Undecided
Unassigned

Bug Description

This happened when opening a datasheet PDF loaded from Sparkfun. I suppose this hasn't to do anything with the PDF file itself (it opened fine the second time) as I received that "VMA region" message in multiple apport issues triggered on my system already.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evince 3.2.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sun Nov 6 17:29:51 2011
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=9646dffe-37d3-4d32-9fc6-53b122473eb6 ro i8042.reset=1 quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7fa627e8ec2a: movdqa (%rdi),%xmm0
 PC (0x7fa627e8ec2a) ok
 source "(%rdi)" (0x000002b0) 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_64-linux-gnu/libc.so.6
 g_param_spec_pool_lookup () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_set_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_set () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
Title: evince crashed with SIGSEGV in g_param_spec_pool_lookup()
UpgradeStatus: Upgraded to oneiric on 2011-10-15 (22 days ago)
UserGroups: adm admin cdrom chipcard dialout lpadmin plugdev sambashare vboxusers

Helge Jung (youngage) wrote :

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 #879926, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers