The problem is still present in Dapper as of 2006-03-26. Breezy doesn't have any problem running on the same machine, and I've found that mainline 2.6.15.6 works correctly.
Quoting the patch comment: "It fixed some machines, but seems to continually interact badly with some X versions. [...] So I think at this point, the best is that we keep the old bogus code that at least is consistent with the bug in the server."
This patch is included in the mainline 2.6.15 kernel. Why isn't applied in Dapper's one?
The problem is still present in Dapper as of 2006-03-26. Breezy doesn't have any problem running on the same machine, and I've found that mainline 2.6.15.6 works correctly.
Applying the patch from http:// www.kernel. org/git/ gitweb. cgi?p=linux/ kernel/ git/torvalds/ linux-2. 6.git;a= commitdiff; h=392c14beaca2e e85a98d0c6b4535 01be67423a20 (which reverts a previous buggy DRM change) on a rebuilt Dapper 2.6.15-19 kernel fixes the problem.
Quoting the patch comment: "It fixed some machines, but seems to continually interact badly with some X versions. [...] So I think at this point, the best is that we keep the old bogus code that at least is consistent with the bug in the server."
This patch is included in the mainline 2.6.15 kernel. Why isn't applied in Dapper's one?