On Mon, 2009-03-09 at 15:33 -0400, Al Dunsmuir wrote: > I would point out the potential trap with leaving something broken for > a long time, and relying on widely published workarounds. It can reduce > the likelyhood of many of the folks affected ever testing the fixes when > they do arrive. In my experience, a significant number of folks will > leave things in the working state until they next do a fresh install of > a subsequent release on that box. If they simply update, the workaround > might well continue to be used for the life of that box. I agree - I'm mainly suggesting this for the diagnostic value, which is why I asked that the info be added to the bug report. If changing the acceleration method fixes the problem, then the developers know the issue is likely in the EXA code somewhere. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
