GNOME Bugzilla – Bug 539561
crash in Document Viewer: I was opening a pdf docu...
Last modified: 2008-06-22 12:35:42 UTC
Version: 2.22.2 What were you doing when the application crashed? I was opening a pdf document. Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Thu Jun 12 16:26:30 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 69156864 vsize: 69156864 resident: 47374336 share: 12804096 rss: 47374336 rss_rlim: 4294967295 CPU usage: start_time: 1214106254 rtime: 2943 utime: 2694 stime: 249 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 0xb6c1e720 (LWP 14979)] [New Thread 0xb6a50b90 (LWP 14980)] (no debugging symbols found) 0xb7fe2424 in __kernel_vsyscall ()
+ Trace 201060
Thread 2 (Thread 0xb6a50b90 (LWP 14980))
----------- .xsession-errors (9939 sec old) --------------------- (firefox-bin:5663): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5663): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5663): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5663): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5663): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5663): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:5663): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Advertencia del gestor de ventanas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600003 (Visor de d) Advertencia del gestor de ventanas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
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 536482 ***