GNOME Bugzilla – Bug 510761
crash in Tasks:
Last modified: 2008-01-20 19:53:32 UTC
Version: 2.10 What were you doing when the application crashed? 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 134352896 vsize: 134352896 resident: 38191104 share: 31481856 rss: 38191104 rss_rlim: 4294967295 CPU usage: start_time: 1200826861 rtime: 74 utime: 64 stime: 10 cutime:0 cstime: 2 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 -1208326432 (LWP 3489)] [New Thread -1245713520 (LWP 3516)] [New Thread -1235223664 (LWP 3511)] [New Thread -1223500912 (LWP 3510)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 186050
Thread 1 (Thread -1208326432 (LWP 3489))
----------- .xsession-errors --------------------- AFD changed from -2 to -1 AFD changed from -2 to -1 AFD changed from -2 to -1 [mjpeg @ 0x10fc1a4]mjpeg: unsupported coding type (c6) [mjpeg @ 0x10fc1a4]mjpeg: unsupported coding type (c1) [mjpeg @ 0x10fc1a4]picture size invalid (29632x41789) [mjpeg @ 0x10fc1a4]mjpeg: unsupported coding type (c7) [mjpeg @ 0x10fc1a4]dqt: 16bit precision [mjpeg @ 0x10fc1a4]mjpeg: unsupported coding type (ce) [mjpeg @ 0x10fc1a4]mjpeg: unsupported coding type (c8) CalDAV Eplugin starting up ... ** (evolution:3489): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3489): 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 ***