GNOME Bugzilla – Bug 496340
crash in Tasks:
Last modified: 2007-11-14 00:45:30 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 219734016 vsize: 219734016 resident: 141148160 share: 29249536 rss: 141148160 rss_rlim: 4294967295 CPU usage: start_time: 1194945890 rtime: 2429 utime: 2336 stime: 93 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208367392 (LWP 2999)] [New Thread -1229608048 (LWP 3925)] [New Thread -1219118192 (LWP 3915)] [New Thread -1271497840 (LWP 3076)] [New Thread -1240097904 (LWP 3037)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 177341
Thread 1 (Thread -1208367392 (LWP 2999))
----------- .xsession-errors (1693 sec old) --------------------- *************************************** It is potentially dangerous, and might not even work properly. [00000382] a52 decoder: A/52 channels:2 samplerate:48000 bitrate:448000 No accelerated IMDCT transform found (.:3461): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed (.:3461): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed (.:3461): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed [00000313] main playlist: stopping playback gnome-mount 0.6 Unmounted /dev/scd0 gnome-mount 0.6 --------------------------------------------------
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 467763 ***