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 515162 - crash in Document Viewer: open pdf file
crash in Document Viewer: open pdf file
Status: RESOLVED DUPLICATE of bug 415714
Product: evince
Classification: Core
Component: general
0.8.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-08 09:47 UTC by Arseny
Modified: 2008-02-08 11:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Arseny 2008-02-08 09:47:33 UTC
Version: 0.8.2

What were you doing when the application crashed?
open pdf file


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.14-60.fc7 #1 SMP Mon Jan 14 22:14:17 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Fedora

Memory status: size: 84299776 vsize: 84299776 resident: 44003328 share: 18010112 rss: 44003328 rss_rlim: 4294967295
CPU usage: start_time: 1202464004 rtime: 141 utime: 127 stime: 14 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208473888 (LWP 4350)]
[New Thread -1210897520 (LWP 4351)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208473888 (LWP 4350))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 Catalog::embeddedFile
    from /usr/lib/libpoppler.so.1
  • #5 poppler_document_get_attachments
    from /usr/lib/libpoppler-glib.so.1
  • #6 ??
  • #7 ev_document_get_attachments
  • #8 ??
  • #9 ev_sidebar_set_document
  • #10 ??
  • #11 g_cclosure_marshal_VOID__VOID
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #13 g_cclosure_marshal_VOID__VOID
    from /lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (135 sec old) ---------------------
Предупреждение менеджера окон: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600003 (Экспо)
Предупреждение менеджера окон: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Предупреждение менеджера окон: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600003 (Экспо)
Предупреждение менеджера окон: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(eog:3769): GdkPixbuf-CRITICAL **: _gdk_pixbuf_load_module_unlocked: assertion `image_module->module == NULL' failed
Предупреждение менеджера окон: Received a _NET_WM_MOVERESIZE message for 0x1404c7e (Emblem); these messages lack timestamps and therefore suck.
(eog:4059): GdkPixbuf-CRITICAL **: _gdk_pixbuf_load_module_unlocked: assertion `image_module->module == NULL' failed
(eog:4086): GdkPixbuf-CRITICAL **: _gdk_pixbuf_load_module_unlocked: assertion `image_module->module == NULL' failed
Предупреждение менеджера окон: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00003 (Экспо)
Предупреждение менеджера окон: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Corrupt JPEG data: premature end of data segment
Error (18608379): Unexpected end of file in flate stream
--------------------------------------------------
Comment 1 Carlos Garcia Campos 2008-02-08 11:06:12 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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