Comment 21 for bug 401055

I've gone ahead and forwarded this upstream as an X bug, however really some additional analysis ought to be done. I don't think there's enough info on the upstream bug for us to be able to expect a response, but who knows, worth a shot I guess.

It would be helpful to narrow this to a test code that reproduces the problem. *Maybe* since firefox is so widely available they'll look at it, but most typically with these kinds of bugs upstream wants to see a concise test case.

It is also almost always a good idea to run the client app using xtrace in order to study the client-server interaction and see exactly what sequence of commands the client is sending to the server. Especially in this case I think it's extraordinarily likely upstream is going to ask for this to be done.