evince crashes with segfault when opening specific pdf

Bug #352709 reported by Gregory Petrosyan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evince

gregory@home:~$ uname -a
Linux home 2.6.27-14-generic #1 SMP Fri Mar 13 18:00:20 UTC 2009 i686 GNU/Linux

gregory@home:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.10
Release: 8.10
Codename: intrepid

gregory@home:~$ apt-cache policy evince
evince:
  Установлен: 2.24.1-0ubuntu1
  Кандидат: 2.24.1-0ubuntu1
  Таблица версий:
 *** 2.24.1-0ubuntu1 0
        500 http://ru.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

pdf file attached

Revision history for this message
Gregory Petrosyan (gregory-petrosyan) wrote :
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in evince (Ubuntu):
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

the example opens fine on jaunty so the bug might be already fixed there

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.