GNOME Bugzilla – Bug 469764
crash in Tasks: trying to get messages. ...
Last modified: 2007-08-24 00:44:23 UTC
Version: 2.10 What were you doing when the application crashed? trying to get messages. Have a message stuck in the out box. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 664875008 vsize: 664875008 resident: 342343680 share: 10301440 rss: 342343680 rss_rlim: 4294967295 CPU usage: start_time: 1187914138 rtime: 690 utime: 382 stime: 308 cutime:2 cstime: 8 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 -1208740128 (LWP 4023)] [New Thread -1236501616 (LWP 4098)] [New Thread -1296331888 (LWP 4081)] [New Thread -1246995568 (LWP 4050)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 157497
Thread 3 (Thread -1296331888 (LWP 4081))
----------- .xsession-errors (30 sec old) --------------------- (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files GLib-ERROR **: gmem.c:172: failed to allocate 1073741824 bytes aborting... CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:4023): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4023): 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 GLib-ERROR **: gmem.c:172: failed to allocate 1073741824 bytes aborting... Xlib: unexpected async reply (sequence 0x1623)! Xlib: sequence lost (0x100ed > 0x17d9) in reply type 0xe3! --------------------------------------------------
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 352284 ***