GNU bug report logs - #53778
29.0.50; Can't start Emacs because of RenderBadPicture X protocol error

Previous Next

Full log

Message #14 received at 53778 <at> debbugs.gnu.org (full text, mbox):

From: Mauro Aranda <maurooaranda <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 53778 <at> debbugs.gnu.org
Subject: Re: bug#53778: 29.0.50; Can't start Emacs because of RenderBadPicture
 X protocol error
Date: Fri, 4 Feb 2022 12:14:54 -0300

[Message part 1 (text/plain, inline)]

El vie, 4 feb 2022 a las 11:52, Eli Zaretskii (<eliz <at> gnu.org>) escribió:
>> From: Mauro Aranda <maurooaranda <at> 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.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.