The latest upstream release 6.3.0 and 6.3.1 have this actually fixed, so once the next version trickles in, this bug is resolved. Sebastian Spaeth