GNOME Bugzilla – Bug 506038
crash in Tasks: Running Firefox
Last modified: 2007-12-28 22:39:57 UTC
Version: 2.10 What were you doing when the application crashed? Running Firefox 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.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 132083712 vsize: 132083712 resident: 39149568 share: 30773248 rss: 39149568 rss_rlim: 4294967295 CPU usage: start_time: 1198838876 rtime: 54 utime: 48 stime: 6 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 -1208318240 (LWP 9098)] [New Thread -1286718576 (LWP 9122)] [New Thread -1231623280 (LWP 9116)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 183307
Thread 1 (Thread -1208318240 (LWP 9098))
----------- .xsession-errors --------------------- localuser:john being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3056 CalDAV Eplugin starting up ... ** (evolution:3271): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3271): DEBUG: mailto URL program: evolution BBDB spinning up... (evolution:3271): e-data-server-DEBUG: Loading categories from "/home/john/.evolution/categories.xml" (evolution:3271): e-data-server-DEBUG: Loaded 30 categories CalDAV Eplugin starting up ... index:0 restoring draft flag 'text/plain' index:0 CalDAV Eplugin starting up ... ** (evolution:9098): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:9098): DEBUG: mailto URL program: evolution --------------------------------------------------
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 ***
*** Bug 506039 has been marked as a duplicate of this bug. ***