On Tue, Dec 08, 2009 at 12:46:19PM +0200, Vitaliy wrote: > Thanks guys for the answers! > > > There was a recomendation on this list to not use 1.7.2 and use 1.7.3 > > instead. > > Russ > > > This issue still presents in 1.7.3 unfortunately. > > > >Vitali - if it didn't occur in 1.7.1 but it does in 1.7.2/3, please > >bisect > > to find the patch that caused the regression. there's only a relatively > > small number of changes, so it should be easy enough to find. > > > > Cheers, > > Peter > > > > I am a new at this codding staff etc:D Would be hard for me to determine > what caused it. > > I will post your answer on the archlinux forum and its bug report, > probably someone knows what to do. > http://bbs.archlinux.org/viewtopic.php?id=86026&p=2 > http://bbs.archlinux.org/viewtopic.php?id=86026&p=2 > > If you have some more ideas please let me know! the short answer is:
git clone git://anongit.freedesktop.org/git/xorg/xserver git checkout -b server-1.7-branch origin/server-1.7-branch ./autogen.sh --prefix=/usr make && make install # see below git bisect start git bisect bad xorg-server-1.7.3 git bisect good xorg-server-1.7.1 make && make install, followed by a test and a "git bisect good" or "git bisect bad" depending on whether the issue occurs. eventually that'll result in a "bad commit". you'll need the xorg development packages installed to be able to build the server and it's best to use the same configure flags for autogen.sh that archlinux uses to build its packages. this is the tricky bit, once you manage to get the server working from git, the bisecting is the easy part :) Cheers, Peter _______________________________________________ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
