evince sometimes crashed with SIGSEGV in __strchr_sse2() (regression in Oneiric?)

Bug #884689 reported by Martin Constantino–Bodin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi!

I’ve recently upgraded to Oneiric and from now, there happens times when I open a PDF with Evince, which Seg Fault immediately.
I cannot see any pattern for those Seg Fault: for instance I’ve just opened two PDF files with Evince.
The first one was well opened, but Evince Seg Fault in the second one; but once I restart Evince on the second one, it works well.
It has never done strange things like that before the upgrade, and this is not the first time in Oneiric it does that.

I have to warn you that there has been some difficulties to upgrade to Oneiric (some package broken for instance). I don’t know if Evince is one of them, but it stay possible.

I hope the informations apport gave would be enough… Do not hesitate to ask me further informations if needed.
Martin.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: evince 3.2.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CheckboxSubmission: 01a18e0a74cbde3d34a62f62830ed079
CheckboxSystem: f134069bba098730d27f59b402920826
CrashCounter: 1
Date: Tue Nov 1 11:31:01 2011
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=fcfa3d54-cbdb-4fb9-ad94-3575c1999a80 ro quiet splash vt.handoff=7
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f55cb14fc2a <__strchr_sse2+26>: movdqa (%rdi),%xmm0
 PC (0x7f55cb14fc2a) ok
 source "(%rdi)" (0x000001a0) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 __strchr_sse2 () at ../sysdeps/x86_64/multiarch/../strchr.S:33
 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
 ev_window_init (ev_window=0x7f55d0364280) at /build/buildd/evince-3.2.1/./shell/ev-window.c:7316
Title: evince crashed with SIGSEGV in __strchr_sse2()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video

Revision history for this message
Martin Constantino–Bodin (martin-bodin) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.