Description of problem:
Probably the server component of eekboard was not running and the eekboard sent a lot of dbus messages. As I started eekboard-servers tose messages were delivered to the eekboard-server,  a lot of keyboard dialogs opened. During this torture, an msd-locate-pointer process got involved and produced a core dump.

Version-Release number of selected component:
mate-settings-daemon-1.5.4-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/msd-locate-pointer
crash_function: handle_error
executable:     /usr/libexec/msd-locate-pointer
kernel:         3.6.10-4.fc18.x86_64
uid:            303
xsession_errors: 

Truncated backtrace:
Thread no. 1 (8 frames)
 #4 handle_error at xcb_io.c:212
 #5 handle_response at xcb_io.c:324
 #6 _XEventsQueued at xcb_io.c:363
 #7 XPending at Pending.c:55
 #8 gdk_check_xpending at gdkevents-x11.c:159
 #9 gdk_event_check at gdkevents-x11.c:2378
 #10 g_main_context_check at gmain.c:3169
 #13 gtk_main at gtkmain.c:1257