evolution crashing suddenly, repeatedly. "insufficient resources"

Scott R. Godin scott.g at mhg2.com
Sun Jul 9 07:24:06 UTC 2006


anyone have any ideas what could be causing this? I try and run it, and it 
flashes on the screen for all of less than a second, and then I get the message 
as the below.

3:12am {5} localhost:/home/webadmin>$ gdb evolution
GNU gdb Red Hat Linux (6.3.0.0-1.122rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db 
library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/evolution
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0x472000
[Thread debugging using libthread_db enabled]
[New Thread -1208789312 (LWP 9428)]
Detaching after fork from child process 9455.
[New Thread -1231877216 (LWP 9456)]

(evolution-2.6:9428): camel-WARNING **: camel_exception_get_id called with NULL 
parameter.
[New Thread -1242367072 (LWP 9457)]
[New Thread -1252856928 (LWP 9458)]
[Thread -1252856928 (LWP 9458) exited]
[New Thread -1252856928 (LWP 9459)]
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
The program 'evolution-2.6' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
   (Details: serial 971 error_code 11 request_code 53 minor_code 0)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error() function.)

Program exited with code 01.




More information about the fedora-list mailing list