On Friday 25 October 2002 02:38 am, Lionel Ulmer wrote:
Grmbl, I must have missed that case when I submitted my fix last time (I only did it in the actual DGA2 usage, not in the 'probing' code).
No need to Grmbl! it was no sweat to fix and disabling dga in the config is a usable workaround until a patch goes in to cvs.
The actual root cause is (for me), a 'feature' in the X server that, instead of reporting the extension as missing on remote clients, report it as being present but then send error messages when trying to use it.
This makes sense; I saw the problem over ssh.