evince crashes when using "find"

Bug #322504 reported by AT
4
Affects Status Importance Assigned to Milestone
poppler (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evince

Ubuntu 8.10
apt-cache policy evince
evince:
  Installed: 2.24.1-0ubuntu1
  Candidate: 2.24.1-0ubuntu1
  Version table:
 *** 2.24.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

In the attached file whenever I try to search for text using find I get a crash. I've tried this several times, starting on several different pages, at different levels of zoom and searching for different things. It will crash after typing in the first letter. Normally the find feature works well for me, so I think it is due to this particular .pdf file.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/evince
NonfreeKernelModules: nvidia
Package: evince 2.24.1-0ubuntu1
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
Uname: Linux 2.6.27-9-generic x86_64

Tags: apport-bug
Revision history for this message
AT (atorgovitsky) wrote :
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. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

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

the example works on jaunty and could be a poppler bug fixed in the new version

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

I can verify that searching the document crashes evince in Intrepid, evince version 2.24.1-0ubuntu1, libpoppler3 version 0.8.7-1ubuntu0.1

Changed in evince:
status: Incomplete → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

don't reopen the bug if you don't reply to the requested informations

Changed in evince:
status: Confirmed → Incomplete
Revision history for this message
AT (atorgovitsky) wrote :

I tried the instructions to run the backtrace,
 https://wiki.ubuntu.com/DebuggingProgramCrash, 1-4
then
 https://wiki.ubuntu.com/Backtrace, 1-5

and everything went smoothly, but I couldn't get it to work. Here's my terminal output:

(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/evince
[Thread debugging using libthread_db enabled]
[New Thread 0x7f94ab0b9780 (LWP 7894)]

Program exited normally.
(gdb) backtrace full
No stack.
(gdb) info registers
The program has no registers now.
(gdb)

I imagine that when I say "backtrace full" it shouldn't say "No stack" right? After I used the "run" command I opened the file in evince, tried to search and got the crash.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the log indicates that evince has been closed and didn't crash

Revision history for this message
AT (atorgovitsky) wrote :

when I use the command "run" the evince window opens up, but I immediately get

(gdb) run
Starting program: /usr/bin/evince
[Thread debugging using libthread_db enabled]
[New Thread 0x7f3002f33780 (LWP 10060)]

Program exited normally.

Even while the evince window is still open and before I've done anything.

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you have an evince already running when you try starting the debug one?

Revision history for this message
AT (atorgovitsky) wrote :

ah yes, that was it on another desktop i had forgotten about.

the backtrace is attached.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the stacktrace indicates that's bug #288429 which is fixed in jaunty

Changed in evince:
status: Incomplete → Fix Released
Changed in poppler:
status: Fix Released → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

closing and settting as duplicate

Changed in evince:
status: Incomplete → Fix Released
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.