search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.48k stars 822 forks source link

Files With Long Basenames or Path Components Not Opening in Windows Programs Such as Notepad #11981

Closed RandomDSdevel closed 2 months ago

RandomDSdevel commented 2 months ago

Windows Version

     Windows versions known to be affected by this issue include:

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

Kernel Version

5.15.153.1-2

Distro Version

Gentoo Linux v2.15 (custom installation)

Other Software

Windows Notepad: v11.2406.9.0

Repro Steps

  1. Inside a running WSL distribution's file system, use either an open terminal session or a Windows Explorer window you've opened to view a location there shared over 9p to create at least one plain-text file with:

    • At least a long basename and/or one or more long file path components (To ensure reproducibility, create a file with a long (base)name in a deep directory hierarchy with at least one, but ideally multiple, long path components.)

    • (Optionally, one or more of:

      • Spaces
      • Special characters allowed in both Linux and Windows file names, such as (straight) single quotes

      in the file's or files' (base)name(s))

    with any extension. (I've been editing Markdown files, so that would give any files used to reproduce this issue an extension of '.md.')

  2. Attempt to have Windows Explorer open the file in Notepad. (Presumably, your system's file type associations are already set to make Notepad the default program for editing Markdown files.)

Expected Behavior

     Notepad opens the file successfully, allowing you to edit it, as in previous versions of Windows.

Actual Behavior

     Notepad:

  1. Spawns a new, empty window for the file you asked Windows Explorer to have it open as if the requested file itself was empty.
  2. Hangs for a little bit.

  3. On top of the parent window from this list's first item, spawns a modal dialog pinned to the former in the middle saying:

    Notepad

    The system cannot find the file specified.

    with a default-focused 'OK' button in the lower right.

    (Note: While this modal dialog remains open, its parent Notepad window can't be moved around the screen by its title bar.)

  4. Pressing the Escape or Enter key on your keyboard dismisses the modal dialog pop-up, leaving an unsaved blank plain-text document behind in its parent Notepad window. You can now close this dangling Notepad window.

Known Work-Around

     Open any file affected by this issue using a Linux command-line or GUI text editor — for example, 'nano' or KWrite.

github-actions[bot] commented 2 months ago

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs Download and execute [collect-wsl-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

microsoft-github-policy-service[bot] commented 2 months ago

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!