From: Brent Epp <brent@pdc.ca>
To: cygwin@cygwin.com
Subject: Re: mintty window flashes open and immediately closes
Date: Wed, 18 Dec 2019 02:27:00 -0000 [thread overview]
Message-ID: <980c2aad-fb2a-b2cc-ac6c-c9072e1d4b1a@pdc.ca> (raw)
In-Reply-To: <00820caa-c15d-6197-24da-fae1780fc560@pdc.ca>
This is interesting: I have a backup copy of my cygwin installation from
2 days ago. I restored it to another folder, made a shortcut... and it
works.
I'll have to run some diffs to double-check, but I'm pretty certain the
only thing that's changed in the past two days is that I ran the latest
installer today to update.
 - Brent
On 2019-12-17 17:36, Brent Epp wrote:
> Thanks, I should mention, I did try disabling my .bashrc file and
> actually my entire user directory... still didn't work.
>
> Also, mintty tells me neither of those options are valid? These are
> the options it tells me are available: https://i.imgur.com/vyMG9t6.png
>
> Also, just a correction to my original email, the shortcut was
> actually:`...mintty.exe -i /Cygwin-Terminal.ico -`
>
> The shortcut I previously stated was something I had done as a
> troubleshooting step and then pasted it into the email by mistake.
>
> Â - Brent
>
> On 2019-12-17 17:17, René Berber wrote:
>> On 12/17/2019 2:58 PM, Brent Epp wrote:
>>
>>> I've been using cygwin for years with no problems. I just updated
>>> cygwin again and I suddenly can't get into the terminal. When I click
>>> the cygwin icon, the window just flashes and immediately closes.
>>>
>>> What's interesting is that I have a number of cygwin/mintty shortcuts
>>> for SSH servers as `c:\path\to\cygwin\bin\mintty.exe /bin/ssh
>>> user@server.com`, which work just fine. I can also get in if I run
>>> `cygwin.bat` in `cmd`, `console2` or any other Windows command
>>> terminal.
>>>
>>> I've tried running the latest cygwin setup, reinstalling `mintty`, and
>>> the shortcut still fails. The shortcut is just the default target:
>>> `C:\path\to\cygwin\bin\mintty.exe /bin/bash --login -i`
>>>
>>> I don't know what else to try. What happened here and how do I fix
>>> this?
>> Probably a problem with your bash init scripts.
>>
>> Try (for the shortcut): C:\cygwin64\bin\mintty.exe --noprofile --norc -
>>
>> If that works, then start spelunking those init files (.bashrc,
>> .profile, /etc/{profile,bash.bashrc}).
>>
>> BTW you don't need to call bash in the shortcut, mintty by default opens
>> bash with those parameters; but the "-" at the end is required.
>>
>> HTH
>
>
> --
> 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
>
>
--
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-12-18 0:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 23:17 Brent Epp
2019-12-18 0:04 ` René Berber
2019-12-18 0:55 ` Brent Epp
2019-12-18 2:27 ` Brent Epp [this message]
2019-12-18 7:29 ` René Berber
2019-12-18 9:04 ` Ken Brown
2019-12-18 9:04 ` Thomas Wolff
2019-12-18 13:41 ` Takashi Yano
2019-12-18 15:10 ` Brent Epp
2019-12-21 15:13 ` Andrey Repin
2019-12-21 18:02 ` Brent Epp
2019-12-22 4:49 Jay Goldman
2019-12-28 21:27 ` Jay Goldman
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=980c2aad-fb2a-b2cc-ac6c-c9072e1d4b1a@pdc.ca \
--to=brent@pdc.ca \
--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).