GNU bug report logs - #40676
28.0.50; gnus locks when reading email

Previous Next

Packages: emacs, gnus;

Reported by: Alex Branham <alex.branham <at> gmail.com>

Date: Thu, 16 Apr 2020 23:19:01 UTC

Severity: normal

Tags: fixed

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #18 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Eric Abrahamsen <eric <at> ericabrahamsen.net>
To: bug-gnu-emacs <at> gnu.org
Subject: Re: bug#40676: 28.0.50; gnus locks when reading email
Date: Fri, 17 Apr 2020 08:09:28 -0700
Alex Branham <alex.branham <at> gmail.com> writes:

> Hello -
>
> gnus locks when reading email (when trying to display the message
> contents) and asks me:
>
> Buffer " *temp*" has a running process; kill it? (y or n) y
>
> This seems to happen independently of backend, as I use nnimap and nntp.
> It also happens when reading through debbugs-gnu.
>
> Specifically, to reproduce, I do:
>
> M-x gnus
> RET (this opens an inbox)
> RET (this tries to open an email)
>
> I can then see the new window & buffer pop up with initial content like:
>
> From: <foo>
> Subject: <bar>
> To: <baz>
> Date: <fooier>
> Reply-To: <barier>
> X-Boundary: <bazier>
>
> but it's not font locked and the rest of the email doesn't show until I
> hit y or n (the email shows after hitting y or n, doesn't seem to make a
> difference).

FWIW, a " *temp*" buffer is only created in mm-util.el, in
`mm-find-buffer-file-coding-system'. My guess is that some mime handler
is calling an external process to do some sort of decoding of article
content or attachment, and that's somehow getting attached to the temp
buffer incorrectly.

Total guess!





This bug report was last modified 4 years and 291 days ago.

Previous Next


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