@enaijo
9 years, 7 months ago
Patch #8, as mentioned from danbp, solved the problem for me.
For me, the problem is introduced with 2.2.2, not solved …
