unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Daniel Colascione <dancol@dancol.org>
Cc: "Peter Münster" <pmlists@free.fr>, emacs-devel@gnu.org
Subject: Re: trunk r116499: Improve dbus error handling; detect bus failure
Date: Mon, 24 Feb 2014 15:25:29 +0100	[thread overview]
Message-ID: <87r46segfa.fsf@gmx.de> (raw)
In-Reply-To: <530B4DBD.1090901@dancol.org> (Daniel Colascione's message of "Mon, 24 Feb 2014 05:48:45 -0800")

Daniel Colascione <dancol@dancol.org> writes:

> Thanks for coming up with that. I can only repro this problem with 
> dbus-debug turned on, but I think this issue is what Peter's been 
> hitting too. It's actually a core Emacs event loop bug that we never 
> noticed before due to checking read-event's return value and breaking 
> the loop early if it ever returns a dbus event.

Well, your shortened timeout in the loop has provoked this error at
least. That's worth the trouble :-)

> Can you try this patch?

Works for me. On one of my slower machines, I've run "emacs -Q" at least
10 times; the error didn't happen again.

So please install the patch.

Best regards, Michael.



  reply	other threads:[~2014-02-24 14:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1WGhnF-0006bq-Ma@vcs.savannah.gnu.org>
2014-02-24  8:18 ` trunk r116499: Improve dbus error handling; detect bus failure Michael Albinus
2014-02-24  8:24   ` Daniel Colascione
2014-02-24  8:54     ` Michael Albinus
2014-02-24 11:45       ` Peter Münster
2014-02-24 12:50         ` Daniel Colascione
2014-02-24 12:59           ` Daniel Colascione
2014-02-24 13:09           ` Michael Albinus
2014-02-24 13:14             ` Michael Albinus
2014-02-24 13:48               ` Daniel Colascione
2014-02-24 14:25                 ` Michael Albinus [this message]
2014-02-24 18:52                   ` Peter Münster

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=87r46segfa.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=dancol@dancol.org \
    --cc=emacs-devel@gnu.org \
    --cc=pmlists@free.fr \
    /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).