can`t start mintty - Githubissues

drowsysword / mintty

Automatically exported from code.google.com/p/mintty

0 stars 0 forks source link

can`t start mintty #361

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

mintty show this log:
\Documents and Settings\lqchu: No such file or directory
but this folder  C:\Documents and Settings\lqchu is exist

Original issue reported on code.google.com by chuliqi...@gmail.com on 21 Nov 2012 at 6:30

Attachments:

minitty.png

GoogleCodeExporter commented 8 years ago

Please provide the information that was requested in the issue template.

What steps will reproduce the problem?
What is the expected output? What do you see instead?
What versions of mintty, Cygwin/MSYS, and Windows are you using?

Original comment by andy.koppe on 1 Dec 2012 at 6:39

Changed state: Waiting

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?

   it  happen at first instanced started,when second instanced started(first instanced is exiting),it is ok.

What is the expected output? What do you see instead?
   i expected second instanced showing at first started.

What versions of mintty, Cygwin/MSYS, and Windows are you using?
   mintty 1.1.2,windows xp.

Original comment by chuliqi...@gmail.com on 3 Dec 2012 at 1:17

Attachments:

[first instanced.png](https://storage.googleapis.com/google-code-attachments/mintty/issue-361/comment-2/first instanced.png)

GoogleCodeExporter commented 8 years ago

 second instanced showing

Original comment by chuliqi...@gmail.com on 3 Dec 2012 at 1:18

Attachments:

[second instanced.png](https://storage.googleapis.com/google-code-attachments/mintty/issue-361/comment-3/second instanced.png)

GoogleCodeExporter commented 8 years ago

sorry,i have a mistakes word.
when second instanced started(first instanced is existing)

Original comment by chuliqi...@gmail.com on 3 Dec 2012 at 1:20

GoogleCodeExporter commented 8 years ago

Apparently mintty is attempting to invoke your Windows home directory as your 
shell (instead of something like bash). This would happen if the SHELL variable 
was wrongly set to your home directory, or, perhaps more likely, if /etc/passwd 
is set up wrongly. In /etc/passwd, the entry for the default shell directly 
follows the one for the home directory, so if the formatting is wrong the home 
directory might end up being interpreted as the default shell.

Have you customised your /etc/passwd? Attaching it here might help clarify the 
problem.

Original comment by andy.koppe on 3 Dec 2012 at 12:46

GoogleCodeExporter commented 8 years ago

Original comment by andy.koppe on 3 Jan 2013 at 11:00

Changed state: Rejected