Hmm, this original bug was filed a month before 1.5.99.902 was released to precise, so it's kind of confusing to see it _fix_ the issue.. Or it was something else back then.
That said, there's probably something weird going on with the driver anyway, so would be great to know what upstream commit(s) broke it. I can't reproduce it myself.
Hmm, this original bug was filed a month before 1.5.99.902 was released to precise, so it's kind of confusing to see it _fix_ the issue.. Or it was something else back then.
That said, there's probably something weird going on with the driver anyway, so would be great to know what upstream commit(s) broke it. I can't reproduce it myself.