This bug appears to have been fixed by the latest gdm3 (3.18.0-2) to hit testing. Perhaps related to the removal of the special .session file? Thanks Stuart