GNOME Bugzilla – Bug 499107
crash in Email: e-mail receiving
Last modified: 2007-11-23 21:23:12 UTC
What were you doing when the application crashed? e-mail receiving 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 116568064 vsize: 116568064 resident: 27467776 share: 18362368 rss: 27467776 rss_rlim: 4294967295 CPU usage: start_time: 1195796600 rtime: 79 utime: 67 stime: 12 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 -1208817952 (LWP 6402)] [New Thread -1281361008 (LWP 6472)] [New Thread -1219654768 (LWP 6425)] (no debugging symbols found) 0x00b03402 in __kernel_vsyscall ()
+ Trace 179331
Thread 1 (Thread -1208817952 (LWP 6402))
----------- .xsession-errors --------------------- ~ScimInputContextPlugin() ScimInputContextPlugin() ~ScimInputContextPlugin() ScimInputContextPlugin() WARNING: please edit ~/.scim/global and change /DefaultConfigModule to kconfig X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2a00003 CalDAV Eplugin starting up ... ** (evolution:6402): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:6402): 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 (evolution:6402): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 --------------------------------------------------
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 ***