I can also verify that the patch in comment#28 fixed my issue. Thanks for your energy in tracking this down!
I can also verify that the patch in comment#28 fixed my issue. Thanks for your energy in tracking this down!