GNOME Bugzilla – Bug 549451
crash in Document Viewer: printing 60 pages: 2 per...
Last modified: 2008-09-01 01:49:06 UTC
Version: 2.20.2 What were you doing when the application crashed? printing 60 pages: 2 per page + recto/verso 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: 95711232 vsize: 95711232 resident: 72273920 share: 15335424 rss: 72273920 rss_rlim: 4294967295 CPU usage: start_time: 1219763977 rtime: 2610 utime: 2516 stime: 94 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 0xb6aec940 (LWP 26177)] [New Thread 0xb6967b90 (LWP 26178)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 205695
Thread 2 (Thread 0xb6967b90 (LWP 26178))
----------- .xsession-errors (29 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. *** 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)! --------------------------------------------------
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 ***