Comment 2 for bug 293970

I will add that leaving the desktop Framebuffer to a virtual terminal (alt f[1-5] all experience same problem) and then going back to desktop will leave the desktop in a 'hanged' state that requires killing hte X server and session.

There are no dbus process files in /tmp so maybe there's a path problem that needs to be updated with bonobo-activiation-server?

The only thing I found for configuration of the bonobo-activation-server was that it looks for (these are catalog files right?) OAF files in /usr/lib/bonobo/server
...
nnection refused
Nov 29 11:52:42 placid bonobo-activation-server (yositune-32138): could not associate with desktop session: Failed to connect to socket /tmp/dbus-9v8gtBkJpB: Connection refused
Nov 29 14:23:30 placid bonobo-activation-server (yositune-7795): could not associate with desktop session: Failed to connect to socket /tmp/dbus-gfE9RjH4U8: Connection refused
Nov 29 14:53:21 placid bonobo-activation-server (yositune-7867): could not associate with desktop session: Failed to connect to socket /tmp/dbus-aMdcG5qNSy: Connection refused