From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: 53778@debbugs.gnu.org
Subject: bug#53778: 29.0.50; Can't start Emacs because of RenderBadPicture X protocol error
Date: Sat, 05 Feb 2022 20:56:21 +0800 [thread overview]
Message-ID: <87y22p1ngq.fsf@yahoo.com> (raw)
In-Reply-To: <CABczVwd-AK+GJQzHBsH=3RSbJQU6Y2WZtw=AD3huscE+MdcbKQ@mail.gmail.com> (Mauro Aranda's message of "Sat, 5 Feb 2022 12:38:18 -0300")
Mauro Aranda <maurooaranda@gmail.com> writes:
> Haven't made any progress with GDB so far, sorry.
I hope you get it working soon.
If you run Emacs with synchronization on outside gdb, wait for it to
crash, and run `coredumpctl debug', what happens? A backtrace from such
a core dump would work as well.
> xdpyinfo output attached.
Thanks, unfortunately I see nothing out of the ordinary here.
next prev parent reply other threads:[~2022-02-05 12:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 14:07 bug#53778: 29.0.50; Can't start Emacs because of RenderBadPicture X protocol error Mauro Aranda
2022-02-04 14:38 ` Mauro Aranda
2022-02-04 14:52 ` Eli Zaretskii
2022-02-04 15:14 ` Mauro Aranda
2022-02-04 15:16 ` Eli Zaretskii
2022-02-04 15:45 ` Mauro Aranda
2022-02-04 16:42 ` Eli Zaretskii
2022-02-04 15:34 ` Stephen Berman
2022-02-04 15:49 ` Mauro Aranda
2022-02-04 15:49 ` Stephen Berman
2022-02-05 1:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-05 1:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-05 1:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-05 15:33 ` Mauro Aranda
2022-02-05 15:38 ` Mauro Aranda
2022-02-05 12:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-10 13:45 ` Mauro Aranda
2022-02-11 1:07 ` 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=87y22p1ngq.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=53778@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=maurooaranda@gmail.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).