all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Alan Third <alan@idiocy.org>
Cc: Stefan Husmann <stefan-husmann@t-online.de>,
	34051@debbugs.gnu.org, 34095-done@debbugs.gnu.org
Subject: bug#34051: 27.0.50; Emacs 27 from master segfaults
Date: Thu, 17 Jan 2019 09:18:02 +0900	[thread overview]
Message-ID: <b4m4la8f879.fsf@jpl.org> (raw)
In-Reply-To: <87r2dhyj2q.fsf@frege.i-did-not-set--mail-host-address--so-tickle-me>

On Tue, 15 Jan 2019 16:52:32 +0000, Alan Third wrote:
> These X server errors are asynchronous and not very helpful. The most
> likely culprit is x_create_x_image_and_pixmap.

> Stefan, please try the attached patch.

Great!  This seems to do the trick also to bug#34095.  Thanks.
(I'm colosing bug#34095 that's probably a duplicate.)





  parent reply	other threads:[~2019-01-17  0:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14 15:08 "X protocol error: BadMatch" on current master Yuri D'Elia
2019-01-14 16:12 ` Eli Zaretskii
2019-01-12 15:46   ` bug#34051: 27.0.50; Emacs 27 from master segfaults stefan-husmann
2019-01-12 16:15     ` Eli Zaretskii
     [not found]       ` <87sgxxwtbs.fsf@frege.i-did-not-set--mail-host-address--so-tickle-me>
2019-01-12 20:22         ` Eli Zaretskii
2019-01-13 11:20           ` Stefan Husmann
2019-01-13 15:24             ` Eli Zaretskii
2019-01-15 16:52               ` Alan Third
2019-01-16 21:22     ` bug#34051: "X protocol error: BadMatch" on current master Yuri D'Elia
2019-01-16 21:28       ` Yuri D'Elia
2019-01-17 13:36       ` Eli Zaretskii
2019-01-17 17:39         ` Alan Third
2019-01-17 17:44           ` Yuri D'Elia
2019-01-17 17:50             ` Alan Third
2019-01-17  0:18     ` Katsumi Yamaoka [this message]
2019-01-17 17:42       ` bug#34051: 27.0.50; Emacs 27 from master segfaults Alan Third

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=b4m4la8f879.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=34051@debbugs.gnu.org \
    --cc=34095-done@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=stefan-husmann@t-online.de \
    /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.