Postman as Snap does not work (due to system-distro isolation)
Open
Nobody has claimed this yet.
bug
- Dominant language
- C++
- Stars
- 11.9k
- Forks
- 429
- PR merge metrics
- No merged PRs in 30d
Description
Windows build number:
22621.608
Your Distribution version:
Ubuntu 22.04.1
Your WSL versions:
WSL version: 0.70.0.0
Kernel version: 5.15.68.1
WSLg version: 1.0.45
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.608
Steps to reproduce:
- Install a clean WSL Ubuntu distro
- Enable Systemd
- Upgrade all packages
- sudo snap install postman
- snap run postman
WSL logs:
WslLogs-2022-10-11_20-44-43.zip
WSL dumps:
No response
Expected behavior:
To at least open the Postman window, I guess.
Actual behavior:
$ snap run postman
The disableGPU setting is set to undefined
Not disabling GPU
[1129:1011/204457.140013:ERROR:browser_main_loop.cc(1400)] Unable to open X display.
Failed to generate minidump.Segmentation fault
# In another distro I found:
❯ snap run postman
The disableGPU setting is set to undefined
Not disabling GPU
[2927:1011/204107.769083:ERROR:browser_main_loop.cc(1400)] Unable to open X display.
The futex facility returned an unexpected error code.[1] 2927 IOT instruction snap run postman
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure using the listed Windows, Ubuntu, WSL, and systemd versions, then inspect WslLogs-2022-10-11_20-44-43.zip alongside the snap run output. Trace the X display and futex failures in the WSLg codebase; done means Postman opens from the Ubuntu Snap installation without the reported crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, ubuntu
- Domain
- desktop-dev, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100