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 562874 - crash in Document Viewer: loading http://www.publi...
crash in Document Viewer: loading http://www.publi...
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
Depends on:
Blocks:
 
 
Reported: 2008-12-01 14:37 UTC by chrisw
Modified: 2008-12-01 17:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description chrisw 2008-12-01 14:37:00 UTC
Version: 2.22.2

What were you doing when the application crashed?
loading http://www.publications.parliament.uk/pa/cm200708/cmselect/cmtran/84/84.pdf from the command line


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.27.5 #1 SMP Sat Nov 8 18:55:35 GMT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 104353792 vsize: 104353792 resident: 81408000 share: 13410304 rss: 81408000 rss_rlim: 4294967295
CPU usage: start_time: 1228134095 rtime: 833 utime: 720 stime: 113 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6bfb700 (LWP 3945)]
[New Thread 0xb6a4cb90 (LWP 3946)]
0xb80a5424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6bfb700 (LWP 3945))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 poppler_attachment_save_to_callback
    from /usr/lib/libpoppler-glib.so.3
  • #8 pdf_document_get_attachments
    at /build/buildd/evince-2.22.2/./backend/pdf/ev-poppler.cc line 394
  • #9 ev_document_get_attachments
    at /build/buildd/evince-2.22.2/./libdocument/ev-document.c line 206
  • #10 ev_sidebar_attachments_set_document
    at /build/buildd/evince-2.22.2/./shell/ev-sidebar-attachments.c line 636
  • #11 ev_sidebar_set_document
    at /build/buildd/evince-2.22.2/./shell/ev-sidebar.c line 511
  • #12 ev_window_setup_document
    at /build/buildd/evince-2.22.2/./shell/ev-window.c line 1126
  • #13 g_idle_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 4090
  • #14 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2012
  • #15 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2645
  • #16 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
  • #17 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.11/gtk/gtkmain.c line 1163
  • #18 main
    at /build/buildd/evince-2.22.2/./shell/main.c line 401
  • #0 __kernel_vsyscall


----------- .xsession-errors (6 sec old) ---------------------
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
Error (113022): Unexpected end of file in flate stream
Error: Unterminated string
Error: End of file inside array
Error: Leftover args in content stream
Error: Invalid Font Weight
Error: Invalid Font Weight
Error: Invalid Font Weight
Error (109116): Bad block header in flate stream
--------------------------------------------------
Comment 1 palfrey 2008-12-01 17:54:49 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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