GNOME Bugzilla – Bug 448439
crash in Calendar: set my email account
Last modified: 2007-06-17 23:13:29 UTC
What were you doing when the application crashed? set my email account 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 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: 164642816 vsize: 164642816 resident: 45027328 share: 25862144 rss: 45027328 rss_rlim: 4294967295 CPU usage: start_time: 1182074293 rtime: 708 utime: 648 stime: 60 cutime:160 cstime: 22 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209186592 (LWP 4420)] [New Thread -1378706544 (LWP 615)] [New Thread -1389196400 (LWP 307)] [New Thread -1243944048 (LWP 21745)] [New Thread -1357726832 (LWP 4472)] (no debugging symbols found) 0x008be402 in __kernel_vsyscall ()
+ Trace 141614
Thread 1 (Thread -1209186592 (LWP 4420))
----------- .xsession-errors (45 sec old) --------------------- (evolution:4420): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) BBDB spinning up... (evolution:4420): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa870018' (evolution:4420): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa870138' (evolution:4420): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:4420): camel-pop3-provider-WARNING **: Bad server response: \xce\xa8\xb5\xc7¼\xa3\xa1\xd3\xca\xcf\xe4\xc3\xfb/\xc3\xdc\xc2\xeb\xca\xe4\xc8\xeb\xb4\xed\xce
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 426227 ***