WSL Bash - .profile is not read

[oskargargas]

Versions

ConEmu build: 170910 x64
OS version: Windows 10 x64, 1709, 16299.19
Used shell version: WSL, Bash 4.3.48(1)-release (not sure how to check WSL version but it's fully updated for the day of this post)

Problem description

.profile is not read by ConEmu {bash} shell which leads to problems like default $PATH is not set.

In PATH folders set by default in .profile in Ubuntu/WSL Python pip things are installed. Of course one can modify path .bashrc but those are by default in .profile.

Steps to reproduce

1. Add echo (or whatever) to .profile
2. Open new shell in ConEmu
3. Verify that .profile was not read

Actual results

.profile is not read by ConEmu {bash} shell

Expected results

.profile is read by shell in ConEmu like it's read by default WSL terminal.

[Maximus5]

What did you compare with? Where.profile is working

[oskargargas]

Default terminal installed with WSL (exactly Ubuntu from Windows Store after recent Fall Creators update). The one with ubuntu-like icon. And apparently windows tells me it's called Ubuntu. Yeah, for sure it is it.

[Maximus5]

This looks like Microsoft bug.
If you run wsl.exe there's no way to trigger .profile.

[Maximus5]

If you had installed previously bash.exe (legacy WSL), did you uninstall it by lxrun /uninstall?
As for me, legacy version blocked .profile from loading by wsl.exe.

[mhofman]

FYI, this might be coming natively: rprichard/wslbridge#18

[athrunsun]

@Maximus5 My windows 10 is version 1703, how do I install wsl.exe? I don't have that one in my system.

[mhofman]

Update to the Windows 10 Fall Creator Update (1709).

[mhofman]

Until this is supported natively by wslbridge, I've managed to get .profile to execute, i.e. get an interactive login shell by executing the connector this way:

%ConEmuBaseDirShort%\conemu-msys2-64.exe --wsl -cur_console:pm:/mnt - -t -- /bin/bash -i -l

The -t is to get wslbridge to open a pty since we're executing a command.
Of course the -i -l is to get Bash's interactive login shell.
Anything after the first - is the args passed to wslbridge.exe.
Anything after the -- is the command executed by wslbridge-backend.

[Maximus5]

The same is done automatically by connector. 12 days ago.

[mhofman]

Correct, but I didn't see a new connector release with that code change.

Also, still useful information for anyone who wants to run a different shell, since wslbridge doesn't respect the user's default shell.
Also, since the connector now explicitly sets the command to execute, when wslbridge does get around to natively support login shell or user's default shell, this change will have to be undone.

[Maximus5]

Connector is bundled into ConEmu. Wasn't it updated in alpha?

[mhofman]

I'm running the preview channel.

[rolandas-valantinas]

Latest alpha - .inputrc is not used from ~/ directory. Contents of .inputrc

$include /etc/inputrc
"\e[A": history-search-backward # Arrow Up
"\e[B": history-search-forward  # Arrow Down

Found this Maximus5/cygwin-connector#3 (comment) and it works. Any reason normal Ubuntu keys not working? I have AppKeys and XTerm selected.

However, it stops working after few minutes or few lines and arrows return to their previous function - really annoying! Gonna switch back to Mintty as it doesn't have any of these issues

Also terminals still starts in /mnt/c/Users not in ~/

[Maximus5]

@rolandas-valantinas Your question is offtopic because your .inputrc is read definitely.
"Normal" Ubuntu keys have two encoding modes, and when you have checked AppKeys you get ^[OA, when AppKeys are off - ^[[A.

[Maximus5]

The issue is closed due to

• WSL Bash - .profile is not read #1298 (comment)
• WSL Bash - .profile is not read #1298 (comment)