GNOME Bugzilla – Bug 574830
crash in Document Viewer: I was printing page 2-6 ...
Last modified: 2009-03-10 20:47:11 UTC
Version: 2.22.2 What were you doing when the application crashed? I was printing page 2-6 of a pdf Distribution: Debian squeeze/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 549195776 vsize: 549195776 resident: 243073024 share: 17338368 rss: 243073024 rss_rlim: 18446744073709551615 CPU usage: start_time: 1236717361 rtime: 1094 utime: 926 stime: 168 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' [Thread debugging using libthread_db enabled] [New Thread 0x7f7b9a41f7d0 (LWP 24575)] [New Thread 0x40bf3950 (LWP 24576)] 0x00007f7b9498ab66 in poll () from /lib/libc.so.6
+ Trace 213339
Thread 2 (Thread 0x40bf3950 (LWP 24576))
----------- .xsession-errors (117106 sec old) --------------------- (acroread-esp:8395): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkObject' (acroread-esp:8395): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject' (acroread-esp:8395): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (acroread-esp:8395): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkObject' (acroread-esp:8395): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkObject' (acroread-esp:8395): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_IS_WIDGET (widget)' failed (acroread-esp:8395): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 555375 ***