Skip to content

Invoke-Item /tmp fails on Debian with strange errors #6827

@iricigor

Description

@iricigor

Steps to reproduce

Invoke-Item /tmp

Expected behavior

Throw a PowerShell error (i.e. no default handler is available or similar).

The issue is not folder specific, i.e. it fails on any folder. It is tested on PS 6.1.0-preview.2

The issue seems to be related to #4252 and #4262, but this is more to address proper error handling than to actually implement the functionality.

Actual behavior

It throws different errors from the underlying system.
On Debian Stretch, it throws full 9 line xdg-open error stack.
screenshot_1

On Debian subsystem on Windows 10, it throws 'No such file or directory' whereas folder exists. If a folder is really not existing, it throws 'Cannot find path'
screenshot_2

Environment data

> $PSVersionTable

Metadata

Metadata

Assignees

No one assigned

    Labels

    Resolution-No ActivityIssue has had no activity for 6 months or moreWG-Cmdlets-Managementcmdlets in the Microsoft.PowerShell.Management module

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions