evince crashed with SIGSEGV in doc_rect_to_view_rect()

Bug #567684 reported by manuel on 2010-04-21
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: evince

I found Bug #269685 similar but my crash is not related to search.

Steps to replicate:
   1.- Open a PDF file which contain text boxes
   2.- Type 2 words in a text box
   3.- press CTLF-LEFT to move a word left
   4.- Evince crash

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 1b6a3fcec77eb1f61cd3ecdd049007c4
CheckboxSystem: c69722ecac764861be52925fa50b4dcc
Date: Tue Apr 20 22:57:52 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evince
Package: evince 2.28.1-0ubuntu1.2
ProcCmdline: root=UUID=26de290e-7001-4f69-8046-4d39957c6393 ro quiet splash usbcore.autosuspend=1
ProcEnviron:
 LANG=es_VE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SegvAnalysis:
 Segfault happened at: 0x9ce73c <doc_rect_to_view_rect+140>: fldl 0x8(%eax)
 PC (0x009ce73c) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evince
StacktraceTop:
 doc_rect_to_view_rect (view=0x88001a8, page=<value optimized out>,
 ev_view_get_area_from_mapping (view=0x88001a8,
 ev_view_form_field_get_region (view=0x88001a8,
 ev_view_form_field_text_save (view=0x88001a8,
 ?? () from /usr/lib/libgobject-2.0.so.0
Tags: ubuntu-unr
Title: evince crashed with SIGSEGV in doc_rect_to_view_rect()
Uname: Linux 2.6.31-20-generic i686
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare

manuel (manuel-soto) wrote :
Sergio Barjola (sbarjola) wrote :

Thank you for taking the time to report this bug. I can confirm in Ubuntu 9.10 too.

Changed in evince (Ubuntu):
status: New → Confirmed
Timmy Shih Jun Yee (shijun) wrote :

Can you please attach a PDF file that contains text boxes? Thanks!

Changed in evince (Ubuntu):
status: Confirmed → Incomplete
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in evince (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers