Skip to content

Setting startingDirectory to WSL path causes indefinite application hang #9541

@zaxbux

Description

@zaxbux

Environment

Windows build number: 19041.867
Windows Terminal version (if applicable): 1.6.10571.0

Steps to reproduce

Add the following startingDirectory to a profile like so:

{
  "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
  "hidden": false,
  "name": "Ubuntu-20.04",
  "source": "Windows.Terminal.Wsl",
  "startingDirectory": "\\\\wsl$\\Ubuntu-20.04\\home\\zach"
}

Expected behavior

Terminal launches profile in starting directory. This has worked for awhile, issue started occuring after some recent updates (either Windows or Terminal).

Actual behavior

Terminal hangs forever when starting profile from new tab dropdown, jumplist, etc.

wt_bug

Note: this screenshot was taken after the startingDirectory was added in my settings.json while application was running. Terminal crashes as soon as the updated profile was clicked. Terminal launched fine and profile worked before adding line.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-TerminalConnectionIssues pertaining to the terminal<->backend connection interfaceIssue-BugIt either shouldn't be doing this or needs an investigation.Priority-2A description (P2)Product-TerminalThe new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions