to:
"
I think this is fixed in the 3.1.19 drivers
"