I confirm both the bug and the "-o nolock" workaround on a "fresh" Jaunty installation (as far as jaunty can be fresh installed...)
I confirm both the bug and the "-o nolock" workaround on a "fresh" Jaunty installation (as far as jaunty can be fresh installed...)