GNOME Bugzilla – Bug 501675
crash in Document Viewer:
Last modified: 2007-12-12 02:27:34 UTC
Version: 2.20.1 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.1 2007-10-26 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22.6ilya-kernel #4 SMP PREEMPT Wed Nov 14 09:27:26 IST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Lush Icon Theme: Lush Memory status: size: 414748672 vsize: 414748672 resident: 113893376 share: 15806464 rss: 113893376 rss_rlim: 18446744073709551615 CPU usage: start_time: 1196838169 rtime: 3928 utime: 3630 stime: 298 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 0x2b15f0577880 (LWP 17459)] [New Thread 0x40800950 (LWP 17460)] (no debugging symbols found) 0x00002b15eb698c7f in waitpid () from /lib/libpthread.so.0
+ Trace 180785
Thread 1 (Thread 0x2b15f0577880 (LWP 17459))
----------- .xsession-errors (118784 sec old) --------------------- (gecko:4374): Gtk-CRITICAL **: _gtk_text_layout_get_block_cursor: assertion `layout != NULL' failed (gecko:4374): Gtk-CRITICAL **: gtk_text_layout_get_cursor_locations: assertion `layout != NULL' failed (gecko:4374): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed (gecko:4374): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed (gnome-terminal:4935): Vte-WARNING **: Отсутствует обработчик управляющей последовательности "device-control-string". (gnome-terminal:4935): Vte-WARNING **: Отсутствует обработчик управляющей последовательности "device-control-string". *** NSPlugin Viewer *** ERROR: NPN_Invoke() invoke: Прерван системный вызов *** NSPlugin Viewer *** ...Too much output, ignoring rest... --------------------------------------------------
*** This bug has been marked as a duplicate of 501673 ***