On Thu, Aug 1, 2013 at 11:12 PM, Adam Williamson <span dir="ltr"><<a href="mailto:awilliam@redhat.com" target="_blank">awilliam@redhat.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On Thu, 2013-08-01 at 20:21 +0800, Morgan Howe wrote:<br>
> The latest mesa in the repos still does not solve this problem, so I<br>
> just wanted to bring it to the maintainer's attention that an update<br>
> for this package should probably be expedited.<br>
<br>
</div></div>We don't simply bump Mesa to bleeding-edge git on stable releases. It'll<br>
fix your bug, sure, but it could just as well break 2x as many things as<br>
it fixes...</blockquote><div> </div></div>I didn't say you need to bump it to bleeding edge git. I'm just letting you know that there's a pretty serious bug in the current version of mesa that is affecting at least a few people - probably even more who just rolled back to F18 and didn't bother filing a bug report. I'm well aware that a version bump might introduce new bugs, but just thought someone might want to consider at least looking into it since a completely broken X is a fairly major issue.<br>