Based on the last comment, I had a look on the code. I can not check the issue myself, so could any affected user check whether the attached patch on trunk solves this issue?
Based on the last comment, I had a look on the code.
I can not check the issue myself, so could any affected user check whether the attached patch on trunk solves this issue?