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 542006 - crash in Document Viewer: Just browsing the web an...
crash in Document Viewer: Just browsing the web an...
Status: RESOLVED DUPLICATE of bug 543942
Product: evince
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
: 543548 544523 545784 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-07-08 07:12 UTC by javier
Modified: 2008-08-02 20:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description javier 2008-07-08 07:12:12 UTC 
Version: 2.22.2

What were you doing when the application crashed?
Just browsing the web and opening a pdf file from a link.


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.22-3-k7 #1 SMP Sun Feb 10 21:04:14 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: gnome

Memory status: size: 75087872 vsize: 75087872 resident: 52776960 share: 13475840 rss: 52776960 rss_rlim: 4294967295
CPU usage: start_time: 1215417379 rtime: 1128 utime: 984 stime: 144 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bfd720 (LWP 21541)]
[New Thread 0xb6a2db90 (LWP 21542)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 202291

Thread 1 (Thread 0xb6bfd720 (LWP 21541))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 poppler_attachment_save_to_callback
    from /usr/lib/libpoppler-glib.so.3
  • #7 ??
    from /usr/lib/evince/backends/libpdfdocument.so
  • #8 ev_document_get_attachments
    from /usr/lib/libevbackend.so.0
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
Error: Weird page contents
Error (1149168): Bad 'Length' attribute in stream
Error: Weird page contents
Error (1149884): Bad 'Length' attribute in stream
Error: Weird page contents
Error (1149884): Bad 'Length' attribute in stream
Error: Weird page contents
Error (1149884): Bad 'Length' attribute in stream
Error: Weird page contents
Error (151120): Unknown operator 'w6078'
Error (151120): Too few (2) args to 'k' operator
Error (245815): Unexpected end of file in flate stream
Error: Unterminated string
Error: End of file inside array
Error: Leftover args in content stream
--------------------------------------------------
Comment 1 Goran Rakic 2008-07-08 17:51:09 UTC 
Thanks for taking the time to report this bug.

Unfortunately, that 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 and reopen this bug or report a new one. 

Also, if you can repeat this crash with same PDF document again, it will help us to resolve this problem if you can provide link to the document. The bug can actually be a problem with the PDF library that Evince uses called Poppler, but we can not know that without valid stack trace and/or PDF file that is causing a problem.

Thanks in advance!
Comment 2 Susana 2008-07-20 09:23:33 UTC 
*** Bug 543548 has been marked as a duplicate of this bug. ***
Comment 3 Susana 2008-07-27 21:52:02 UTC 
*** Bug 544523 has been marked as a duplicate of this bug. ***
Comment 4 Carlos Garcia Campos 2008-08-01 08:06:30 UTC 
*** Bug 545784 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2008-08-02 20:25:46 UTC 
Bug 543942 has a slightly better backtrace, though we still need a better one. Bug reporters, please help fixing this by providing a good trace!
Comment 6 André Klapper 2008-08-02 20:26:00 UTC 

*** This bug has been marked as a duplicate of 543942 ***