Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: Antoine Levitt <antoine.levitt@gmail.com>
Cc: ding@gnus.org
Subject: Re: nnimap gets confused after hardware suspend/resume
Date: Sun, 10 Apr 2011 22:21:16 +0200	[thread overview]
Message-ID: <87y63hq2mb.fsf@member.fsf.org> (raw)
In-Reply-To: <87y63iug4c.fsf@gmail.com> (Antoine Levitt's message of "Sun, 10 Apr 2011 20:16:03 +0200")

Antoine Levitt <antoine.levitt@gmail.com> writes:

Hi Antoine,

> Sometimes, after a suspend and resume, nnimap will lose its
> connection, and fail with
>
> [...]
>
> I'm not 100% sure what triggers it, and it's hard to debug. It only
> seems to happen when I suspend for extended periods of time though
> (typically, when I suspend at night and resume the morning after.)

I cannot help you, but now that you've started a thread about that, I
cry on your shoulder.  When I suspend my computer for a sufficiently
long time and wake it up again, I sometimes see these Gnus/Emacs
behaviors:

  a) Some connections broken, but I can re-open them in the server
     buffer.  After doing so, often my Gmane groups show up completely
     unread with thousands of unread messages.  After restarting
     Emacs/Gnus, all is ok again.

  b) I see the that Gnus is fetching news (probably it was doing so
     while I suspended), and Emacs is completely locked up.  C-g
     repeatedly doesn't help, so that I have to kill it.

Bye,
Tassilo
-- 
Sent from my Emacs



  reply	other threads:[~2011-04-10 20:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10 18:16 Antoine Levitt
2011-04-10 20:21 ` Tassilo Horn [this message]
2011-04-12 15:48 ` Lars Magne Ingebrigtsen
2011-04-12 17:35   ` Antoine Levitt
2011-04-12 17:44     ` Lars Magne 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y63hq2mb.fsf@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --cc=antoine.levitt@gmail.com \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).