I have built a fairly recent git snapshots of -intel that you can grab
here for testing:

http://people.ubuntu.com/~bryce/bisect/

If it does resolve the issue, it would be helpful if you could check
some of the versions between Hardy/2.2.1-1ubuntu5 and 2.2.99.901 on that
page, as this will help narrow down which patch may have solved it.  We
can then pull that patch in for Hardy.

Also, in your description you said it didn't occur with vesa "(or at
least very rarely)".  If testing the latest git deb of the -intel driver
doesn't make the issue go away, could you test on -vesa more and see if
you can definitively determine whether the issue occurs with -vesa too?
If it does, then it may not be a driver issue after all, and may instead
be a hardware, kernel, or xserver problem.

We have libpciaccess in Ubuntu, in the Universe repository.  We build
the Ubuntu packages with that disabled for now.  We'll probably get it
into main for Intrepid and start making it a build-time dependency like
Debian does.

-- 
Display corruption in VTs on Intel 855GME
https://bugs.launchpad.net/bugs/210600
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to