GNOME Bugzilla – Bug 473435
crash in Tasks: Opening Evolution.surfin...
Last modified: 2007-09-04 22:58:39 UTC
What were you doing when the application crashed? Opening Evolution.surfing net in firefox Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 140070912 vsize: 140070912 resident: 25362432 share: 17289216 rss: 25362432 rss_rlim: 4294967295 CPU usage: start_time: 1188878807 rtime: 114 utime: 104 stime: 10 cutime:1 cstime: 1 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 -1208412448 (LWP 7723)] [New Thread -1231217776 (LWP 7753)] [New Thread -1241707632 (LWP 7743)] (no debugging symbols found) 0x0038b402 in __kernel_vsyscall ()
+ Trace 160290
Thread 1 (Thread -1208412448 (LWP 7723))
----------- .xsession-errors (7 sec old) --------------------- JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] CalDAV Eplugin starting up ... ** (evolution:7723): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:7723): DEBUG: mailto URL program: evolution (evolution:7723): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:7723): camel-WARNING **: camel_exception_get_id called with NULL parameter. --------------------------------------------------
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 ***