Comment 3 for bug 91818

This is reproducible for me at the moment. I should also mention that it's the gdb child process that spins, using 100% of cpu. I can recover by either killing that process, or restarting gdm as a whole.

Here's my X log in case it helps.