After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 379852 - Evince crash when opening PDF
Evince crash when opening PDF
Status: RESOLVED DUPLICATE of bug 303944
Product: evince
Classification: Core
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-27 17:19 UTC by cmptrmaniac62
Modified: 2006-11-30 06:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description cmptrmaniac62 2006-11-27 17:18:12 UTC
Distribution: Debian 4.0
Package: evince
Severity: Normal
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Debian
Synopsis: Evince crash when opening PDF
Bugzilla-Product: evince
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Evince crashes when opening the following PDF:
http://www.adobe.com/products/acrobat/pdfs/3d_pdf_demo.pdf

Steps to reproduce the crash:
1. Open the PDF

Expected Results:
Not crashing :-)

How often does this happen?
Always

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/evince'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47290589754512 (LWP 9464)]
[New Thread 1082132832 (LWP 9465)]
(no debugging symbols found)
0x00002b02b1c57d06 in poll () from /lib/libc.so.6




------- Bug created by bug-buddy at 2006-11-27 17:19 -------

Comment 1 André Klapper 2006-11-27 22:57:43 UTC
Thanks for taking the time to report this bug.
Unfortunately it lacks some information that may help us in finding the cause of the bug. The stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Also this may be a Poppler Bug (the backend used by Evince to render PDF), could you please supply the poppler version and type? You can find it in the Help->About menu in Evince.
Thanks in advance!
Comment 2 cmptrmaniac62 2006-11-28 00:37:40 UTC
I was unable to get debug symbols for libpoppler, libpthread or evince, but the new trace might be enough? If not, I'll be happy to compile from scratch to get debug symbols.

--------------------------------

Evince version: 0.4.0
Poppler version: 0.4.5 (splash)

--------------------------------

Backtrace was generated from '/usr/bin/evince'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47509439562896 (LWP 16245)]
[New Thread 1082132832 (LWP 16246)]
0x00002b35a63c8d06 in poll () from /lib/libc.so.6

Thread 2 (Thread 1082132832 (LWP 16246))

  • #0 waitpid
    from /lib/libc.so.6
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 820
  • #2 <signal handler called>
  • #3 JPXStream::readCodeBlockData
    from /usr/lib/libpoppler.so.0
  • #4 JPXStream::readTilePartData
    from /usr/lib/libpoppler.so.0
  • #5 JPXStream::readTilePart
    from /usr/lib/libpoppler.so.0
  • #6 JPXStream::readCodestream
    from /usr/lib/libpoppler.so.0
  • #7 JPXStream::readBoxes
    from /usr/lib/libpoppler.so.0
  • #8 JPXStream::reset
    from /usr/lib/libpoppler.so.0
  • #9 SplashOutputDev::drawImage
    from /usr/lib/libpoppler.so.0
  • #10 Gfx::doImage
    from /usr/lib/libpoppler.so.0
  • #11 Gfx::opXObject
    from /usr/lib/libpoppler.so.0
  • #12 Gfx::go
    from /usr/lib/libpoppler.so.0
  • #13 Gfx::display
    from /usr/lib/libpoppler.so.0
  • #14 Page::displaySlice
    from /usr/lib/libpoppler.so.0
  • #15 poppler_page_render_to_pixbuf
    from /usr/lib/libpoppler-glib.so.0
  • #16 pdf_document_find_get_progress
  • #17 ev_job_render_run
  • #18 ev_job_queue_update_job
  • #19 ev_job_queue_init
  • #20 g_thread_create_proxy
    at gthread.c line 553
  • #21 start_thread
    from /lib/libpthread.so.0
  • #22 clone
    from /lib/libc.so.6
  • #23 ??

Comment 3 Nickolay V. Shmyrev 2006-11-28 01:47:16 UTC
 Hi, this looks like a bug with the PDF backend.  Could you please follow these instructions to help get this bug fixed.  Thank You. 

http://live.gnome.org/Evince/PopplerBugs#poppler
 

Moreover, there is similar gpdf bug, so I suspect it's a long waiting problem. Please, transfer it to poppler and provide a testcase.

*** This bug has been marked as a duplicate of 303944 ***
Comment 4 cmptrmaniac62 2006-11-30 06:26:57 UTC
This bug has been transferred to the Poppler Bugzilla:

https://bugs.freedesktop.org/show_bug.cgi?id=9203