From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Robert Pluim Newsgroups: gmane.emacs.bugs Subject: bug#63555: closed (Re: bug#63555: emacs 29 complains that it can't connect to the display) Date: Mon, 22 May 2023 13:28:09 +0200 Message-ID: <87sfbok3li.fsf@gmail.com> References: <83ednbrwfp.fsf@gnu.org> <87ttwbawse.fsf@vps.thesusis.net> <87a5xyrjce.fsf@vps.thesusis.net> <875y8klt89.fsf@gmail.com> <877ct0zph8.fsf@yahoo.com> <87wn10k7ew.fsf@gmail.com> <87ttw4y5ur.fsf@yahoo.com> 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="34428"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , Phillip Susi , 63555@debbugs.gnu.org To: Po Lu Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon May 22 13:29:23 2023 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 1q13j8-0008m9-QA for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 22 May 2023 13:29:22 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q13it-0007qq-9H; Mon, 22 May 2023 07:29:07 -0400 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 1q13io-0007pw-09 for bug-gnu-emacs@gnu.org; Mon, 22 May 2023 07:29:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1q13in-00037e-OM for bug-gnu-emacs@gnu.org; Mon, 22 May 2023 07:29:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1q13in-0002xg-K8 for bug-gnu-emacs@gnu.org; Mon, 22 May 2023 07:29:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Robert Pluim Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 22 May 2023 11:29:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63555 X-GNU-PR-Package: emacs Original-Received: via spool by 63555-submit@debbugs.gnu.org id=B63555.168475490111334 (code B ref 63555); Mon, 22 May 2023 11:29:01 +0000 Original-Received: (at 63555) by debbugs.gnu.org; 22 May 2023 11:28:21 +0000 Original-Received: from localhost ([127.0.0.1]:33709 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q13i9-0002wj-35 for submit@debbugs.gnu.org; Mon, 22 May 2023 07:28:21 -0400 Original-Received: from mail-wr1-f53.google.com ([209.85.221.53]:53502) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q13i4-0002wS-VC for 63555@debbugs.gnu.org; Mon, 22 May 2023 07:28:19 -0400 Original-Received: by mail-wr1-f53.google.com with SMTP id ffacd0b85a97d-309550263e0so3401303f8f.2 for <63555@debbugs.gnu.org>; Mon, 22 May 2023 04:28:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684754891; x=1687346891; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:from:to:cc:subject:date:message-id :reply-to; bh=Oyeu81gWUJ/3plgDtzhiTBiNGVHa+ZvgoxaJzglxXr0=; b=E/fbnOa1YQUIipi9+k378S0Yo0ZbRp6vLI1vh+CA9/RKrgCyqVBblNDzpXNx325SUr 09+wt2tYRaFzATXHa242YYxreVpeRLA1EeI7iI68uBP5PRQNe5VLc2my9FY+fqsOM5hG sdTRhjVm26ZYJ+6W9SZ4LsqloOaQPuGwBJTAeTuAklRR0bx0QV2U7gyE5tHmxoOzQLNm TtqF9hm8rtlYCvgjtOF8PhIIglZIeUyXD3LtFNTzoSp/0RiIsJVODpmUMV2IoidOOEoH rG8UsPlQ+LjqHzrCWfn6skvlhyGr7Dw8EJDsppU4H3ChLgi9jLbuF2zxLoR9nSV+7lVY vqvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684754891; x=1687346891; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Oyeu81gWUJ/3plgDtzhiTBiNGVHa+ZvgoxaJzglxXr0=; b=LChzP0qi3zB8j0cyyh/xQ42ggLQ0aEghE+bhaeQbdIO5C9zdVui9ypMhWoW5Ghq1Ii zDQcCgLrD/w/Np8HmgCazO2sh1Ts4I4pJ1xx82esQL/6t40AoqExMKYEhKzXgUdypLZa W7zbiYQ9H9bEyWeax4W/uiFYcj35Ja4jhA5Iw0dbPceK3Qf5/qXQE4FyS+yx4RVNEz/I CAONaGPIPW3QAllWLCPGrQ1jC9F2SLncujZvUoR3KXTAtIP94AnG7+FpqSiDJeGn3xnE hKaH9py7B5pqFL8AnOUiX9J9W6HVCyreIHNV2TuXmWb8zi2c4TBJKVwT6dg75vXzG54f ue4A== X-Gm-Message-State: AC+VfDzlQ5whrTy9jn6twidkY83Ic2atO0vSMkqXrXQqKynh22IIrUGn 8/jQMDXyh6BYI/tyecqo5lg= X-Google-Smtp-Source: ACHHUZ52YBjS7xXrY8Vt5c+YzSG1DLk2a/asEgg/y/tbQrN7XBsbQc4mJnbR+dhJ0PrZ3NaVxF9IkA== X-Received: by 2002:adf:ee05:0:b0:309:3c19:a127 with SMTP id y5-20020adfee05000000b003093c19a127mr7069333wrn.36.1684754890670; Mon, 22 May 2023 04:28:10 -0700 (PDT) Original-Received: from rltb ([82.66.8.55]) by smtp.gmail.com with ESMTPSA id o10-20020a056000010a00b002c70ce264bfsm7387735wrx.76.2023.05.22.04.28.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 22 May 2023 04:28:10 -0700 (PDT) In-Reply-To: <87ttw4y5ur.fsf@yahoo.com> (Po Lu's message of "Mon, 22 May 2023 19:15:40 +0800") 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:262145 Archived-At: >>>>> On Mon, 22 May 2023 19:15:40 +0800, Po Lu said: Po Lu> Robert Pluim writes: >>>>>>> On Mon, 22 May 2023 17:26:27 +0800, Po Lu = said: >>=20 Po> The problem with this approach is that gtk_init_check initializes t= he Po> window system upon success, so once pgtk_term_init is called in Po> pgtkterm.c, the window system is set up a second time, leaving two Po> display connections open... >>=20 >> Is there anything stopping us from removing that call to gtk_init? Po Lu> Yes, since the PGTK build is supposed to support multiple displa= ys. Ha! And has anyone actually tested that? :-) Po Lu> BTW, the other problem with calling `gtk_init_check' is that whe= n it Po Lu> returns FALSE, calling any other GTK function results in undefin= ed Po Lu> behavior. Thus, if `gtk_init_check' is used at startup, opening= a Po Lu> display later becomes unsafe, even if a display connection is th= en Po Lu> available. Do the gtk folks deliberately set out to make their users=CA=BC lives difficult, or is it accidental? Looks like Eli=CA=BCs NEWS entry is it, then. Robert --=20