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: Sun, 07 Aug 2022 18:14:50 +0300 Message-ID: <3629604.AQ1hHsVFQY@odin> References: <1932596.zmb9SnqgO4@odin> <20004002.VVDfsmh7uS@odin> <83zgggw0r2.fsf@gnu.org> 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="7971"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, 56967@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Aug 07 17:15:15 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 1oKhzn-0001x1-5x for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 07 Aug 2022 17:15:15 +0200 Original-Received: from localhost ([::1]:45186 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oKhzm-0008Ts-0W for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 07 Aug 2022 11:15:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39652) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oKhza-0008QN-B1 for bug-gnu-emacs@gnu.org; Sun, 07 Aug 2022 11:15:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:48415) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oKhza-0007l4-06 for bug-gnu-emacs@gnu.org; Sun, 07 Aug 2022 11:15:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oKhzZ-00079n-R5 for bug-gnu-emacs@gnu.org; Sun, 07 Aug 2022 11:15:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Bjoern Bidar Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 07 Aug 2022 15:15:01 +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.165988529827483 (code B ref 56967); Sun, 07 Aug 2022 15:15:01 +0000 Original-Received: (at 56967) by debbugs.gnu.org; 7 Aug 2022 15:14:58 +0000 Original-Received: from localhost ([127.0.0.1]:38164 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oKhzW-00079D-Ah for submit@debbugs.gnu.org; Sun, 07 Aug 2022 11:14:58 -0400 Original-Received: from thaodan.de ([185.216.177.71]:58400) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oKhzV-000790-3m for 56967@debbugs.gnu.org; Sun, 07 Aug 2022 11:14:57 -0400 Original-Received: from odin.localnet (dsl-trebng12-b04885-76.dhcp.inet.fi [176.72.133.76]) by thaodan.de (Postfix) with ESMTPSA id EFCA4D07416; Sun, 7 Aug 2022 18:14:50 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=thaodan.de; s=mail; t=1659885291; bh=AcicHs/dEivM0+yGiPkvXNkuGibtOEbj8GCMDZLFzqo=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=skadsrAqw4ZQ7a24CzBuMYz3X8o0Of/d0sEchVb5+yP4rFdhnmJQiDW/6cnF8w90a 6i01JizrUEOCbdJsidqqrYlTVFw3SgXTZHzm93uCK8QsTR0kP2orxRhZz8uctQZosG ++pgIHKE5CH4x831Qh4dZNweeyniddDwo8ZDF7aKPtoXXpMUHZ15IgzWm/DamRvybX Lb5+XTV97c8V4KgISPpXQgBVSsnArnWm9sR+4VdeLdBeH8fQwvmDU92YqdhNcsssEO 6BEYjThZoMIiExa1RuxmOe75G+/kagP5Q1+cXa+OVp7u1akF/U8BVHJWHTRotL4E+n bLZtoLQBK/8R3Ww4FxPTADNOKmVGECpA0wzsHCmeDfweAybahokZ0FBQlrqAL01AL5 GQXu2XIpqoOcs+gdZ9Xvmp7KwRkKBHU7zUfBTBiINZ6ontxfPw4X/jccLCMpVZSien fPw+x1p0HjdLEikTGdt15lhJDJp5RAIKMLPyz4wV9UM88ZoiLdu2d89MIp03kunLq/ px6l6ZQyo+zS8a9yJZgEMaw5WqUlaKlM0jfPZG5tV8eQCvk+2jWz0cN7n7ZIotD+zU dgmRVsGrRyyF6Te8sMPa3tN3TuOnv/Q1dR2bL/vx9SzlFFFLVfthwdpgdZNhfumoM2 jw0xhB/BMugygaOh8EAsax4A= In-Reply-To: <83zgggw0r2.fsf@gnu.org> 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:239075 Archived-At: Am Sonntag, 7. August 2022, 18:07:29 EEST schrieb Eli Zaretskii: > > Cc: 56967@debbugs.gnu.org > > Date: Sun, 07 Aug 2022 17:51:25 +0300 > > From: Bjoern Bidar via "Bug reports for GNU Emacs, > >=20 > > the Swiss army knife of text editors" > >=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 > >=20 > > I don't really understand why calling _exit is an acceptable solution > > anyone that has to safe some state to the disk is lost. >=20 > > I attach the whole conversation to not take anything out of context her= e: > Those guys evidently think that an application without display cannot > do anything. They forget that even if display connection is lost, and > even if this is due to some fault of the application, that application > could still shut down gracefully instead of losing all of the user's > work, if only GTK wouldn't call _exit "because it's acceptable", or > "because emacs is a 1980s teletype app", or because whatever other > ridiculous justifications these guys come up for such misconduct. I don't know what to say, I'm befuddled too. The audacity to act such a way as a library. > > I already told you > > If the display connection is closed by the server, then there's > > no > > safe way to store the data >=20 > Really? Since when does saving data to disk require a display > connection?? I don't know either, this is what came after: Because the toolkit has no idea what's left of the system's integr= ity how could it start before the compositor? the display connection lost doesn't mean the whole system is brok= en=20 but just the compositor. But I assume that the toolkit takes precedence ove= r=20 the app it self. Thaodan: You literally **cannot** know that two[m]: background services such as systemd --user services wouldn't it fail because no $WAYLAND_DISPLAY? *** First activity: MichaelNazzarenoTrimarchi[m] joined 53 minutes 11 secon= ds=20 ago. Well the app can really do anything before=20 starting the graphic subsystem. It can even wait that Wayland service is=20 started before do any specific toolkit initialization=20 MichaelNazzarenoTrimarchi[m]: Exactly, apps such as editors might= =20 reload their last session which can take quite some time=20 There it makes sense to start as early as possible. How can I find out if GTK did an invalid request to the composito= r? That is simple=20 You can activate Wayland tracing of message You can see then message sent to compositor It's rather difficult that is an application= =20 bug but could be a client side Wayland part bug