GNOME Bugzilla – Bug 549454
crash in Document Viewer: printing http://www.lin...
Last modified: 2008-09-01 01:49:19 UTC
Version: 2.20.2 What were you doing when the application crashed? printing http://www.linuxsymposium.org/2008/ols-2008-Proceedings-V1.pdf from page 121 to 180 Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: gnome Memory status: size: 88047616 vsize: 88047616 resident: 65978368 share: 15302656 rss: 65978368 rss_rlim: 4294967295 CPU usage: start_time: 1219764570 rtime: 1396 utime: 1354 stime: 42 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 0xb6a7e940 (LWP 26514)] [New Thread 0xb68f9b90 (LWP 26515)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 205697
Thread 2 (Thread 0xb68f9b90 (LWP 26515))
----------- .xsession-errors (19 sec old) --------------------- *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. Xlib: unexpected async reply (sequence 0x1f7fe)! evince: /build/buildd/cairo-1.6.4/src/cairo-ps-surface.c:595: _cairo_ps_surface_emit_unscaled_font_subset: Assertion `NOT_REACHED' failed. Xlib: unexpected async reply (sequence 0xe51c)! Xlib: unexpected async reply (sequence 0x9a9b)! Xlib: unexpected async reply (sequence 0x6f31)! --------------------------------------------------
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. Thanks in advance!
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 524762 ***