GNOME Bugzilla – Bug 536563
crash in Document Viewer: printing a big file
Last modified: 2008-06-07 08:15:43 UTC
Version: 2.20.2 What were you doing when the application crashed? printing a big file Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 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: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mac4Lin_Icons_v0.4 Memory status: size: 50036736 vsize: 50036736 resident: 27500544 share: 14749696 rss: 27500544 rss_rlim: 4294967295 CPU usage: start_time: 1212575457 rtime: 5890 utime: 5763 stime: 127 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 0xb6a5c940 (LWP 6387)] [New Thread 0xb68b1b90 (LWP 6388)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199539
Thread 2 (Thread 0xb68b1b90 (LWP 6388))
----------- .xsession-errors --------------------- Error: Unknown character collection 'Adobe-Japan1' Xlib: unexpected async reply (sequence 0x37c2)! Error: /syntaxerror in -file- Operand stack: sfnts --nostringval-- Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1909 1 3 Dictionary stack: --dict:1156/1684(ro)(G)-- --dict:0/20(G)-- --dict:120/200(L)-- --dict:7/11(L)-- Current allocation mode is local Last OS error: 2 GPL Ghostscript 8.62: Unrecoverable error, exit code 1 ** (evince-thumbnailer:6475): WARNING **: Interpreter failed. Xlib: sequence lost (0x1388f > 0x3893) in reply type 0x0! --------------------------------------------------
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 ***