This issue is still not fixed on 3.14.0-ubuntu1. When scanning I see the same behaviour as ametedinov describes in #8
This issue is still not fixed on 3.14.0-ubuntu1. When scanning I see the same behaviour as ametedinov describes in #8