From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Bjoern Bidar via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#56967: 29.0.50; Frequent crashes under Wayland Date: Mon, 08 Aug 2022 11:56:19 +0300 Message-ID: <2062339.XFdaHZJ8Qi@odin> References: <1932596.zmb9SnqgO4@odin> <20004002.VVDfsmh7uS@odin> <875yj3sbj5.fsf@yahoo.com> Reply-To: Bjoern Bidar Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19002"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56967@debbugs.gnu.org To: Po Lu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Aug 08 10:57:43 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1oKyZz-0004lz-5d for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 08 Aug 2022 10:57:43 +0200 Original-Received: from localhost ([::1]:47112 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oKyZy-0003uw-3E for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 08 Aug 2022 04:57:42 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56508) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oKyZK-0003sP-Ic for bug-gnu-emacs@gnu.org; Mon, 08 Aug 2022 04:57:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49428) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oKyZK-0001a5-9g for bug-gnu-emacs@gnu.org; Mon, 08 Aug 2022 04:57:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oKyZK-0007B2-5Y for bug-gnu-emacs@gnu.org; Mon, 08 Aug 2022 04:57:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Bjoern Bidar Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 08 Aug 2022 08:57:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56967 X-GNU-PR-Package: emacs Original-Received: via spool by 56967-submit@debbugs.gnu.org id=B56967.165994899027538 (code B ref 56967); Mon, 08 Aug 2022 08:57:02 +0000 Original-Received: (at 56967) by debbugs.gnu.org; 8 Aug 2022 08:56:30 +0000 Original-Received: from localhost ([127.0.0.1]:39177 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oKyYn-0007A5-LO for submit@debbugs.gnu.org; Mon, 08 Aug 2022 04:56:30 -0400 Original-Received: from thaodan.de ([185.216.177.71]:58844) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oKyYk-00079o-RS for 56967@debbugs.gnu.org; Mon, 08 Aug 2022 04:56:28 -0400 Original-Received: from odin.localnet (dsl-trebng12-b04885-76.dhcp.inet.fi [176.72.133.76]) by thaodan.de (Postfix) with ESMTPSA id 57EDAD0374A; Mon, 8 Aug 2022 11:56:20 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=thaodan.de; s=mail; t=1659948980; bh=bP7H6sDzcwltsTt9FLmv9RZEvQoik1m9MIH0Q+IkD7c=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=lpaTxH70iugI7wt08YuzPq0vJn7KfEENI96knG+5dRshANIl+fxD5rdl716mT1DTf L2jmu8ARYU82Mh7HQikcOvqONw62tbN7wdQbfYwY5CG9xOm/clEue2QM/zcgiPEP4Z QjvSv++VpDPeo0FONr9eCuAuMyevZ2+FAvuDLlXVzfOI37MATSIW2QVpkbalg8uWbd EqEP0FNCEAD5qshHUqfa3qOIbxmgwGeUtaafROeS70jO1mDKU/qHviLQht6j/PeFJi ftsf7Pq7Er59XZKyfKgzuwHnSHkMAdHlOSkMLbUP7EnExr8Kir03BJirs68V6vhT+9 HowSmr96MrW5kUI1VGpIUstHJN2r8XjCo6Mib9iXGKUczH7aGgr1YNq1XS+Gorjesx 3+uS2szDkqsCsJ1t0kjiKli+u4Nj7db32Z8Kg9NzUwPZ+Xu7FakipRL84cD8w7YdRr TQQ73beL/ihUW1cGFKwVhEMnHX3d6IfveylJIrmKeJBEStwNNJMdnVqGEvv8NXPQKE diG+u2sEvIZfgO7iDQseMiWNClS7Da5GyyEsz6L4M+xt454rC3SeaE5FudaeYzGH4S YzUs/PmUZNPF+gv7GGsRmh2Iu1pqMOxt0ZUemi/Y9gDDv0KkRXHYPc3ctAm8wYLdyh FsbRB+pfGvaD8+GVqdiU2OHM= In-Reply-To: <875yj3sbj5.fsf@yahoo.com> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:239103 Archived-At: Am Montag, 8. August 2022, 05:40:30 EEST schrieb Po Lu: > Bjoern Bidar writes: > > I did I had my hole session running, nothing else had that issue. > > I kept the GTK-Demo running nothing happened it ran just fine. >=20 > Thanks. >=20 > > After a few hours Emacs exited with the same behaviour as explained in = the > > bug. >=20 > Do you see the same if you run Emacs as something other a daemon? >=20 > > I on the #gtk channel on what do and I got from ebassi that it is ok to > > just call _exit. > > He says it might be the client behaving wrong: > > Thaodan: It could happen because the client made an invalid > > request=E2=80=94 Wayland mandates that the display server closes the co= nnection > > in that case > We don't make raw Wayland requests anywhere, so it must be a bug in GTK. What could be the way that GTK is used or is emacs with pgtk 99% a run of t= he=20 mill gtk app? > > And if you lose the socket then you' > > you'll have to find the new one and reconnect > > Thaodan: Only emacs does that > > Pretty much literally > > "that"? > > "app may run longer or before the compositor starts" > > Because emacs is really a 1980s teletype app > > What does that change? calling _exit is not a solution. > > Lets assume the fault for this happening is emacs, what could > > cause this? >=20 > Outdated information. The PGTK port of Emacs doesn't do anything close > to that, because GTK doesn't let us. >=20 > > Calling exit is perfectly acceptable: the display connection is > > severed, and that can happen for multiple reasons, including the display > > server going away > > There's no "the display server is still running, but it closed > > the > > socket" mechanism for the toolkit to use >=20 > So why not use exit, which lets the atexit handlers run? I don't know, can someone ask? I feel like these people act like douches w= hen=20 some random person asks. > > The socket got closed > > The toolkit terminates > > Thaodan: It could happen because the client made an invalid > > request=E2=80=94 Wayland mandates that the display server closes the co= nnection > > in that case Or the display server decided to kill the client > > because it was unresponsive > > Why should the toolkit/lib call exit isn't there any better > > mechanism to doing such a thing in glib or gtk for that matter? > > It would be better to not need any hacks to prevent gtk from > > killing apps. > > Thaodan: There is no such mechanism > > ebassi: OK so what's the idea behind using _exit as a mechani= sm, > > doesn't that break any other app that has state so safe too? like for > > example an office application that wants to safe it's data before going > > down. I already told you > > If the display connection is closed by the server, then there's > > no > > safe way to store the data >=20 > Store the data that is in Emacs core?? How did these people learn to > write software? I guess they did but learned that they are always right when there's an iss= ue?=20 Idk.