unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Steve Newcomb <srn@coolheads.com>
To: 13486@debbugs.gnu.org
Subject: bug#13486: 24.2.92: large X-selections: timed out waiting for property notify event
Date: Wed, 8 Oct 2014 12:50:44 -0700 (PDT)	[thread overview]
Message-ID: <1412797844730-333732.post@n5.nabble.com> (raw)
In-Reply-To: <861ttftngo.fsf@yandex.ru>

In my experience, this bug does not require a large X selection to be
revealed.

Like Dmitry, I am running Ubuntu 14.04 stock emacs 24, (GNU Emacs 24.3.1
(x86_64-pc-linux-gnu, GTK+ Version 3.10.7) of 2014-03-07 on lamiak, modified
by Debian) but now I've had to abandon it in favor of emacs 23.  The
timed-out-waiting-for-property-notify-event thing has stopped me dead,
dozens of times, requiring me to kill the emacs process and restart the
whole session.  No amount of control-G keypresses can restore it to
responsiveness.  I have not been doing large cut-and-paste operations
(which, yes, also have the similar effect reported above).  I've been
running pdb (python debugger) sessions in shell buffers.  That alone will
put emacs 24 into the unresponsive state described above.  It doesn't seem
to matter whether I'm running locally under X11, or on a remote machine via
an X11 tunnel, or via an x11vnc session.

I rather like everything about Emacs 24, except for the one unfortunate fact
that it simply doesn't work in my pdb sessions in shell buffers.  Emacs 23
still works, though, and that's a great mercy.





--
View this message in context: http://emacs.1067599.n5.nabble.com/bug-13486-24-2-92-large-X-selections-timed-out-waiting-for-property-notify-event-tp275798p333732.html
Sent from the Emacs - Bugs mailing list archive at Nabble.com.





  reply	other threads:[~2014-10-08 19:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 14:22 bug#13486: 24.2.92: large X-selections: timed out waiting for property notify event Charles Rendleman
2013-01-18 20:29 ` Glenn Morris
     [not found]   ` <CALiJhZ4HoOgSxq3z_08iwiq7BR0+rT0RN8tybGO-+MG7ryTXWA@mail.gmail.com>
2013-01-19  1:46     ` Glenn Morris
2013-01-19  5:44       ` Chong Yidong
     [not found]         ` <CALiJhZ5BdYmGk-hBM1kwOFgT-guw_PZwHcLOtuj0TMhU0Xv1Dw@mail.gmail.com>
2013-01-19 15:41           ` Chong Yidong
2013-01-19 17:19             ` Stefan Monnier
2013-01-19 21:55               ` Charles Rendleman
2013-05-15 21:28             ` unfrostedpoptart
2014-07-21  3:11               ` Dmitry Gutov
2014-10-08 19:50                 ` Steve Newcomb [this message]
2014-10-08 21:34                   ` Stefan Monnier
2015-06-23 23:44 ` bug#13486: 25.0.50; struct selection_input_event data might be corrupted by assignments as another structure type Paul Eggert
2015-06-24  0:56   ` YAMAMOTO Mitsuharu
2015-06-24  1:05     ` bug#17026: " Paul Eggert
2015-06-24  1:20       ` bug#13486: " YAMAMOTO Mitsuharu
2020-09-13 15:53   ` Lars Ingebrigtsen

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=1412797844730-333732.post@n5.nabble.com \
    --to=srn@coolheads.com \
    --cc=13486@debbugs.gnu.org \
    /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).