simplex-chat / simplex-chat/simplex-chat

WSL notifications don't work

Open
#2,338 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement terminal windows
Dominant language
Haskell
Stars
19.5k
Forks
1.4k
Avg merge
1d 20h
Merged PRs (30d)
71

Description

When running the SimpleX Chat terminal app v5.0.0.2 on WSL2 (1.2.5.0), I get the following error whenever a notification should appear:

> /home/jonathan/.simplex/win-toast-notify.ps1 : AuthorizationManager check failed.
At line:1 char:1
+ /home/jonathan/.simplex/win-toast-notify.ps1 "jonathan_1> " "hello"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess

When I run powershell.exe ~/.simplex/win-toast-notify.ps1, I can interactively give permission to run the script once:

Security warning
Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run
 without this warning message. Do you want to run \\wsl.localhost\Ubuntu\home\jonathan\.simplex\win-toast-notify.ps1?
[D] Do not run  [R] Run once  [S] Suspend  [?] Help (default is "D"):

I attempted to get rid of the warning by entering powershell.exe from within WSL in that directory and running " Unblock-File -Path .\win-toast-notify.ps1`, but this does not fix the problem.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with /home/jonathan/.simplex/win-toast-notify.ps1 and reproduce the notification command under WSL2 using the reported PowerShell invocation. Investigate why the script still triggers AuthorizationManager after Unblock-File, and consider the issue done when WSL notifications run without an authorization prompt or security error.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, powershell
Domain
operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.