evince crashed with SIGSEGV in __strchr_sse42()

Bug #896816 reported by Anand Kumria on 2011-11-27
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Undecided
Unassigned

Bug Description

double clicked on file, and this crash dialog came up

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evince 3.2.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sat Nov 26 23:49:28 2011
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=5e5dbc25-bc60-422e-9227-9ede108329e7 ro quiet splash no_console_suspend vt.handoff=7
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, user)
 LANG=en_AU.UTF-8
 LC_MESSAGES=en_AU.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7fe69f5578f4 <__strchr_sse42+36>: movdqa (%r8),%xmm0
 PC (0x7fe69f5578f4) ok
 source "(%r8)" (0x00000350) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 __strchr_sse42 () at ../sysdeps/x86_64/multiarch/strchr.S:97
 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 __strchr_sse42()
UpgradeStatus: Upgraded to oneiric on 2011-11-12 (14 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Anand Kumria (wildfire) wrote :

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 #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