unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Matt Armstrong <matt@rfc20.org>
Cc: drsl@drshapeless.com, Robert Pluim <rpluim@gmail.com>,
	58584@debbugs.gnu.org
Subject: bug#58584: 29.0.50; M-w crashes Emacs
Date: Tue, 18 Oct 2022 08:36:27 +0800	[thread overview]
Message-ID: <87wn8yc6ic.fsf@yahoo.com> (raw)
In-Reply-To: <87lepe75g3.fsf@rfc20.org> (Matt Armstrong's message of "Mon, 17 Oct 2022 09:58:20 -0700")

Matt Armstrong <matt@rfc20.org> writes:

> X-Debbugs-CC: Po Lu <luangruo@yahoo.com>
>
> ^^^ to get Po's attention.
>
>
> Robert Pluim <rpluim@gmail.com> writes:
>
>>>>>>> On Mon, 17 Oct 2022 23:15:01 +0800, Jacky Li via "Bug reports for GNU
>> Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> said:
>>
>>     Bug> I was at eff4a4f49a. In EXWM, using M-w will crash Emacs. The x server
>>     Bug> gave an error of not finding the libinput module. I then switched to
>>     Bug> dwm, Emacs still crashed after M-w.
>>
>>     Bug> I am currently at b9aff5fdb8, everything is fine. I strongly suspect the
>>     Bug> bug was introduced in abf683bb03. It should be something related to
>>     Bug> putting things into kill buffer related to X. An extra information is
>>     Bug> that my Emacs is built with libinput2 support.
>>
>> Reverting abf683bb03 makes that crash go away for me.
>>
>> I guess Po Lu will look at it.

I tested that change under the no toolkit build and it worked there, so
it's probably specific to GTK 3.  Thanks, I will look into this.





  reply	other threads:[~2022-10-18  0:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 15:15 bug#58584: 29.0.50; M-w crashes Emacs Jacky Li via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-17 15:34 ` Robert Pluim
2022-10-17 16:58   ` Matt Armstrong
2022-10-18  0:36     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-17 16:49 ` Matt Armstrong
2022-10-18  0:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18  8:24   ` Robert Pluim
2022-10-18 10:08     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 10:27       ` Robert Pluim
2022-10-18 10:45         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 12:42           ` Robert Pluim

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=87wn8yc6ic.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=58584@debbugs.gnu.org \
    --cc=drsl@drshapeless.com \
    --cc=luangruo@yahoo.com \
    --cc=matt@rfc20.org \
    --cc=rpluim@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).