From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ulrich Mueller Newsgroups: gmane.emacs.devel Subject: Re: Emacs daemon dies at Xorg crash Date: Sat, 20 Dec 2008 19:35:04 +0100 Message-ID: <18765.15064.497113.969975@a1ihome1.kph.uni-mainz.de> References: <1229454957.21129.0.camel@localhost> <18760.56870.137654.853165@a1ihome1.kph.uni-mainz.de> <87k59yssad.fsf@cyd.mit.edu> <200812171708.mBHH8hPO008789@mothra.ics.uci.edu> <18761.21020.890676.865384@a1ihome1.kph.uni-mainz.de> <200812172251.mBHMp3ce010724@mothra.ics.uci.edu> <18762.15396.428952.119630@a1i15.kph.uni-mainz.de> <200812181914.mBIJE7qb013842@mothra.ics.uci.edu> <18762.51405.911216.76307@a1ihome1.kph.uni-mainz.de> <200812182249.mBIMnYK6014142@mothra.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1229798133 441 80.91.229.12 (20 Dec 2008 18:35:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 20 Dec 2008 18:35:33 +0000 (UTC) Cc: Chong Yidong , Diego Petteno , emacs-devel@gnu.org To: Dan Nicolaescu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 20 19:36:39 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LE6gm-0008EX-Oc for ged-emacs-devel@m.gmane.org; Sat, 20 Dec 2008 19:36:37 +0100 Original-Received: from localhost ([127.0.0.1]:41111 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LE6fa-000618-9B for ged-emacs-devel@m.gmane.org; Sat, 20 Dec 2008 13:35:22 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LE6fV-00060t-Sl for emacs-devel@gnu.org; Sat, 20 Dec 2008 13:35:17 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LE6fT-00060d-Di for emacs-devel@gnu.org; Sat, 20 Dec 2008 13:35:16 -0500 Original-Received: from [199.232.76.173] (port=60800 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LE6fT-00060a-AP for emacs-devel@gnu.org; Sat, 20 Dec 2008 13:35:15 -0500 Original-Received: from a1iwww1.kph.uni-mainz.de ([134.93.134.1]:37506) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LE6fS-0004A2-Sz for emacs-devel@gnu.org; Sat, 20 Dec 2008 13:35:15 -0500 Original-Received: from a1ihome1.kph.uni-mainz.de (a1ihome1.kph.uni-mainz.de [134.93.134.75]) by a1iwww1.kph.uni-mainz.de (8.14.0/8.13.4) with ESMTP id mBKIZ52k029149; Sat, 20 Dec 2008 19:35:06 +0100 Original-Received: from a1ihome1.kph.uni-mainz.de (localhost [127.0.0.1]) by a1ihome1.kph.uni-mainz.de (8.14.0/8.14.1) with ESMTP id mBKIZ5Kg007456; Sat, 20 Dec 2008 19:35:05 +0100 Original-Received: (from ulm@localhost) by a1ihome1.kph.uni-mainz.de (8.14.0/8.14.0/Submit) id mBKIZ4YO007450; Sat, 20 Dec 2008 19:35:04 +0100 In-Reply-To: <200812182249.mBIMnYK6014142@mothra.ics.uci.edu> X-Mailer: VM 8.0.2-487 under Emacs 22.2.1 (i686-pc-linux-gnu) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 1) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:107133 Archived-At: >>>>> On Thu, 18 Dec 2008, Dan Nicolaescu wrote: >> > Can you try the patch at: >> > http://permalink.gmane.org/gmane.emacs.bugs/22201 >> >> Tested and Emacs doesn't die anymore. I find the "Connection lost ..." >> message in the *Messages* buffer after reconnecting. > IMO that patch is good, but it fixes the effect in this case, not the > cause. Given where we are in the release process I'd like an OK from > one of the maintainers to check it in. The intention of that test in cmd_error_internal is clear from the comment before it, namely to exit if there's an error during initialisation or in batch mode (both not the case here): /* If the window system or terminal frame hasn't been initialized yet, or we're not interactive, write the message to stderr and exit. */ So, any reason why above patch cannot be checked in? Ulrich