-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ConEmuC: Root process was alive less than 10 sec, ExitCode=0. #1773
Comments
I get the same error on windows 10 when trying to start any shell to do with powershell (bash works fine for me)
|
Reload the default tasks, and see if those work |
Same deal 😢 |
Can you post the content of the task you are running? |
Task Parameters: FWIW I also tried deleting the task parameter and running only the command, but no dice |
try PowerShell.exe. Also my default task is |
Tried both of those, no change |
well is powershell on your path? |
from vanilla command prompt:
from bash in cmder:
|
Really no idea then, can you try a nightly build? https://ci.appveyor.com/project/MartiUK/cmder/build/1.0.667-master/artifacts |
Nightly does the same thing 😂 at this point I'd point the blame at my laptop - but it's been freshly imaged. I'll go back to older builds and try that now 😞 |
I asked in the ConEmu project and they informed me this: @TeamSpen210 |
not sure why you closed this. powershell crashes... |
Probably because this is not a cmder issue. |
According to TeamSpen210 this is a feature of convenience. I tried to reproduce the same error using the powershell and it did not occur. @ittayd Can you tell me how to reproduce ? |
Well, obviously something in my environment that causes it. But I have no idea how to debug it. |
@ittayd Questions:
You could launch a Cmder Cmd session and run |
1. yes
2. yes
3. no such file in cmder and I can't share the ps1 file. it starts ssh
agent which seems to cause the crash
4. no
it turns out the culprit is the conemuhk injection. once i disabled this,
everything seems fine.
attached the diag file
…On Tue, Dec 11, 2018 at 3:26 PM Dax T Games ***@***.***> wrote:
@ittayd <https://github.com/ittayd> Questions:
1. I assume Powershell works outside Cmder?
2. Do Cmder Cmd and Bash sessions work?
3. If 1 and 2 = Yes what are the contents of
%cmder_root%\config\user_profile.ps1 and from Powershell the contents
of the $profile file.
4. Are there any *.ps1 files in %cmder_root%\config\profile.d
You could launch a Cmder Cmd session and run cmder_diag.cmd and post the
output. This may give us enough of a picture of your environment to help.
Make sure you look at the output and sanitize it before posting, it
probably doesn't contain anything sensitive but just make sure.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1773 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACCMLG2p2PI5eRI0FVM9zWx8r7e9re9ks5u37KFgaJpZM4T9FBE>
.
|
@ittayd Glad you found the issue. If you do not have |
no, nothing. iirc, i update cmder a month ago.
…On Tue, Dec 11, 2018 at 4:59 PM Dax T Games ***@***.***> wrote:
@ittayd <https://github.com/ittayd> Glad you found the issue.
If you do not have %cmder_root%\config\user_profile.ps1 you are running
an older version OR Powershell never got far enough in Cmder to actually
create one for you. Now that you say it is working it should exist now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1773 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACCMAZD3lMnfSfD6hHyOPHpJluhI3uDks5u38hZgaJpZM4T9FBE>
.
|
@ittayd then something is still broken because it should self create. The diag file did not come through. I assume you attached it to an email. |
I was using the cmder with bash and closed with using control + D after about 3 seconds, then the following displayed the following message:
ConEmuC: Root process was alive less than 10 sec, ExitCode = 0.
Would you like to know if this is a bug or just a message ?
Can you corrupt something in the cmder or ConEmu?
Thanks.
The text was updated successfully, but these errors were encountered: