From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cygwin snapshots after 23, Feb. ocasionally destroys windows logon session
Date: Mon, 04 Mar 2019 18:10:00 -0000 [thread overview]
Message-ID: <87ef7mo6i4.fsf@Rainer.invalid> (raw)
In-Reply-To: <20190305002849.fdb1c8db14f8f83e5210553f@nifty.ne.jp> (Takashi Yano's message of "Tue, 5 Mar 2019 00:28:49 +0900")
Takashi Yano writes:
> I encountered a problem with cygwin snapshots after 23, Feb.
> If I login to cygwin via ssh and logout from ssh session,
> explorer sometimes gets into erroneous state. Most of
> operations cannot be done on explorer.
Yup, I've had this happen, too (20190303 snapshot).
Btw, if this happens to you in an RDP session on a machine in some rack
somewhere… do not lock the screen (either actively or through timer
expiration. You will need a second account that can kill the first
session to recover. INstead, you need to sign out at the first signs of
this occuring.
> The following modification seems to cause this problem.
> But I am not sure what is wrong with this code.
This makes me wonder what Windows does when you log out of your desktop
session…
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-03-04 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 15:28 Takashi Yano
2019-03-04 15:57 ` Corinna Vinschen
2019-03-04 16:06 ` Corinna Vinschen
2019-03-04 16:39 ` Corinna Vinschen
2019-03-04 17:26 ` Bill Stewart
2019-03-05 12:16 ` Takashi Yano
2019-03-05 12:46 ` Corinna Vinschen
2019-03-04 18:10 ` Achim Gratz [this message]
2019-03-04 19:35 ` Andrey Repin
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=87ef7mo6i4.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).