Comment 16 for bug 716433

abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: evolution -c mail --sync
component: evolution
crash_function: raise
executable: /usr/bin/evolution
global_uuid: 6f27b1bde132b66c0cb0916f3aa4d685a8a00814
kernel: 2.6.33.5-112.fc13.i686.PAE
package: evolution-2.30.1-6.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

comment
-----
Evloution dies with the message:

Gdk-ERROR **: The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 1919308 error_code 13 request_code 60 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.)
aborting...

when run with --sync it prints out

[alx@aronia ~]$ (evolution:11072): e-data-server-DEBUG: Loading categories from "/home/alx/.evolution/categories.xml"
(evolution:11072): e-data-server-DEBUG: Loaded 47 categories

** (evolution:11072): CRITICAL **: categories_icon_theme_hack: assertion `filename != NULL && *filename != '\0'' failed
evolution: xcb_io.c:452: _XReply: Assertion `!dpy->xcb->reply_data' failed.

[1]+ Aborted (core dumped) evolution --sync -c mail

How to reproduce
-----
1. Run evolution
2. Change view to Calendar
3.