That sounds exactly like what happened. Curious combination of events
leading to failure.
And indeed, as in the previous report: it's nasty, because one cannot open
a terminal to fix it!
I have a minimal system (I wouldn't have been able to delete the lock
manually),
such that I was forced to reboot with emergency as a kernel line
parameter,chroot into my system and open a bash shell in order to fix it.

Arjen Rouvoet
*a.j.rouvoet@gmail.com <a.j.rouvoet@gmail.com>*
T: 06 - 19943967



On 23 June 2014 14:40, Axel Beckert <abe@deuxchevaux.org> wrote:

> Hi,
>
> On Mon, Jun 23, 2014 at 11:32:47AM +0200, Arjen Rouvoet wrote:
> > At that point I noticed the system time was messed up (propably by
> windows
> > usage). After syncing, zsh worked fine again with the original history
> file.
> >
> > I wonder if the history contained some timestamp in the future, which got
> > zsh confused. But in any case, I thought it was a bug worth mentioning.
>
> This sounds a lot like an issue (32574) reported back in April against
> zsh 5.0.5: http://www.zsh.org/mla/workers/2014/msg00363.html
>
>                 Kind regards, Axel
> --
> /~\  Plain Text Ribbon Campaign                   | Axel Beckert
> \ /  Say No to HTML in E-Mail and News            | abe@deuxchevaux.org
>  (Mail)
>  X   See http://www.nonhtmlmail.org/campaign.html | abe@noone.org
> (Mail+Jabber)
> / \  I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/
> (Web)
>