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: Re: Killing a frame sometimes kills emacs Date: Thu, 01 Sep 2011 15:05:29 +0200 Message-ID: <87pqjk2z1i.fsf@thinkpad.tsdh.de> References: <87d3flnxoo.fsf@thinkpad.tsdh.de> <83fwkhdld0.fsf@gnu.org> <871uw04lr9.fsf@thinkpad.tsdh.de> <87sjog35jj.fsf@thinkpad.tsdh.de> <4E5F7ECD.9060601@swipnet.se> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1314882361 23494 80.91.229.12 (1 Sep 2011 13:06:01 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 1 Sep 2011 13:06:01 +0000 (UTC) Cc: Eli Zaretskii , Andreas Schwab , emacs-devel@gnu.org To: "Jan D." Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 01 15:05:56 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 1Qz6xv-0005LS-NA for ged-emacs-devel@m.gmane.org; Thu, 01 Sep 2011 15:05:55 +0200 Original-Received: from localhost ([::1]:36473 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qz6xu-0000TZ-Ua for ged-emacs-devel@m.gmane.org; Thu, 01 Sep 2011 09:05:54 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:42514) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qz6xn-0000Mp-Hg for emacs-devel@gnu.org; Thu, 01 Sep 2011 09:05:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qz6xj-0002VS-Ha for emacs-devel@gnu.org; Thu, 01 Sep 2011 09:05:47 -0400 Original-Received: from deliver.uni-koblenz.de ([141.26.64.15]:58903) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qz6xh-0002P1-JM; Thu, 01 Sep 2011 09:05:41 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by deliver.uni-koblenz.de (Postfix) with ESMTP id 2C0A5D235E; Thu, 1 Sep 2011 15:05:32 +0200 (CEST) X-Virus-Scanned: amavisd-new at uni-koblenz.de Original-Received: from deliver.uni-koblenz.de ([127.0.0.1]) by localhost (deliver.uni-koblenz.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XVoIs6T1vVpq; Thu, 1 Sep 2011 15:05:31 +0200 (CEST) X-CHKRCPT: Envelopesender noch thorn@fastmail.fm Original-Received: from thinkpad.tsdh.de (tsdh.uni-koblenz.de [141.26.67.142]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by deliver.uni-koblenz.de (Postfix) with ESMTPSA id E47EDD2359; Thu, 1 Sep 2011 15:05:30 +0200 (CEST) User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 141.26.64.15 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:143688 Archived-At: "Jan D." writes: >>> Isn't that the known gtk bug with multiple displays? >> >> As said in the reply to Eli, I don't have multiple displays. There's >> only one X instance in which emacs runs with exactly one X11 frame. >> Then I invoked "emacsclient -c" to get another X11 frame, and closing >> that made emacs crash. > > From Emacs point of view, localhost:0 and unix:0 and :0 are three > different displays, even if they physically are the same. > > Try doing the same and after you clicked the link in chromium, evaluate > (x-display-list). If you have more than one entry, it is the Gtk+ problem. Indeed, after opening a new emacs frame from chromium, I have two entries: (":0.0" ":0"). Before that, it was only (":0.0"). But still, since all other apps somehow spawning new emacs frames don't create this problem, I wonder if chromium does something special. I've checked its sources, and eventually it'll call something like XDGUtil("xdg-open", "path/to/file.txt"); You can check that function here: http://codesearch.google.com/codesearch#OAMlx_jo-ck/src/chrome/browser/platform_util_linux.cc&l=17 That in turn calls LaunchProcess() http://codesearch.google.com/codesearch#OAMlx_jo-ck/src/base/process_util_posix.cc&l=531 Bye, Tassilo