Comment 3 for bug 458306

No longer seems to be happening with acroread 9.1.0-7jaunty2, and the same X server version. I am retaining a copy of the older acroread package so that I can reproduce this. I think a reproducible client-induced lockup in the Karmic-released X server is a serious bug which should be investigated, even if not triggered by current packages. I assume that Bryce Harrington was able to reproduce this too, so it's not just my hardware.

I'm not familiar with the X protocol or how one would go about getting a trace of what the application is doing to cause this. But I'm happy to put some time in to help isolate a simple test case, if someone with more knowledge of these things could give me some pointers on how to get started.