nurupo Sun, 10 Dec 2017 18:49:11 -0800
Looks like this bug got resolved. Had the same issue before, but it got fixed in the latest (4:17.08.3-1) version of the package.
