GNOME Bugzilla – Bug 489166
crash in Tasks: i send/recive mail
Last modified: 2007-10-22 22:39:28 UTC
Version: 2.10 What were you doing when the application crashed? i send/recive mail 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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 248811520 vsize: 248811520 resident: 71155712 share: 62656512 rss: 71155712 rss_rlim: 4294967295 CPU usage: start_time: 1193087369 rtime: 67 utime: 56 stime: 11 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 -1208899872 (LWP 10607)] [New Thread -1393820784 (LWP 10643)] [New Thread -1290458224 (LWP 10629)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 172053
Thread 1 (Thread -1208899872 (LWP 10607))
----------- .xsession-errors (198320 sec old) --------------------- (brasero:28929): GStreamer-WARNING **: Failed to load plugin '/usr/lib/gstreamer-0.10/libgstamrnb.so': libamrnb.so.0: cannot open shared object file: No such file or directory Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3600003 specified for 0x360149d (Burning DV). [00000291] main playlist: nothing to play [00000291] main playlist: nothing to play gnome-mount 0.6 Ejected /dev/scd0 gnome-mount 0.6 ** (gnome-mount:29606): WARNING **: Drive /dev/scd0 does not contain media. Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3600003 specified for 0x36642db (Burning DV). gnome-mount 0.6 Ejected /dev/scd0 [00000291] main playlist: stopping playback ...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 364700 ***