GNOME Bugzilla – Bug 513704
crash in Tasks:
Last modified: 2008-02-01 23:56:01 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.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 115740672 vsize: 115740672 resident: 39149568 share: 31797248 rss: 39149568 rss_rlim: 4294967295 CPU usage: start_time: 1201876579 rtime: 122 utime: 109 stime: 13 cutime:0 cstime: 3 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 -1208670496 (LWP 7941)] [New Thread -1247155312 (LWP 7971)] [New Thread -1236272240 (LWP 7960)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 187739
Thread 1 (Thread -1208670496 (LWP 7941))
----------- .xsession-errors --------------------- 0 QLayout "unnamed" added to QWidget "unnamed", which already has a layout [mpeg4 @ 0x10ec1a4]header damaged [mpeg4 @ 0x10ec1a4]header damaged [mpeg4 @ 0x10ec1a4]header damaged [mpeg4 @ 0x10ec1a4]header damaged [mpeg4 @ 0x10ec1a4]header damaged [mpeg4 @ 0x10ec1a4]header damaged [mpeg4 @ 0x10ec1a4]header damaged [mpeg4 @ 0x10ec1a4]header damaged CalDAV Eplugin starting up ... ** (evolution:7941): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:7941): 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 431459 ***