From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ali Bahrami <ali_gnu2@emvision.com>
Cc: 69762@debbugs.gnu.org
Subject: bug#69762: X11 versions of Emacs 29 on sparc fail at startup
Date: Sat, 16 Mar 2024 14:32:07 +0800 [thread overview]
Message-ID: <87il1msn4o.fsf@yahoo.com> (raw)
In-Reply-To: <87plvusnbc.fsf@yahoo.com> (Po Lu's message of "Sat, 16 Mar 2024 14:28:07 +0800")
Po Lu <luangruo@yahoo.com> writes:
> I don't think such a drastic measure is necessary under the
> circumstances. We should (please test) put this down as a bug in the
> X.Org server and install an error trap around SyncCreateFence requests,
> thus:
>
> diff --git a/src/xterm.c b/src/xterm.c
> index c8a43785564..26926bc4faa 100644
> --- a/src/xterm.c
> +++ b/src/xterm.c
> @@ -7292,6 +7292,7 @@ x_sync_init_fences (struct frame *f)
> && dpyinfo->xsync_minor < 1))
> return;
>
> + x_ignore_errors_for_next_request (dpyinfo, 0);
> output->sync_fences[0]
> = XSyncCreateFence (FRAME_X_DISPLAY (f),
> /* The drawable given below is only used to
> @@ -7303,6 +7304,7 @@ x_sync_init_fences (struct frame *f)
> = XSyncCreateFence (FRAME_X_DISPLAY (f),
> FRAME_X_WINDOW (f),
> False);
> + x_stop_ignoring_errors (dpyinfo, 0);
>
> XChangeProperty (FRAME_X_DISPLAY (f), FRAME_OUTER_WINDOW (f),
> dpyinfo->Xatom_net_wm_sync_fences, XA_CARDINAL,
Scratch that,
diff --git a/src/xterm.c b/src/xterm.c
index c8a43785564..2358918ac5b 100644
--- a/src/xterm.c
+++ b/src/xterm.c
@@ -7292,6 +7292,7 @@ x_sync_init_fences (struct frame *f)
&& dpyinfo->xsync_minor < 1))
return;
+ x_ignore_errors_for_next_request (dpyinfo, 0);
output->sync_fences[0]
= XSyncCreateFence (FRAME_X_DISPLAY (f),
/* The drawable given below is only used to
@@ -7303,6 +7304,7 @@ x_sync_init_fences (struct frame *f)
= XSyncCreateFence (FRAME_X_DISPLAY (f),
FRAME_X_WINDOW (f),
False);
+ x_stop_ignoring_errors (dpyinfo);
XChangeProperty (FRAME_X_DISPLAY (f), FRAME_OUTER_WINDOW (f),
dpyinfo->Xatom_net_wm_sync_fences, XA_CARDINAL,
next prev parent reply other threads:[~2024-03-16 6:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 17:57 bug#69762: X11 versions of Emacs 29 on sparc fail at startup ali_gnu2
2024-03-13 0:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-13 17:02 ` ali_gnu2
2024-03-14 0:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-14 5:56 ` Ali Bahrami
2024-03-14 6:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 1:48 ` Ali Bahrami
2024-03-15 2:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 4:22 ` Ali Bahrami
2024-03-15 6:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 16:37 ` Ali Bahrami
2024-03-16 0:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-16 4:58 ` Ali Bahrami
2024-03-16 6:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-16 6:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-03-17 1:13 ` Ali Bahrami
2024-03-16 11:14 ` Eli Zaretskii
2024-03-16 12:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-17 1:38 ` ali_gnu2
2024-03-17 11:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-23 17:00 ` Alan Coopersmith
2024-04-03 17:48 ` Alan Coopersmith via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 10:34 ` Eli Zaretskii
2024-04-06 11:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 16:36 ` ali_gnu2
2024-04-07 0:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87il1msn4o.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=69762@debbugs.gnu.org \
--cc=ali_gnu2@emvision.com \
--cc=luangruo@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.