From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Vladimir Nikishkin Newsgroups: gmane.emacs.bugs Subject: bug#39081: 26.3; Emacs hangs if external SCIM input method is killed Date: Wed, 15 Jan 2020 00:24:49 +0800 Message-ID: References: <87lfqey1xj.fsf@delllaptop.lockywolf.net> <83blra8lnb.fsf@gnu.org> <83wo9y71gt.fsf@gnu.org> <83h8107lwa.fsf@gnu.org> <83eew2592b.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000d150c2059c1c0862" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="256962"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 39081@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jan 14 17:26:15 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1irP1C-0014Mz-TL for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 14 Jan 2020 17:26:15 +0100 Original-Received: from localhost ([::1]:43088 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1irP1B-0000l7-Nn for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 14 Jan 2020 11:26:13 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57468) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1irP10-0000kl-Uc for bug-gnu-emacs@gnu.org; Tue, 14 Jan 2020 11:26:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1irP0z-0001n3-Qh for bug-gnu-emacs@gnu.org; Tue, 14 Jan 2020 11:26:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55722) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1irP0z-0001mv-Nw for bug-gnu-emacs@gnu.org; Tue, 14 Jan 2020 11:26:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1irP0z-00061j-Kx for bug-gnu-emacs@gnu.org; Tue, 14 Jan 2020 11:26:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Vladimir Nikishkin Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 14 Jan 2020 16:26:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 39081 X-GNU-PR-Package: emacs Original-Received: via spool by 39081-submit@debbugs.gnu.org id=B39081.157901911223096 (code B ref 39081); Tue, 14 Jan 2020 16:26:01 +0000 Original-Received: (at 39081) by debbugs.gnu.org; 14 Jan 2020 16:25:12 +0000 Original-Received: from localhost ([127.0.0.1]:33462 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1irP0C-00060S-4Y for submit@debbugs.gnu.org; Tue, 14 Jan 2020 11:25:12 -0500 Original-Received: from mail-ed1-f44.google.com ([209.85.208.44]:36769) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1irP0A-000605-8G for 39081@debbugs.gnu.org; Tue, 14 Jan 2020 11:25:10 -0500 Original-Received: by mail-ed1-f44.google.com with SMTP id j17so12438334edp.3 for <39081@debbugs.gnu.org>; Tue, 14 Jan 2020 08:25:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uI1psvlh7HytghVHpkSwoGRDr+jCFGtZjTsFJ7jnvp4=; b=syjJdJT/wVd32aV7ix5iDi+LmPb7vEZHw4nOr3Q/5trJMGu08X7JYi+Fi28ycP376i en6HYMgB5eYYqrDltmndZ2rZYzNcjZvIERzEokgwxA2o6reOTbwlRVPuNoJ9iB+vPvYf QRDOfWvOkG5BicbO800irOOkHHOo2PqAhNH4xnbukurJpaAcKowHeQJbSeAK2hNYuNuq MWb3nN2IFtsYm2rU3fLivH+QGjK+KeX//oEaCB3GTYQjtryz2PzD+wbTmCLKDHJd4DGu QaB88jLrQDS/RhW/Ch0jYe9QGBnPnZppx5DX5cs2WCeU9Qs8dbGo4m5ZC9TuE/fvPr9I G6bQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uI1psvlh7HytghVHpkSwoGRDr+jCFGtZjTsFJ7jnvp4=; b=MNfDSdZhAUC+D6xA/F1mM+XMz10h/Lh8A0h7JIacOHRnUcDt94dttQJKR/8oNPTIpF 0I8fhLlzDzpOBf+M5XKzszp8o5NjUGC1Z/xlXQuKUU3LihJ4Nj7i4z58JPxm9uLuRp2V MIX2Zlydps3xsZYDQXqSE2l3uG+D03OUsipJWuRVPZ0myOcrICO3EO+d+GZZQNZNCdE/ tv4ZyOQvDEkxwKXsFv/2X3neA1N+4T1rx5c+AGxdfi666+cnJLKJxZK0T6bmCrUQvU8f ZMaylaAra5k8Gt1rUWnae8X9gLSJMEsWliXwzoAXF5aRdjVco/22BCE/KTaOFS9xBzHz Ku8A== X-Gm-Message-State: APjAAAX8Wr8CY/cD1jfE/VoF4ps85Tt5qp+0KaWr6/BqyR1wA4VcxFiF gW6ZIkYbQVkaQ7mEI+HJUxPniMOIIGtKhs3Oupc= X-Google-Smtp-Source: APXvYqykNLCS99WC5X1VvYDkKg5U553VsR2+ETBRXfoX4gLC9yvATUQZTmibgWUKToJ1n6niCVmMdFXIZ707843tE/Y= X-Received: by 2002:aa7:d982:: with SMTP id u2mr24469483eds.238.1579019104504; Tue, 14 Jan 2020 08:25:04 -0800 (PST) In-Reply-To: <83eew2592b.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 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.org gmane.emacs.bugs:174576 Archived-At: --000000000000d150c2059c1c0862 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Does Emacs have any deliberate support for SCIM. (Why should it?) Almost every other application simply ignores the crash. If input is requested again, SCIM daemon seems to get started on demand. Eli Zaretskii =E6=96=BC 2020=E5=B9=B41=E6=9C=8814=E6=97=A5 = =E9=80=B1=E4=BA=8C 23:52 =E5=AF=AB=E9=81=93=EF=BC=9A > > From: Vladimir Nikishkin > > Date: Tue, 14 Jan 2020 11:54:15 +0800 > > Cc: 39081@debbugs.gnu.org > > > > This is the "crashed" trace. Note the GTK message in between. > > Thanks. This seems to be an X error. > > And now I'm actually asking myself how reasonable is it to expect > Emacs to continue working when its IM service crashes. Why is this a > use case we should support? does it happen a lot in practice. > > (I admit I know very little about the architecture of SCIM support in > Emacs, in terms of what OS services we use to communicate with it, and > thus I cannot reason about the difficulty in surviving SCIM crashes. > Does someone know?) > --000000000000d150c2059c1c0862 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Does Emacs have any deliberate support for SCIM. (Why sho= uld it?)

Almost every other ap= plication simply ignores the crash. If input is requested again, SCIM daemo= n seems to get started on demand.

Eli Zaretskii <eliz@gnu.org> =E6=96=BC 2020=E5=B9=B41=E6=9C=8814=E6= =97=A5 =E9=80=B1=E4=BA=8C 23:52 =E5=AF=AB=E9=81=93=EF=BC=9A
> From: Vladimir Nikishkin <lockywolf@gmail= .com>
> Date: Tue, 14 Jan 2020 11:54:15 +0800
> Cc: 39081@debbugs.gnu.org
>
> This is the "crashed" trace. Note the GTK message in between= .

Thanks.=C2=A0 This seems to be an X error.

And now I'm actually asking myself how reasonable is it to expect
Emacs to continue working when its IM service crashes.=C2=A0 Why is this a<= br> use case we should support? does it happen a lot in practice.

(I admit I know very little about the architecture of SCIM support in
Emacs, in terms of what OS services we use to communicate with it, and
thus I cannot reason about the difficulty in surviving SCIM crashes.
Does someone know?)
--000000000000d150c2059c1c0862--