GNOME Bugzilla – Bug 479979
Crash in wnck_task_button_glow()/cairo_translate()
Last modified: 2009-01-19 15:45:10 UTC
Version: 2.20.0.1 What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.20.0 2007-09-20 (JHBuild) BugBuddy Version: 2.20.0 System: Linux 2.6.22.5-mactel #6 SMP Fri Sep 21 17:21:38 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 28213248 vsize: 28213248 resident: 14745600 share: 11259904 rss: 14745600 rss_rlim: 4294967295 CPU usage: start_time: 1190622911 rtime: 5126 utime: 4694 stime: 432 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/local/libexec/wnck-applet' (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 -1225472320 (LWP 3128)] 0xb7fc4410 in __kernel_vsyscall ()
+ Trace 165192
Thread 1 (Thread -1225472320 (LWP 3128))
----------- .xsession-errors (43161 sec old) --------------------- (rhythmbox-metadata:11161): GStreamer-CRITICAL **: gst_element_post_message: assertion `message != NULL' failed ** (rhythmbox-metadata:11161): CRITICAL **: gst_missing_decoder_message_new: assertion `gst_caps_is_fixed (decode_caps)' failed (rhythmbox-metadata:11161): GStreamer-CRITICAL **: gst_element_post_message: assertion `message != NULL' failed ** (rhythmbox-metadata:11161): CRITICAL **: gst_missing_decoder_message_new: assertion `gst_caps_is_fixed (decode_caps)' failed (rhythmbox-metadata:11161): GStreamer-CRITICAL **: gst_element_post_message: assertion `message != NULL' failed ** (rhythmbox-metadata:11161): CRITICAL **: gst_missing_decoder_message_new: assertion `gst_caps_is_fixed (decode_caps)' failed (rhythmbox-metadata:11161): GStreamer-CRITICAL **: gst_element_post_message: assertion `message != NULL' failed ...Too much output, ignoring rest... --------------------------------------------------
Eloi: did you see the crash again? Also, if it's possible to have more information in the stack trace for the future, that'd be great ;-) Thanks!
*** Bug 529714 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!