I can't reproduce this on a fresh install. Unless you know any different this bug can be closed.
On Fri, 18 Jan 2019 at 13:16 Peter Hull <peterhul...@gmail.com> wrote: > On Fri, Jan 18, 2019 at 12:25 PM Peter Hull <peterhul...@gmail.com> wrote: > > I can try and > > re-create a fresh install if that would help? > I tried a fresh install (still under VirtualBox) and it didn't have > this problem. So it may be nothing. I'll check my original one later > when I get back to that machine. >
