If I start gvim (GUI version of vim) in a terminal I get an error message and gvim locks up. The message is: ---------------------------------------------------------------------- E852: The child process failed to start the GUI[xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. gvim: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. -------------------------------------------------------------------------- I can prevent it from happening, either by starting gvim with dmenu or by doing "gvim &" in a terminal. I think gvim normally starts as a child process from a terminal. Is this a bug? Any way of preventing the error apart from those I've mentioned/ -- Anthony Campbell - ac@acampbell.org.uk Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk - sample my ebooks at http://www.smashwords.com/profile/view/acampbell