From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16529 invoked by alias); 23 Jun 2014 12:58:21 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32788 Received: (qmail 8708 invoked from network); 23 Jun 2014 12:58:09 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,FREEMAIL_REPLY,HTML_MESSAGE, RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=fAGsMPTqqB6DoOnIxA5NOvpTFsvn4bbqcv4CneENA0I=; b=Tr4BOnawIIeXuP0pfnX5JRPrI5m6HsV3n8rwIHR2uR/HVlHTRQUjii5p2kY4J/hSNk rgZP5s1OiKsBXR3NzQch4A3SNnIj7VHlZS4l30Jsvj0EPNGJSrebdKEYbaBzFVcHZfAR QkIcWxtZrTVZS3TbzED/7ykwNLfuMM7w0pKOHsvEsvGmD9C6iW+ZM5pve//xGxb2NWZF Nr3TS89zfPaM+z5GMkgupJ2SZ1snTx/sGIkxx+HzyGahoTqpFneoJI941UIBwMupYVp/ nClkhxsY2zZhbHr4tJTrv9YQr3hWLTY9BFSmlov4UDzjbXlKLVLobH+czsv5Bt0Huxno LLXQ== X-Received: by 10.194.237.135 with SMTP id vc7mr9728328wjc.86.1403528285565; Mon, 23 Jun 2014 05:58:05 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20140623124027.GD5355@sym.noone.org> References: <20140623124027.GD5355@sym.noone.org> From: Arjen Rouvoet Date: Mon, 23 Jun 2014 14:57:45 +0200 Message-ID: Subject: Re: BUG: ZSH freezes (on history) when systime is wrong To: zsh-workers@zsh.org Content-Type: multipart/alternative; boundary=089e01494148e4bc4e04fc806491 --089e01494148e4bc4e04fc806491 Content-Type: text/plain; charset=ISO-8859-1 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 * T: 06 - 19943967 On 23 June 2014 14:40, Axel Beckert 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) > --089e01494148e4bc4e04fc806491--