GNOME Bugzilla – Bug 481482
crash in Tasks:
Last modified: 2007-10-01 13:46:26 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.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 114073600 vsize: 114073600 resident: 35086336 share: 28409856 rss: 35086336 rss_rlim: 4294967295 CPU usage: start_time: 1191030941 rtime: 83 utime: 73 stime: 10 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 -1208498464 (LWP 3667)] [New Thread -1271628912 (LWP 3701)] [New Thread -1261139056 (LWP 3700)] [New Thread -1218876528 (LWP 3675)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 166315
Thread 1 (Thread -1208498464 (LWP 3667))
----------- .xsession-errors (8 sec old) --------------------- Trying to dispose element fakesink, 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:3352): GStreamer-CRITICAL **: Trying to dispose element fakesink, 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. CalDAV Eplugin starting up ... ** (evolution:3667): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3667): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files --------------------------------------------------
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 ***