From: Jean Louis <bugs@gnu.support>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Michael Albinus <michael.albinus@gmx.de>, 42374@debbugs.gnu.org
Subject: bug#42374: 28.0.50; too many tramp messages after computer sleep
Date: Wed, 9 Dec 2020 18:31:50 +0300 [thread overview]
Message-ID: <X9Dt5tEaDZDGW5An@protected.rcdrun.com> (raw)
In-Reply-To: <878sa7101s.fsf@gnus.org>
* Lars Ingebrigtsen <larsi@gnus.org> [2020-12-09 18:18]:
> Jean Louis <bugs@gnu.support> writes:
>
> > * Lars Ingebrigtsen <larsi@gnus.org> [2020-10-26 18:50]:
> >> Jean Louis <bugs@gnu.support> writes:
> >>
> >> >> > How do I turn off desktop-auto-save? Variable is not there to
> >> >> > customize.
> >> >>
> >> >> M-x desktop-save-mode
> >> >
> >> > Thank you, I turned it off, but I cannot replicate easily.
> >>
> >> Did you make any further progress in replicating this?
> >
> > Computer was put to sleep many times, it can even be I was reporting
> > from other computer but this one. It was regular error after sleep. So
> > I turned off desktop-save
>
> OK, so it sounds unlikely that we'll make further progress on this bug,
> and I'm closing this bug report.
Bug could be archived or otherwise taged but not closed. As the issue
is not closed by its definition. The workflow to close the bug just
because there is no more information about that does not necessarily
solve the issue.
Problem is in the desktop-save that does something that I cannot
easily and speedy replicate. When desktop-save is turned on, and
computer goes to sleep, after some unknown time that starts
happening. As I am busy I do not test malfunction as it disturbs the
work. But I could try again.
> > However, even if I do tramp-cleanup-all-connections I cannot access
> > SSH Tramp.
>
> This sounds like a different bug -- if you're still seeing that one,
> please open a new bug report.
I got impression only that those were related as messages came
together.
By the way I am using Emacs in interrupted way all the time, you may
be lucky having it all nice and good, not so on my side. We are
debugging memory leak and getting mtraces takes days. It happens in
working instance, not in empty running Emacs session. If I start
turning on desktop-mode and notebook sleep there are too many things
at once to handle and observe.
Don't close my bugs if they are not solved.
next prev parent reply other threads:[~2020-12-09 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 17:30 bug#42374: 28.0.50; too many tramp messages after computer sleep Jean Louis
2020-07-16 7:34 ` Michael Albinus
2020-07-16 8:39 ` Jean Louis
2020-07-16 11:14 ` Michael Albinus
2020-07-21 12:06 ` Jean Louis
2020-07-21 15:42 ` Michael Albinus
2020-07-24 7:08 ` Jean Louis
2020-10-26 15:49 ` Lars Ingebrigtsen
2020-10-28 12:01 ` Jean Louis
2020-12-09 15:17 ` Lars Ingebrigtsen
2020-12-09 15:31 ` Jean Louis [this message]
2020-12-09 15:39 ` Lars Ingebrigtsen
2020-12-09 16:17 ` Jean Louis
2020-12-09 16:48 ` Lars Ingebrigtsen
2020-12-09 17:23 ` Jean Louis
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=X9Dt5tEaDZDGW5An@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=42374@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
/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).