GNOME Bugzilla – Bug 511573
crash in Take Screenshot: push start
Last modified: 2008-03-23 23:44:42 UTC
What were you doing when the application crashed? push start Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 61063168 vsize: 61063168 resident: 23465984 share: 16896000 rss: 23465984 rss_rlim: 4294967295 CPU usage: start_time: 1201104315 rtime: 21 utime: 17 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-screenshot' (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 -1208416544 (LWP 3803)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 186509
Thread 1 (Thread -1208416544 (LWP 3803))
----------- .xsession-errors (136 sec old) --------------------- (pidgin:2716): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed (pidgin:2716): GStreamer-CRITICAL **: gst_object_unref: assertion `((GObject *) object)->ref_count > 0' failed (pidgin:2716): GStreamer-CRITICAL **: Trying to dispose element play, but it is not in the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. (pidgin:2716): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed (pidgin:2716): GStreamer-CRITICAL **: gst_object_unref: assertion `((GObject *) object)->ref_count > 0' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 503297 ***