From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Arsen =?utf-8?Q?Arsenovi=C4=87?= Newsgroups: gmane.emacs.devel Subject: Re: Qt can now survive Wayland compositor restarts Date: Sat, 11 Mar 2023 13:25:05 +0100 Message-ID: <86edpvzd09.fsf@aarsen.me> References: <87pm9g36vk.fsf@athena.silentflame.com> <1499bc96-cecf-3c79-59e9-0c1db6a45aca@yandex.ru> <86ilf82qh9.fsf@aarsen.me> <83o7ozydhk.fsf@gnu.org> <87a60jeo57.fsf@yahoo.com> <86bkkz364s.fsf@aarsen.me> <875yb7ee3p.fsf@yahoo.com> <86a60j1q55.fsf@aarsen.me> <871qlvecy5.fsf@yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28017"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , dgutov@yandex.ru, spwhitton@spwhitton.name, emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Mar 11 13:31:41 2023 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 1payNx-00072u-6b for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Mar 2023 13:31:41 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1payN5-0001K0-Rj; Sat, 11 Mar 2023 07:30:47 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1payMy-0001GN-G3 for emacs-devel@gnu.org; Sat, 11 Mar 2023 07:30:44 -0500 Original-Received: from mout-p-103.mailbox.org ([2001:67c:2050:0:465::103]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_CHACHA20_POLY1305:256) (Exim 4.90_1) (envelope-from ) id 1payMw-0003fS-KN; Sat, 11 Mar 2023 07:30:40 -0500 Original-Received: from smtp202.mailbox.org (smtp202.mailbox.org [10.196.197.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-103.mailbox.org (Postfix) with ESMTPS id 4PYj1h3nQdz9sXg; Sat, 11 Mar 2023 13:30:32 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aarsen.me; s=MBO0001; t=1678537832; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Buctv5giLLhmOn6o4vLucLukATbEbCJMp/nxzT701oA=; b=NykFH4F6NmkN131QISZ+0170dOYuYX7vpzY8Y+081/q27+hpBKiYvr3pimvu45R9kUNjpK iYMu9r8RnwtZ8Tv83eEPMuxwxh/ZXzFfwId04s/hmgs1JOuhHboC+CIj4AnR5CJJhNXnZv s5JU7g0TTJnZ7zl19OkoJuT110k7KGmC5kac9TZkUm2ogQofpQgC/pmn06n0Zr6O9vBNs6 DRMjKr9ehN3F5hMviVCD3dqvcHyw+qk0fKkxWde3V0XZmErfQHew+PGq7mxJC9JkStyX1n YAZzbCyJ9K0UTFZQLopx33AMQr42CarQAYuxzhw8YXhWNkn0ry4M1aSZCAhxDg== In-reply-to: <871qlvecy5.fsf@yahoo.com> Received-SPF: pass client-ip=2001:67c:2050:0:465::103; envelope-from=arsen@aarsen.me; helo=mout-p-103.mailbox.org X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:304293 Archived-At: --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Po Lu writes: > Arsen Arsenovi=C4=87 writes: > >> It would be indeed. >> >> The likelihood of crashes would be lowered if the display server event >> loop is not kept busy by the Elisp interpreter, though, which is why a >> separate thread would help (for instance, I suspect that the reason I >> see crashes when sending mail on occasion is because smtpmail blocks the >> main thread and a bunch of mouse events get queued up in the meanwhile, >> causing libwayland to give up). > > If the display server crashes, the connection is closed, and GDK gives > up when it calls `wl_display_flush' at some point and gets SIGPIPE. > It's not related to events being queued up or whatever. Yes, it's indeed not related in the display server crash case. That is not the case that concerns me in this instance, though. The display server keeps working just fine when I see GTK call _exit. You can simulate this by starting Emacs, suspending it, resizing the window a bunch and clicking around, and then unsuspending it: ~$ emacs ^Z [1]+ Stopped emacs << Some mouse/resize spam here for a few seconds >> ~ 148 $ fg emacs Gdk-Message: 13:26:40.087: Lost connection to Wayland compositor. ~ 1 $=20 >> In either case, the better fix would be teaching GTK not to do silly >> things on error conditions, and instead consult the user, but I'm not >> sure how doable that is. > > Very easy, as was proven when this feature actually worked as intended > sometime during the 2.14 series. It's just that the GTK developers need > their power fix and refuse to actually fix the problem, because ``only > Emacs needs this fixed.'' That's what I was fearing too ;). I know of at least one instance of this affecting GTK apps, so "only Emacs needs this" is false. Do you have a link to the bug handy? I'd like to read the history. =2D-=20 Arsen Arsenovi=C4=87 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iOYEARYKAI4WIQT+4rPRE/wAoxYtYGFSwpQwHqLEkwUCZAx0Zl8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0RkVF MkIzRDExM0ZDMDBBMzE2MkQ2MDYxNTJDMjk0MzAxRUEyQzQ5MxAcYXJzZW5AYWFy c2VuLm1lAAoJEFLClDAeosSTZLAA/jtEON9aZYh4KS2Qf5vimnP8F0Q+WBF0OeAz 468pNxfzAP99TffEs8Ux93J1WOFzboUwFJUmKTwiWd5+6vD65PjXDA== =E+8E -----END PGP SIGNATURE----- --=-=-=--