From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Killing a frame sometimes kills emacs Date: Wed, 31 Aug 2011 22:16:55 +0200 Message-ID: <87d3flnxoo.fsf@thinkpad.tsdh.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1314821831 9287 80.91.229.12 (31 Aug 2011 20:17:11 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 31 Aug 2011 20:17:11 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 31 22:17:04 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QyrDb-0003cp-69 for ged-emacs-devel@m.gmane.org; Wed, 31 Aug 2011 22:17:03 +0200 Original-Received: from localhost ([::1]:52793 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QyrDa-0000BD-9f for ged-emacs-devel@m.gmane.org; Wed, 31 Aug 2011 16:17:02 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:35070) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QyrDY-0000Az-EG for emacs-devel@gnu.org; Wed, 31 Aug 2011 16:17:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QyrDW-0005fK-MV for emacs-devel@gnu.org; Wed, 31 Aug 2011 16:17:00 -0400 Original-Received: from out3.smtp.messagingengine.com ([66.111.4.27]:40798) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QyrDW-0005fD-DG for emacs-devel@gnu.org; Wed, 31 Aug 2011 16:16:58 -0400 Original-Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8077B215F6 for ; Wed, 31 Aug 2011 16:16:57 -0400 (EDT) Original-Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 31 Aug 2011 16:16:57 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=from:to:subject:date:message-id :mime-version:content-type; s=smtpout; bh=AoRjIhPQQZQ3QzV1Wfjt17 83uSs=; b=A8ln2UnfLtRkPSBwQsLC1QYQ/gYd8bxympgVpfjTfCAtXyepeIFpPP nGYHrzkGN9NNM3cR0lSy0Mpb5/URuo/IS+mxb1qsfl+skkbwWMfVGI6w8RFxSH+c D8bJwZ8cFbav9yo0ZPpNxK+JxQxMO7Mqa9i59WUco9ofPDRMSCrtg= X-Sasl-enc: GB0jY5KD3SJgcf8cc+slIIHCfBhLJebBW3RH1Jgipv4x 1314821817 Original-Received: from thinkpad.tsdh.de (91-67-169-145-dynip.superkabel.de [91.67.169.145]) by mail.messagingengine.com (Postfix) with ESMTPSA id E213A96068A for ; Wed, 31 Aug 2011 16:16:56 -0400 (EDT) User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 66.111.4.27 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:143668 Archived-At: Hi all, since lately, I have a really annoying problem with the current emacs trunk. My current emacs is about 4 days old, but I've hit that problem already when I came back from holiday three weeks ago. The problem is that frequently, killing an emacs X11 frame kills the complete emacs instance. It doesn't crash or so, but it's just like if I had called `kill-emacs'. The usual steps are: 1. Start emacs (the server is activated from my .emacs) 2. Work for several hours without issues 3. emacsclient -c [maybe-a-file.txt] 4. kill the client frame with C-x 5 0, C-x #, or the X knob at the window decoration ==> BANG! Emacs is gone... My problem is that I'm totally unable to reproduce the issue. I've just tried to activate and use all packages/modes I usually work with (Gnus, Org, SLIME/Clojure, Elisp, AUCTeX, rcirc) step by step, but still creating and killing frames works as it's supposed to do. Do you have any suggestions on how to debug this issue? Bye, Tassilo