Thanks for the speedy replies. I guess my next question is - can someone recompile xorg and narrow the problem patch down? If people want a blind guess as to which patch it was I'd go with 132:
The original report says that Xorg worked in the Gutsy tribe 3 release. According to http://cdimage.ubuntu.com/releases/gutsy/tribe-3/ this was release on the 17th-18th July. By 4th August the breakage had arrived. Using the i386 alternate CD's file list (the desktop CDs file list seems very small and might be broken) we can tell that xserver-xorg- core_1.3.0.0.dfsg-6ubuntu2_i386.deb was what was shipped. Looking at the original reporter's xorg output we can tell the broken xorg was built on 26th July. Using the changelog on http://changelogs.ubuntu.com/changelogs/pool/main/x/xorg-server/xorg- server_1.3.0.0.dfsg-12ubuntu3/changelog the first August xorg build is apparently 2:1.3.0.0.dfsg-12 (it's a pity the reporter didn't include a xorg package version number in the original report, nor did xorg mention the package version number in its log). I'd guess the problem patch was made (strictly) between the xserver- xorg-core_1.3.0.0.dfsg-6ubuntu2_i386.deb and 2:1.3.0.0.dfsg-12 releases. The dates in the changelog around July are a bit funny though. The only patch from then that seems to be in an area that would affect this bug is debian/patches/132_composite-no-clipping.diff which is why I would start around there. This is pure speculation though. -- [nvidia-glx-new] glxgears, 3d apps crash X when using compiz-fusion (gutsy) https://bugs.launchpad.net/bugs/130325 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
