That was also the fix I applied on my instance long before there was a trouble ticket submitted for something similar to this.
