From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?ISO-8859-1?Q?Jan_Dj=E4rv?= Newsgroups: gmane.emacs.devel Subject: Re: emacs --daemon and GDK default display Date: Mon, 23 Mar 2009 18:09:36 +0100 Message-ID: <49C7C250.9030505@swipnet.se> References: <18879.34340.349741.391197@a1ihome1.kph.uni-mainz.de> <49BF8DD5.2030502@gnu.org> <18887.22064.669003.766051@a1i15.kph.uni-mainz.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1237828212 28742 80.91.229.12 (23 Mar 2009 17:10:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 23 Mar 2009 17:10:12 +0000 (UTC) Cc: emacs-devel@gnu.org, Jason Rumney To: Ulrich Mueller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 23 18:11:28 2009 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 1LlngJ-00083a-IN for ged-emacs-devel@m.gmane.org; Mon, 23 Mar 2009 18:11:23 +0100 Original-Received: from localhost ([127.0.0.1]:58300 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Llnew-0005Rz-Nt for ged-emacs-devel@m.gmane.org; Mon, 23 Mar 2009 13:09:58 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Llnen-0005Oh-46 for emacs-devel@gnu.org; Mon, 23 Mar 2009 13:09:49 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Llneg-0005Lf-9z for emacs-devel@gnu.org; Mon, 23 Mar 2009 13:09:48 -0400 Original-Received: from [199.232.76.173] (port=41923 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Llneg-0005Lb-2n for emacs-devel@gnu.org; Mon, 23 Mar 2009 13:09:42 -0400 Original-Received: from proxy3.bredband.net ([195.54.101.73]:40398) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Llned-00050Q-BZ; Mon, 23 Mar 2009 13:09:39 -0400 Original-Received: from ironport.bredband.com (195.54.101.120) by proxy3.bredband.net (7.3.139) id 49C0B9D7001E9097; Mon, 23 Mar 2009 18:09:38 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgEvAINfx0lV4S1uPGdsb2JhbACBUJQXAQEBATW8X4N+Bg X-IronPort-AV: E=Sophos;i="4.38,409,1233529200"; d="scan'208";a="498362350" Original-Received: from c-6e2de155.25-1-64736c10.cust.bredbandsbolaget.se (HELO coolsville.localdomain) ([85.225.45.110]) by ironport1.bredband.com with ESMTP; 23 Mar 2009 18:09:38 +0100 Original-Received: from c-89-160-50-208.cust.bredband2.com (c-89-160-50-208.cust.bredband2.com [89.160.50.208]) by coolsville.localdomain (Postfix) with ESMTPSA id 33C527FA07B; Mon, 23 Mar 2009 18:09:37 +0100 (CET) User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) In-Reply-To: <18887.22064.669003.766051@a1i15.kph.uni-mainz.de> X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:109792 Archived-At: Ulrich Mueller skrev: >>>>>> On Tue, 17 Mar 2009, Jason Rumney wrote: >>> While I think that the blame is with libcanberra, I'm confused >>> about the fact that the segfault only happens during the second >>> request from a client. Does it mean that there is a GDK default >>> display at the time of the first request, but not for the second >>> one? Why? > >> Just a guess without looking at libcanberra, but could the bug be >> that libcanberra remembers the default display created during the >> first request and tries to reuse it after it is closed? > > It doesn't remember it. libcanberra just calls a GTK function, which > in turn asks the GDK display manager for the default display. And that > returns a valid display for the first request, but a null pointer for > the second one. > If I remember correctly, the display manager does not set a new default display when the old is closed. There is some code for that case i gtkutil.c. But there was a bug in it. I don't know if that fixes anything, but please try again. Note that closing displays under Gtk+ is generally buggy in itself. If you can capture a stack trace in the debugger we should be able to tell if it is Gtk+ or Emacs that is doing the wrong thing. Jan D.