From: Mauro Aranda <maurooaranda@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 53778@debbugs.gnu.org
Subject: bug#53778: 29.0.50; Can't start Emacs because of RenderBadPicture X protocol error
Date: Fri, 4 Feb 2022 12:14:54 -0300 [thread overview]
Message-ID: <CABczVwdWe6Mj4vK6wvN2voR_iv==iY3Y=LKmExuO0oH763JXDA@mail.gmail.com> (raw)
In-Reply-To: <83ee4i3cr6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
El vie, 4 feb 2022 a las 11:52, Eli Zaretskii (<eliz@gnu.org>) escribió:
>> From: Mauro Aranda <maurooaranda@gmail.com>
>> Date: Fri, 4 Feb 2022 11:38:46 -0300
>>
>> After commit b944841173... I can't start GUI Emacs.
>>
>> I did:
>> ./configure && make
>>
>> And when I start Emacs with "emacs -Q" I get:
>> X protocol error: RenderBadPicture (invalid Picture parameter) on
protocol request 138
>> When compiled with GTK, Emacs cannot recover from X disconnects.
>> This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221
>> For details, see etc/PROBLEMS.
>> Backtrace:
>> ./src/emacs(emacs_backtrace+0x41)[0x81bc731]
>> ./src/emacs(terminate_due_to_signal+0x7f)[0x809958c]
>> ./src/emacs[0x8099abd]
>> ./src/emacs[0x8098b20]
> We need you to start Emacs under GDB, passing Emacs the command-line
> option '-xrm "emacs.synchronous: true"', and then show the backtrace
> inside GDB. That should produce a much more useful backtrace than the
> one you posted.
I know, but...
> Why are you unable to run GDB?
With GDB 10.1, I get:
../../gdb/utils.c:671: internal-error: virtual memory exhausted: can't
allocate 4064 bytes.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
I have never run into this problem before.
[-- Attachment #2: Type: text/html, Size: 1711 bytes --]
next prev parent reply other threads:[~2022-02-04 15:14 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABczVwdWe6Mj4vK6wvN2voR_iv==iY3Y=LKmExuO0oH763JXDA@mail.gmail.com' \
--to=maurooaranda@gmail.com \
--cc=53778@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.