Comment 7 for bug 1238410

On the same machine with a new 14.04 install this does not occur though still an issue with the 13.10 install
The 13.10 was installed on 10/04 so possibly a new 13.10 release install would be fine, I've no inclination to try as 13.10 is relatively unimportant