GNU bug report logs - #21337
25.0.50; inotify error message

Previous Next

Package: emacs;

Reported by: Robert Pluim <rpluim <at> gmail.com>

Date: Mon, 24 Aug 2015 12:13:02 UTC

Severity: normal

Merged with 21361

Found in version 25.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Robert Pluim <rpluim <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 21337 <at> debbugs.gnu.org
Subject: bug#21337: 25.0.50; inotify error message
Date: Mon, 24 Aug 2015 18:22:16 +0200
Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Robert Pluim <rpluim <at> gmail.com>
>> Date: Mon, 24 Aug 2015 14:12:33 +0200
>> 
>> commit 200c2b10faf298bf65e8b6dbd0cb9ef00b2f95d6 made inotify be
>> preferred to gnotify.
>> 
>> That has shown that there's something amiss in our inotify
>> support: my emacs now spams me with
>> 
>> "Error while trying to read file system events"
>> 
>> whenever I run Gnus, making it unusable.
>
> Please provide more details.  Do you have global-auto-revert-mode
> enabled, per chance?

I do, but I've had that enabled for at least the last 6 months.  I
went away on vacation, re-pulled & re-built, and got the inotify
errors. Relevant .emacs:

 '(dired-auto-revert-buffer (quote dired-directory-changed-p))
 '(global-auto-revert-mode t)
 '(global-auto-revert-non-file-buffers t)

although disabling those 3 makes no difference to the behaviour.

I've double checked my emacs build was using gnotify before.

It's always possible that inotify is trying to access some
non-existent file, but without a filename that's hard to determine.

Regards

Robert




This bug report was last modified 9 years and 261 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.