GNOME Bugzilla – Bug 452459
crash in Email: first start
Last modified: 2007-06-30 15:25:43 UTC
What were you doing when the application crashed? first start 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 94892032 vsize: 94892032 resident: 22462464 share: 14446592 rss: 22462464 rss_rlim: 4294967295 CPU usage: start_time: 1183179052 rtime: 89 utime: 72 stime: 17 cutime:1 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 -1208994080 (LWP 16619)] (no debugging symbols found) 0x00fd3402 in __kernel_vsyscall ()
+ Trace 144779
Thread 1 (Thread -1208994080 (LWP 16619))
----------- .xsession-errors (11 sec old) --------------------- ** (nautilus:3217): WARNING **: Hit unhandled case 38 (Сервис недоступен) in fm_report_error_loading_directory --- Hash table keys for warning below: --> file:///home/miwa (nautilus:16083): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) ** (nautilus:3217): WARNING **: Hit unhandled case 46 (Время ожидания истекло) in fm_report_error_loading_directory ** (nautilus:3217): CRITICAL **: nautilus_view_get_selection: assertion `NAUTILUS_IS_VIEW (view)' failed ** (nautilus:3217): WARNING **: Hit unhandled case 38 (Сервис недоступен) in fm_report_error_loading_directory CalDAV Eplugin starting up ... ** (evolution:16619): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:16619): DEBUG: mailto URL program: evolution --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 425129 ***