conemu-cyg-64.exe conflict with WIN10 1903 and Cygwin 3.1.1 (needs confirmation) (title updated) #2035

userdocs · 2019-12-19T16:21:54Z

Edit - The cause of this issue has been identified. See this comment - #2035 (comment)

Versions

ConEmu build: 191012 x64 Installer
OS version: Windows 10 x64 1903
Used shell version - Cygwin bash - Cygwin 3.1.1

Problem description

When using the connector as described here CygwinMsysConnector with the current Cygwin 3.1.1 release certain keys stop working - like the arrow keys and delete.

This configuration does not work:

set CHERE_INVOKING=1
 & set "PATH=C:\cygwin64\bin;%PATH%"
 & %ConEmuBaseDirShort%\conemu-cyg-64.exe /usr/bin/bash.exe --login -i -new_console:p:C:"C:\cygwin64\Cygwin.ico"

This will work: (removed - %ConEmuBaseDirShort%\conemu-cyg-64.exe)

set CHERE_INVOKING=1
 & set "PATH=C:\cygwin64\bin;%PATH%"
 &  /usr/bin/bash.exe --login -i -new_console:p:C:"C:\cygwin64\Cygwin.ico"

Steps to reproduce

Windows 10 1903 x64 (possibly related to this specific build, i will try a VM of an older edition)
Install Cygwin x64
Install ConEmu x64

Note: I had an older version of Cygwin on WIN10 1903 x64 and it worked fine. I updated Cygwin to 3.1.1 and rebooted and then experienced the described issue.

Actual results

You can type but arrow keys and delete doe not work (possibly more keys are affected)

Expected results

That these keys work as they did previously.

The text was updated successfully, but these errors were encountered:

9numbernine9 · 2019-12-19T18:19:55Z

Thanks for posting this issue - I think I'm running into the same problem and I thought I was starting to go crazy. I'm running Windows 10 1809 with Cygwin 3.1.0 but the behaviour is otherwise the same.

Looking at the release notes for Cygwin 3.1.0, they've added a feature that adds support for pseudo consoles in PTY: Pseudo console is a new feature in Windows 10 1809, which provides console APIs on virtual terminal. With this patch, native console applications can work in PTYs such as mintty, ssh, gnu screen or tmux.

I think this new feature might be related to the issue; if you explicitly disable pseudo console support in Windows by changing the registry value HKEY_CURRENT_USER\Console\ForceV2 from 1 to 0 and open a new {Cygwin bash} shell, everything should work fine (or at least it does for me). Note that I don't recommend this is a permanent solution - this might break some other app on your machine that expects this feature to be enabled!

userdocs · 2019-12-19T19:10:14Z

Which is why when i look at the description of the conemu-cyg connector:

This helper tool is an attempt to create the symbiont of POSIX enabled pty and WinAPI full-featured terminal.

I wonder what the best temporary fix is and i if need the connector any more? Number 1 seems to work for me and what i need.

1: Disable the connector in the Startup/Tasks by removing the command.

2: A registry edit described here #2035 (comment)

edit - No - Option 1 will cause the loss of functionality and generally cause odd stuff to happen and is not a solution.

zouhair · 2019-12-21T18:46:39Z

I ended up using this line in the startfile and it seem to fix most of the problem, but I don't think it's still a total fix:

set CHERE_INVOKING=1 & set "PATH=C:\cygwin\bin;%PATH%" & %ConEmuBaseDirShort%\conemu-cyg-64.exe -new_console:p C:\cygwin\bin\bash.exe --login -i -cur_console:p1 -new_console:d:C:\cygwin\home\poboxy -new_console:C:"C:\cygwin\Cygwin.ico"

userdocs · 2019-12-21T19:13:37Z

If i debug my active process i get this over and over on Cygwin 3.1.1

{6612.1408} MS_VC_THREADNAME_EXCEPTION at 0x00007FF87BD9A839 flags 0x00000000 FC=1

Maximus5 · 2019-12-21T19:43:57Z

If i debug my active process i get this over and over on Cygwin 3.1.1
{6612.1408} MS_VC_THREADNAME_EXCEPTION at 0x00007FF87BD9A839 flags 0x00000000 FC=1

This exception is not a "real" exception. It's used to set a name for a thread, which is useful during debugging.
This type of exception should be skipped manually.

Maximus5 · 2019-12-21T19:45:10Z

I need reanimate my work on pty definitely. As not only wsl requires it...

userdocs · 2019-12-21T19:49:51Z

Ok, thanks for clarifying that. Is there any info I can provide like the dumps that will help or is that not necessary with this particular issue?

amartinr · 2019-12-26T08:01:06Z

I'm experiencing the same problem. I also used a similar solution like you used, @userdocs. I'm using TERM=xterm-256color, if that matters. The thing is that I'm missing a line feed every time I hit the tab key for autocompletion or the enter key.

amartinr@myhost /
$ ls
     bin/                 Cygwin.ico           etc/                 proc/                usr/
                                                                                             cygdrive/
        Cygwin-Terminal.ico  home/                sbin/                var/
                                                                           Cygwin.bat           dev/
           lib/                 tmp/

amartinr@myhost /
$ ls
     bin          Cygwin.bat  Cygwin-Terminal.ico  etc   lib   sbin  usr
cygdrive  Cygwin.ico  dev                  home  proc  tmp   var

I found out that I don't have this problem if I use mintty, but mintty hijacks many keybindings...

set CHERE_INVOKING=1 & set "PATH=%ConEmuDrive%\cygwin64\bin;%PATH%" & C:\cygwin64\bin\mintty.exe

anenviousguest · 2019-12-27T21:03:05Z

If that helps, I noticed that in the ANSI log file the arrows and Del keystrokes do not even appear.

Bokonon-ONI · 2019-12-28T18:01:32Z

Same specs here as posted above and I am also experiencing this issue. One thing to add that I didn't see posted, not sure it's relevant, I ran cygwin's bash.exe from both powershell and the regular Windows command prompt and they both behave as expected, the arrow keys work just fine.

tyan0 · 2019-12-29T04:33:14Z

Hello.

I looked into this problem and found the cause is the patch I proposed on April 2019 for cygwin console handler. I will propose revised patch for cygwin shortly.

FYI: This is not related to pseudo console support in cygwin.

userdocs · 2019-12-29T11:58:06Z

Thanks! I was just guessing as all i knew was that by updating Cygwin it broke the ConEmu integration but I had no idea why. I'll update the main comment to link to yours and wait for it to be fixed.

Do you have a rough estimate how long that process take might take?

tyan0 · 2019-12-29T13:02:51Z

Do you have a rough estimate how long that process take might take?

I'm not sure. I plan to submit the patch in a few days. After that, the maintainer will determine whether the patch is appropriate. If they accept the patch, it will be pushed to git repositry. However, it might not released soon. The timing of new release is decided by maintainer.

The release dates of cygwin in the past were:
3.0.0-1: Feb. 17, 2019
3.0.1-1: Feb. 20, 2019
3.0.2-1: Mar. 6, 2019
3.0.3-1: Mar. 10, 2019
3.0.4-1: Mar. 16, 2019
3.0.5-1: Mar. 31, 2019
3.0.6-1: Apr. 7, 2019
3.0.7-1: May.1, 2019
3.1.0-1: Dec. 17, 2019
3.1.1-1: Dec. 18, 2019
3.1.2-1: Dec. 22, 2019

Bokonon-ONI · 2019-12-29T15:27:27Z

So @tyan0 are you saying the fix is on the cygwin side? Thanks for the quick reply. By any chance, do have a link to a changeset/checkin/PR with either the fix or the code that broke, I'm a developer but haven't worked on this kind of stuff and am just curious. Thanks again!

tyan0 · 2020-01-01T07:01:18Z

By any chance, do have a link to a changeset/checkin/PR with either the fix or the code that broke, I'm a developer but haven't worked on this kind of stuff and am just curious. Thanks again!

The old patch which causes the issue was:
https://www.cygwin.com/ml/cygwin-patches/2019-q2/msg00013.html

The revised patch is:
https://www.cygwin.com/ml/cygwin-patches/2020-q1/msg00004.html

tyan0 · 2020-01-15T03:07:15Z

A new cygwin has not yet been released, but a developer snapshot that fixes this problem is ready.
https://cygwin.com/snapshots/
Please test.

vehovsky · 2020-01-15T08:00:04Z

@tyan0 thanks! I can confirm it's working.

mooninite · 2020-01-15T13:15:30Z

Yes, thanks. The Jan 14th snapshot fixed the issue for me, too.

tyan0 · 2020-01-17T15:43:58Z

Thanks for testing!

userdocs · 2020-01-17T17:02:35Z

@tyan0 snapshot 20200114 fixed it for me as well. Thanks.

GameDr04 · 2020-01-22T23:45:41Z

I wasn't able to get the patch to work but considering the many successes before me, it's probably user error.

Instead, I removed and reinstalled Cygwin, but explicitly chose version 3.0.7 at install-time.
That worked for me.

pccasto · 2020-01-26T02:30:07Z

I had issues with the 2020-01-24. Not sure if they were due to my method of install, or what.
However the 2020-01-14 installed cleanly and fixed this issue.

ravermeister · 2020-01-26T16:41:13Z

for me the 2020-01-24 works too:

[ravermeister@virusmaster 24.01.2020]$ md5sum.exe cygwin1-20200124.dll
0f481acb062a24d0b503eb1b47776234 *cygwin1-20200124.dll
[ravermeister@virusmaster 24.01.2020]$ md5sum.exe /usr/bin/cygwin1.dll
0f481acb062a24d0b503eb1b47776234 */usr/bin/cygwin1.dll
[ravermeister@virusmaster 24.01.2020]$

chrisbanm · 2020-02-13T17:02:13Z

I downloaded cygwin1-20200212.dll for 64 bit and it also fixed the arrow key functionality. I haven't done enough testing to see if it broke anything else, but the arrows work just fine.

userdocs · 2020-02-19T12:25:12Z

They have release update 3.1.4-1

https://cygwin.com/ml/cygwin-announce/2020-02/msg00006.html

Can people test and confirm please.

Edit: seems to be working as expected for me.

lokeshgovindu · 2020-02-19T16:15:07Z

I have tested, it's working fine.

…

On Wed, 19 Feb, 2020, 17:55 userdocs, ***@***.***> wrote: They have release update 3.1.4-1 https://cygwin.com/ml/cygwin-announce/2020-02/msg00006.html Can people test and confirm please. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2035?email_source=notifications&email_token=ACCDOM7O44OHZLPFDKMYKCLRDUQKXA5CNFSM4J5KJJR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMHTGKA#issuecomment-588198696>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACCDOM4JRX45AJ4C2DN2HI3RDUQKXANCNFSM4J5KJJRQ> .

pccasto · 2020-02-19T16:28:46Z

Second confirmation - 3.1.4-1 installed and works for me as well.
$ uname -a
CYGWIN_NT-10.0 <my_hostname> 3.1.4(0.340/5/3) 2020-02-19 08:49 x86_64 Cygwin

Thanks again!

chrisbanm · 2020-02-19T16:35:54Z

Confirmed. I have also updated to CygWin 3.1.4 x86_64 and the arrow key issues are fixed. The arrow keys work correctly with ConEmu 191012[64] on Win 10 1909.

flyser · 2020-02-19T17:55:44Z

Unfortunately cygwin 3.1.4 did not fix this issue for me on Windows 10 1903. Do I need a special conemu version or setting?

userdocs · 2020-02-19T19:32:48Z

The test would work or fail with the documentation example:

set CHERE_INVOKING=1
 & set "PATH=C:\cygwin64\bin;%PATH%"
 & %ConEmuBaseDirShort%\conemu-cyg-64.exe /usr/bin/bash.exe --login -i -new_console:p:C:"C:\cygwin64\Cygwin.ico"

It may sound silly, but try restarting your OS. Please see my note in the original issue:

Note: I had an older version of Cygwin on WIN10 1903 x64 and it worked fine. I updated Cygwin to 3.1.1 and rebooted and then experienced the described issue.

cy18 · 2020-03-02T02:34:08Z

My problem has been fixed with cygwin 3.1.4 on Windows 10 1909.

Inlight-by · 2020-05-29T11:13:04Z

My problem has been fixed with cygwin 3.1.4 on Windows 10 1909.

Same thing, the issue was gone after updating cygwin to 3.1.4 version

cebaa · 2020-07-10T13:27:09Z

Working for me as well on cygwin 3.1.5 and ConEmu 200615.

@userdocs Probably worth closing this if it's fixed for you, just so others are aware (and so Maximus5 has one less bug to track, I assume that's helpful to him).

userdocs changed the title ~~conemu-cyg-64.exe conflict with WIN10 1809 and Cygwin 3.1.1 (needs confirmation)~~ conemu-cyg-64.exe conflict with WIN10 1903 and Cygwin 3.1.1 (needs confirmation) (title updated) Dec 19, 2019

userdocs mentioned this issue Dec 30, 2019

Not work command history Up Arrow #2037

Open

tyan0 mentioned this issue Jan 7, 2020

Space padded to the Prompt #2045

Open

pccasto mentioned this issue Jan 26, 2020

Arrow keys not working in Bash for Windows #629

Closed

userdocs closed this Oct 14, 2020

Maximus5 / ConEmu

conemu-cyg-64.exe conflict with WIN10 1903 and Cygwin 3.1.1 (needs confirmation) (title updated) #2035

conemu-cyg-64.exe conflict with WIN10 1903 and Cygwin 3.1.1 (needs confirmation) (title updated) #2035

userdocs commented Dec 19, 2019 •

edited

9numbernine9 commented Dec 19, 2019

userdocs commented Dec 19, 2019 •

edited

zouhair commented Dec 21, 2019

userdocs commented Dec 21, 2019

Maximus5 commented Dec 21, 2019

Maximus5 commented Dec 21, 2019

userdocs commented Dec 21, 2019

amartinr commented Dec 26, 2019

anenviousguest commented Dec 27, 2019

Bokonon-ONI commented Dec 28, 2019 •

edited

tyan0 commented Dec 29, 2019

userdocs commented Dec 29, 2019

tyan0 commented Dec 29, 2019

Bokonon-ONI commented Dec 29, 2019

tyan0 commented Jan 1, 2020

tyan0 commented Jan 15, 2020

vehovsky commented Jan 15, 2020

mooninite commented Jan 15, 2020

tyan0 commented Jan 17, 2020

userdocs commented Jan 17, 2020

GameDr04 commented Jan 22, 2020

pccasto commented Jan 26, 2020

ravermeister commented Jan 26, 2020

chrisbanm commented Feb 13, 2020

userdocs commented Feb 19, 2020 •

edited

lokeshgovindu commented Feb 19, 2020

pccasto commented Feb 19, 2020 •

edited

chrisbanm commented Feb 19, 2020

flyser commented Feb 19, 2020 •

edited

userdocs commented Feb 19, 2020

cy18 commented Mar 2, 2020

Inlight-by commented May 29, 2020

cebaa commented Jul 10, 2020

Maximus5 / ConEmu

Sponsor Maximus5/ConEmu

conemu-cyg-64.exe conflict with WIN10 1903 and Cygwin 3.1.1 (needs confirmation) (title updated) #2035

conemu-cyg-64.exe conflict with WIN10 1903 and Cygwin 3.1.1 (needs confirmation) (title updated) #2035

Comments

userdocs commented Dec 19, 2019 • edited

Edit - The cause of this issue has been identified. See this comment - #2035 (comment)

Versions

Problem description

Steps to reproduce

Actual results

Expected results

9numbernine9 commented Dec 19, 2019

userdocs commented Dec 19, 2019 • edited

zouhair commented Dec 21, 2019

userdocs commented Dec 21, 2019

Maximus5 commented Dec 21, 2019

Maximus5 commented Dec 21, 2019

userdocs commented Dec 21, 2019

amartinr commented Dec 26, 2019

anenviousguest commented Dec 27, 2019

Bokonon-ONI commented Dec 28, 2019 • edited

tyan0 commented Dec 29, 2019

userdocs commented Dec 29, 2019

tyan0 commented Dec 29, 2019

Bokonon-ONI commented Dec 29, 2019

tyan0 commented Jan 1, 2020

tyan0 commented Jan 15, 2020

vehovsky commented Jan 15, 2020

mooninite commented Jan 15, 2020

tyan0 commented Jan 17, 2020

userdocs commented Jan 17, 2020

GameDr04 commented Jan 22, 2020

pccasto commented Jan 26, 2020

ravermeister commented Jan 26, 2020

chrisbanm commented Feb 13, 2020

userdocs commented Feb 19, 2020 • edited

lokeshgovindu commented Feb 19, 2020

pccasto commented Feb 19, 2020 • edited

chrisbanm commented Feb 19, 2020

flyser commented Feb 19, 2020 • edited

userdocs commented Feb 19, 2020

cy18 commented Mar 2, 2020

Inlight-by commented May 29, 2020

cebaa commented Jul 10, 2020

userdocs commented Dec 19, 2019 •

edited

userdocs commented Dec 19, 2019 •

edited

Bokonon-ONI commented Dec 28, 2019 •

edited

userdocs commented Feb 19, 2020 •

edited

pccasto commented Feb 19, 2020 •

edited

flyser commented Feb 19, 2020 •

edited