Comment 5 for bug 795373

This one positively drives me nuts!
When I first started seeing it, I gave up using emacs-x. Instead, I have been running :emacs -nw" within a terminal. That works just fine.
Yesterday (Wed, 03 Aug), more or less by error, I typed "emacs" in the terminal. Behold! Up comes the X emacs display.
I tried it twice to verify that I had not imagined it. It was real.
Today, I tried it and it again crashes -- it takes my gdm session down with it and I need to log in again.

Here are a couple of other things I've tried.
Boot into Single mode.
type STARTX. Get the generic X-windows desktop.
Launch emacs.
IT WORKS!

Still in Single mode,
type GDM. Get a gdm greeter. Log in.
Launch emacs.
IT WORKS!

SO, this would seem to relate to something that may (or perhaps not) be running when in multi-user mode.

Next trick is to build a local emacs with debugging symbols and source, and try launching it in DDD. I don't have a lot of hope for that, because the stacktrace seems to indicate the SIGABRT originates in the GTK library.