Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting error when opening Portmaster #1371

Closed
Jcastors500 opened this issue Nov 25, 2023 · 4 comments
Closed

Getting error when opening Portmaster #1371

Jcastors500 opened this issue Nov 25, 2023 · 4 comments
Labels
bug TYPE: a report on something that isn't working stale ATTRIBUTE: this issue has not had recent activity

Comments

@Jcastors500
Copy link

What happened?

When I open portmaster, it shows an error. When I click on ok the error closes and the app works, but it's kinda annoying.

What did you expect to happen?

The app should have opened without error.

How did you reproduce it?

I can reproduce the bug just by opening the app via the start menu of windows.

Additional information

Here is the error :

image

A JavaScript error occured in the main process

Uncaught Exception:
Error: EPIPE: broken pipe, write
at Socket._write (node:internal/net:55:25)
at writeOrBuffer 12)
at _ write
at Writable.write (node:internal/streams/writable:334:10)
at console.value
at console.log (node:internal/console/constructor:360:26)
at
(C: \ Program Data\Safi ng \ P ortmaster\ -
at ChildProcess.emit (node:events:527:28)
at ChildProcess._handle.onexit

Debug-Info: https://support.safing.io/privatebin/?d9f4bbb47e306819#FNzzYe4DKM73AqfTPu7ear1921aQRM19o8bJ8tPxn6xn

@Jcastors500 Jcastors500 added the bug TYPE: a report on something that isn't working label Nov 25, 2023
@Ultratc99
Copy link

Same error, any resolution?

@Raphty
Copy link
Member

Raphty commented Dec 4, 2023

@Ultratc99 we have a presumed fix in the current beta
https://wiki.safing.io/en/FAQ/SwitchReleaseChannel

we were not able to reproduce the issue though. Feedback would be welcome

Copy link

github-actions bot commented Feb 6, 2024

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

@github-actions github-actions bot added the stale ATTRIBUTE: this issue has not had recent activity label Feb 6, 2024
Copy link

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug TYPE: a report on something that isn't working stale ATTRIBUTE: this issue has not had recent activity
Projects
None yet
Development

No branches or pull requests

4 participants
@Raphty @Jcastors500 @Ultratc99 and others