Comment 19 for bug 287542

Fascinating. There's something weirder going on here, and it may
actually be the X server's fault.

So, vinagre was working fine for me, and then I rebooted into
"recovery mode" and selected "fix X server" (even though my X server
was working fine; I was testing something else…), and it was after
doing that that vinagre stopped working, even though I didn't make the
connection at the time. This occurred to me yesterday when another
program, mupen64plus (not in Ubuntu --
http://code.google.com/p/mupen64plus/) crashed with the exact same X
error.)

When that happened, I got suspicious and swapped in the X config from
before the "fix X server" (automatically backed up in /etc/X11/), and
now all three VNC viewers, as well as mupen64plus, work fine. I'm
attaching both X configs in the hope that someone else can figure
something out.

- Nelson