From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 337 invoked by alias); 5 Jul 2017 03:46:19 -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: 41400 Received: (qmail 2495 invoked from network); 5 Jul 2017 03:46:18 -0000 X-Qmail-Scanner-Diagnostics: from out2-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(66.111.4.26):SA:0(-0.7/5.0):. Processed in 1.728992 secs); 05 Jul 2017 03:46:18 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at daniel.shahaf.name does not designate permitted sender hosts) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= daniel.shahaf.name; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=cHJn4B 6qIiOAPTkDdVQFD5UfYcqin7Acj6kWqitU+uY=; b=mZkvzKdFY8HKBUCpx94FsX jKsbtxczKzbjpmkJS7LFo72j4/2iyBu7TjeL93vvmVJ9Ev0/hXB55VqE9wHk4+yt dX0h/zO4NcayzRusA5nbwzstBzxSnYK6+F52MRaYSjqG6EOH6gzLx+eMl+YN75H6 +NrPtsOU4BHdQxEx7cN9JP8+h2KWsZ0Dzfb4UOG/jr48DO76dNM7nZ0uOj3Uqm89 pLn9htW3fhHLHn6FV7GRRxRaC58k70DmIR6Z5MTYDjZ7BkIaHWfEmljC5Xabkf1p xbD+FA3Gnvls6aHqHiXjM+h30Sswf5vSchGmbCWpcFn5YsAwFxzC5wohJGvwyxzw == DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=cHJn4B 6qIiOAPTkDdVQFD5UfYcqin7Acj6kWqitU+uY=; b=Xypts5iuRVeMn7PDR9+ity uq3JmG9D7+6sdd98y7cBVT3G/aCfuTj0r6aVR8MBua4isklOQpyuxjbFASnKMkUa 4Y3upyCwYSdIGC+MhLLKyLHn9mN+fSR2UR9x65Nsns7gy3Nc4EsDGQA/IUXeNeHR 7Oovh/GHM84zmrt2kthec4aThsU7OPBP27fe+Km1b6NILAS6SQVsXQ+nBh01AQqb w47/o3tjLvr1j8Z2wYzzVjYZ2IxIK5HC3LLTql4rH4BUrZuGMIceHkPmyvaKn5y5 5nwAEifBiaLA9BA8+4uylYbunFVa9HV95yq/xZ8oZC6GM0TVwWVOuXBhCCA84KYw == X-ME-Sender: Message-Id: <1499226004.1319542.1030633936.6F950F38@webmail.messagingengine.com> From: Daniel Shahaf To: zsh-workers@zsh.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-6c54a332 Subject: Re: Opening vim causes lockout In-Reply-To: Date: Wed, 05 Jul 2017 03:40:04 +0000 References: This should have gone to -users@ but I'll answer here to avoid splitting the thread. Steven Walton wrote on Tue, 04 Jul 2017 12:23 -0500: > I have an open stack exchange on this issue: > https://askubuntu.com/questions/931965/vim-takes-me-to-lockout-screen-zsh-error-possibly-x > First of all, your response to immediately reboot was wrong. You should have kept the working shells open so as to diff them to the broken shells. Fortunately this problem doesn't involve the boot loader or you'd have learnt this lesson the hard way. > My Problem: > When I type `vim` I get taken to my lockout screen. This happens without > fail. When I log back in I have my file open. I also randomly logout, but > this has only happened twice in the last hour. > Frankly, it sounds like you left your workstation unlocked and a coworker pulled a prank on you by changing your dotfiles. Depending on how skillful/vindictive they are, they may also have overwritten your 'which'. There is no command you can run inside zsh to rule this out. > I think this is connected to zsh because if I switch to bash I do not have > this problem.I am using antigen and oh-my-zsh but I moved my zshrc file and > opened a blank session and still have the problem. `which zsh` points to > `/usr/bin/zsh`. > But if I have to debug this on the assumption that it's a genuine problem: first of all, _which_ screen do you get --- the initial login screen (e.g., lightdm) or the screensaver screen (e.g., light-locker)? If it's the former, check syslog. (Run 'tail -f /var/log/{Xorg.log,messages,auth}' and 'journalctl -f' in screen or tmux --- you need to be root to tail /v/l/auth --- then reproduce the problem and see if there are any relevant messages.) > When being locked out my screens display "no signal" for a second. > Good luck, Daniel > Distributor ID: Ubuntu > Description: Ubuntu 16.04.2 LTS > Release: 16.04 > Codename: xenial