From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Jonathan Doull <jonathan@hotlink.technology>
Cc: 21796@debbugs.gnu.org
Subject: bug#21796:
Date: Fri, 23 Jun 2017 11:55:27 -0400 [thread overview]
Message-ID: <CAM-tV-9Bw=2rzJ0xRZDO1bPyG1h+MW4eynb_w26526zZxHaGUg@mail.gmail.com> (raw)
In-Reply-To: <CANrRQd8AVrvuz_EAGsK3=v3B4g6C7e=2Br7yPht2WkHHtPf-fA@mail.gmail.com>
On Fri, Jun 23, 2017 at 11:47 AM, Jonathan Doull
<jonathan@hotlink.technology> wrote:
> This bug causes me to restart Emacs a few times every hour during heavy
> usage, which is very disruptive, and has stopped Emacs being fun.
>
> The bug is tagged with "moreinfo", however I'm uncertain how to improve on
> the quality of reporting that precedes me. I'm happy to assist with
> diagnosis if instructed.
>
> In the meantime do any fellow sufferers know a workaround (apart from
> dropping ediff)?
>
It looks like all reporters were using GTK, does the problem go away
if you ./configure --with-x-toolkit=lucid?
next prev parent reply other threads:[~2017-06-23 15:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 0:02 bug#21796: 25.0.50; exiting ediff can leave Emacs unresponsive to keyboard input Sean McAfee
2015-10-31 7:34 ` Eli Zaretskii
[not found] ` <86twolu3xg.fsf@sungevity.com>
2015-11-16 20:42 ` Eli Zaretskii
2015-11-16 21:48 ` Sean McAfee
2015-11-28 8:02 ` bug#21796: emacs not responding to keyboard events Mohammad Toossi
2016-03-16 14:54 ` bug#21796: 24.5; exiting ediff can leave Emacs unresponsive to keyboard input johannes.muelmenstaedt
2016-07-11 17:57 ` bug#21796: Mark Grosen
2017-06-23 15:47 ` bug#21796: Jonathan Doull
2017-06-23 15:55 ` Noam Postavsky [this message]
2017-06-23 16:13 ` bug#21796: Jonathan Doull
2017-06-23 17:23 ` bug#21796: martin rudalics
2017-06-23 17:54 ` bug#21796: Jonathan Doull
2017-06-24 8:39 ` bug#21796: martin rudalics
2017-06-23 19:03 ` bug#21796: exiting ediff can leave Emacs unresponsive to keyboard input Noam Postavsky
2017-06-24 8:39 ` martin rudalics
2017-06-28 18:37 ` Jonathan Doull
2017-06-29 7:17 ` martin rudalics
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='CAM-tV-9Bw=2rzJ0xRZDO1bPyG1h+MW4eynb_w26526zZxHaGUg@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=21796@debbugs.gnu.org \
--cc=jonathan@hotlink.technology \
/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).