Ok, thanks for the info.
In my case this behavior shows up immediately at the first virtual session startup, but maybe it is the same problem that you are looking at. I have tried a few times to move between 4.1.x and 4.2.x, and the problem is triggered for me when using 4.2.x. But of course that could be a number of reasons if you are certain that the problem always has been present.