From: Alan Coopersmith <alan.coopersmith@oracle.com>
To: Po Lu <luangruo@yahoo.com>, ali_gnu2@emvision.com
Cc: 69762@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#69762: X11 versions of Emacs 29 on sparc fail at startup
Date: Sat, 23 Mar 2024 10:00:42 -0700 [thread overview]
Message-ID: <22c91ff9-05e3-4c22-8b7e-34d07dbe30d9@oracle.com> (raw)
In-Reply-To: <87wmq1qdip.fsf@yahoo.com>
Ali asked me to look into this bug as one of the X11 maintainers for
Solaris, but I also am one of the upstream maintainers for X.Org.
On 3/17/24 04:54, Po Lu wrote:
> Whatever the conditions for the X server crash, please report it (or ask
> Rainier to do so) to the X.Org developers. Between the recent deletion
> of support for byte-swapping and its developers transition to only
> assembling Xwayland releases, there is very little love remaining in
> that organization for the rank-and-file of X users, and every reminder
> of our existence counts towards restoring some of that lost dedication.
There's still some of us working to maintain X11 for X11 users (mostly
because Wayland isn't an option for our kernel). Also note that byte
swapping was *not* deleted, just disabled by default and can be easily
re-enabled. Which is important here, because the bugs Ali & Rainer
found are not SPARC-specific, but caused by them running emacs on a
SPARC and displaying it onto an x86 desktop, thus invoking the byte
swapping code where both the Xsync & Xinput2 bugs lie.
I've merged a fix upstream for the Xsync bug already, as it was quite
simple: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1437/
The Xinput2 one is a little more involved and I'm working on getting it
fixed upstream now.
--
-Alan Coopersmith- alan.coopersmith@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/solaris
next prev parent reply other threads:[~2024-03-23 17:00 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22c91ff9-05e3-4c22-8b7e-34d07dbe30d9@oracle.com \
--to=alan.coopersmith@oracle.com \
--cc=69762@debbugs.gnu.org \
--cc=ali_gnu2@emvision.com \
--cc=eliz@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).