From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Alexander Prähauser" <alexander.praehauser@gmx.at>
Cc: 66281@debbugs.gnu.org
Subject: bug#66281: 30.0.50; Emacs won't start on X11 with 10 bit color depth
Date: Sun, 01 Oct 2023 18:59:37 +0800 [thread overview]
Message-ID: <87il7qliau.fsf@yahoo.com> (raw)
In-Reply-To: <87fs2ud14m.fsf@gmx.at> ("Alexander Prähauser"'s message of "Sun, 01 Oct 2023 13:37:06 +0200")
Alexander Prähauser <alexander.praehauser@gmx.at> writes:
> I put the output into the attached file.
Debugging symbols are absent from the copy of Emacs being run under gdb,
so this output is meaningless. Please build Emacs from source code and
debug that in its place.
next prev parent reply other threads:[~2023-10-01 10:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r0mf1rl2.fsf@gmx.at>
2023-10-01 1:03 ` bug#66281: 30.0.50; Emacs won't start on X11 with 10 bit color depth Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-01 11:37 ` Alexander Prähauser
2023-10-01 10:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-10-01 14:09 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-02 10:48 ` Alexander Prähauser
2023-10-02 10:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-02 17:10 ` Alexander Prähauser
2023-10-03 0:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-03 20:31 ` Alexander Prähauser
2023-10-03 23:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-05 21:51 ` Alexander Prähauser
2024-01-10 10:36 ` Stefan Kangas
2024-01-10 11:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-10 12:00 ` Stefan Kangas
2023-10-01 11:11 ` Stefan Kangas
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=87il7qliau.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=66281@debbugs.gnu.org \
--cc=alexander.praehauser@gmx.at \
--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).