GNOME Bugzilla – Bug 534831
crash in Document Viewer: scrolling
Last modified: 2008-06-10 08:14:49 UTC
Version: 2.22.1.1 What were you doing when the application crashed? scrolling Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-amd64 #1 SMP Wed May 14 14:04:05 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Wasp Icon Theme: Wasp Memory status: size: 402882560 vsize: 402882560 resident: 68173824 share: 13672448 rss: 68173824 rss_rlim: 18446744073709551615 CPU usage: start_time: 1211687846 rtime: 2273 utime: 1925 stime: 348 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7f04d0d08780 (LWP 6975)] [New Thread 0x42055950 (LWP 6976)] (no debugging symbols found) 0x00007f04ca992d04 in __lll_lock_wait () from /lib/libpthread.so.0
+ Trace 198629
Thread 2 (Thread 0x42055950 (LWP 6976))
----------- .xsession-errors (2225 sec old) --------------------- (npviewer.bin:32073): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64 (npviewer.bin:32073): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64 (npviewer.bin:32073): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64 (npviewer.bin:32073): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libsmooth.so: wrong ELF class: ELFCLASS64 (pan:31661): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (pan:31661): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (pan:31661): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `src != NULL' failed (pan:31661): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed --------------------------------------------------
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!
*** Bug 535761 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 536482 ***