From: Robert Pluim <rpluim@gmail.com>
To: 58584@debbugs.gnu.org
Cc: drsl@drshapeless.com
Subject: bug#58584: 29.0.50; M-w crashes Emacs
Date: Mon, 17 Oct 2022 17:34:25 +0200 [thread overview]
Message-ID: <87tu42wjjy.fsf@gmail.com> (raw)
In-Reply-To: <871qr632iy.fsf@drshapeless.com> (Jacky Li via's message of "Mon, 17 Oct 2022 23:15:01 +0800")
>>>>> 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.
Robert
--
next prev parent reply other threads:[~2022-10-17 15:34 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tu42wjjy.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=58584@debbugs.gnu.org \
--cc=drsl@drshapeless.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 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.