Comment 8 for bug 1540553

I tried today from a live Ubuntu 16.04 environment for a shorter amount of time, this time with the right bitness and Chrome version 50. I still cannot reproduce the issue.

I noticed that this issue is most easily reproduced when I try and launch Chrome as soon as possible after booting up. This is difficult to reproduce on a live environment as I have to first download and install the package.