abrt version: 1.1.18
Attached file: backtrace, 52803 bytes
Attached file: coredump, 124801024 bytes
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce
Created attachment 499836 [details]
Thanks for a bug report. I see couple other similar bugs crashing in XAllocID, but none matches this one close enough. I see from the backtrace that this happened in time of opening calendar view for the first time, but somewhere in gdk, when creating a cursor image. If you are able to reproduce this anyhow (though I recall this being rather occasional crash), then giving valgrind a chance to explain what happened with the memory might help to identify the issue. You can run evolution under valgrind like this, but note evolution will be significantly slower due to all memory checking:
$ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>evo.txt
Then you can examine the evo.txt and check whether it contains anything which will include functions like XAllocID or gdk_cursor_new or e_day_view_init.
Backtrace analysis found this bug to be similar to bug #705579, closing as duplicate. This bug seems to belong to component libX11, libXcursor or libXrender.
Bugs which were found to be similar to this bug:
emerald: bug #680592
gedit: bug #650406
gnome-scan: bug #609230
gnome-screensaver: bug #666451
nautilus: bug #543282, bug #545493, bug #574789, bug #576538, bug #601500, bug #614613, bug #633017, bug #705579
yelp: bug #587425, bug #618993
This comment is automatically generated.
*** This bug has been marked as a duplicate of bug 705579 ***