From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?UTF-8?Q?Adam_Sj=C3=83=C2=B8gren_via_=22Emacs_development_discussions=2E?= Newsgroups: gmane.emacs.devel Subject: Re: long-standing GTK bug Date: Tue, 12 May 2020 09:57:15 +0200 Organization: koldfront - analysis & revolution, Copenhagen, Denmark Message-ID: <87d079io10.fsf@tullinup.koldfront.dk> References: <83zhbcg6s4.fsf@gnu.org> <87r1wng2ki.fsf@linaro.org> <83o8rrenn1.fsf@gnu.org> <87blnr6uck.fsf@tullinup.koldfront.dk> <87wo5kumkn.fsf_-_@tullinup.koldfront.dk> <86ftc5hc8j.fsf@gmail.com> Reply-To: =?UTF-8?Q?Reply-to=3A_Adam_Sj=C3=83=C2=B8gren_=3Casjo=40koldfront=2Edk=3E?= =?UTF-8?Q?=0A?= Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="79047"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) To: emacs-devel@gnu.org Cancel-Lock: sha1:4OuT9isHuIxYUNEC0PMLWTnwlH0= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 12 09:57:59 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jYPna-000KSs-Re for ged-emacs-devel@m.gmane-mx.org; Tue, 12 May 2020 09:57:58 +0200 Original-Received: from localhost ([::1]:54852 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jYPnZ-0001p8-UK for ged-emacs-devel@m.gmane-mx.org; Tue, 12 May 2020 03:57:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59408) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYPn5-0000zT-IP for emacs-devel@gnu.org; Tue, 12 May 2020 03:57:27 -0400 Original-Received: from ciao.gmane.io ([159.69.161.202]:33712) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jYPn2-00047i-EH for emacs-devel@gnu.org; Tue, 12 May 2020 03:57:27 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1jYPmz-000Jfr-Gm for emacs-devel@gnu.org; Tue, 12 May 2020 09:57:21 +0200 X-Injected-Via-Gmane: http://gmane.org/ OpenPGP: id=476630590A231909B0A0961A49D0746121BDE416; url=https://asjo.koldfront.dk/gpg.asc X-Face: )qY&CseJ?.:=8F#^~GcSA?F=9eu'{KAFfL1C3/A&:nE?PW\i65"ba0NS)97, Q(^@xk}n4Ou rPuR#V8I(J_@~H($[ym:`K_+]*kjvW>xH5jbgLBVFGXY:(#4P>zVBklLbdL&XxL\M)%T}3S/IS9lMJ ^St'=VZBR List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:249952 Archived-At: Hi Andres, andres.ramirez writes: > Which hints leads You from xterm.c to frame.c? I could not figure out why x_terminal_close() wasn't called when the last frame on a display was closed, and that lead me to frame.c. Took me a couple of evenings of adding a _lot_ of print-statements and experimenting. My original goal was to look into "the GTK bug", and this "^C hanging"/X-connection not being closed fell out of it as a bonus. > Adam> Ah, I've now read through the bugs referenced in the > Adam> comment, and it sounds like the problem that was handled by > Adam> adding this doesn't happen every time. When > Adam> x_delete_terminal() gets called much less, the described > Adam> crashes are less likely to happen. > > I have skimmed also the bugs referenced there. A lot of info and > situations. All of that cases would need retest. I don't know that any of those bugs are resolved, but I think the workaround was acknowledged to be just a workaround when it was added, so if the problems with the scrollbars can be solved, I think the workaround can be removed for Lucid/Motif builds. > Nice job. This bug affects a lot of emacs users. on 2016 I digged a > little bit on this bug aka "long-standing GTK bug". While related, this is not "the GTK bug", nor does it resolve it. If you remove the workaround in frame.c and remove the call to emacs_abort() when using GTK in x_connection_closed() in xterm.c, and the connection to a display is terminated while Emacs has a window on that display, you'll still get an endless stream of warnings from GLib, i.e. "the GTK bug". I've tried updating the latest issue on this in the GTK GitLab, to see if anyone has some clues: · https://gitlab.gnome.org/GNOME/gtk/-/issues/2315#note_795365 I haven't heard anything yet, and I would not be surprised if they still are cross with the Emacs community. Thanks for replying, I agree it would be really nice to get to the bottom of this long standing issue. Best regards, Adam -- "Ett, två, tre, pang på rödbetan." Adam Sjøgren asjo@koldfront.dk