Open sergani opened 1 year ago
Digging around it seems like a Ventura bug... will update this case if ever it's resolved by Apple :/
Digging around it seems like a Ventura bug... will update this case if ever it's resolved by Apple :/
I think it's caused by call generatePrivoxyLauchAgentPlist every time config changed. No?
Open #1461 to try to fix this issue.
Digging around it seems like a Ventura bug... will update this case if ever it's resolved by Apple :/
I think it's caused by call generatePrivoxyLauchAgentPlist every time config changed. No?
Possibly, I'm not an expert really to comment. I can see a new case was raised to address the issue, so thank you.
It seems to have been an issue with MacOS indeed that was resolved in 13.3: https://youtu.be/f3slUk94QM0
I’m yet to upgrade and see if that gets resolved or not.
Just wanted to report that Ventura 13.3 didn't solve the issue.
Hello, I wanted to report back that 1.10.2 fixed the issue except in one condition; when starting the computer from a shutdown state I get the notifications.
same problem 13.5.2 (22G91)
same problem 13.5.2 (22G91)
+1, I've tried sfltool resetbtm
and deleted it from LaunchAgents. I'm getting very frustrated at Apple for these issues.
14.0 (23A344) has the same issues. mac mini
This issue is relevant for Sonoma 14.6.1 (23G93). I am getting new alerts after every system reboot. Also wondering why I only get SS alerts... 🤔
Describe the bug Not sure if this is a MacOS issue, or a SS one. Basically whenever I start or stop SS two notifications pop up that relate to ss-local and privacy scripts, indicating that both could run in the background. The problem is that these notifications stick around and have to be cleared manually.
To Reproduce Just stop or start the service. Happens every time. It also happens when changing modes even if the proxy is turned off.
Expected behavior This behavior is accepted and expected on the first time ever these scripts are added to the background items. Subsequent turn on/off actions should not invoke these notifications.
Screenshots
System and Shadowsocksx-NG version: (please complete the following information):
Diagnoisis file: ShadowsocksX-NG_diagnose_20230314_094029.txt
ss-local.log None found
Application log None found
Crash Log NA
Additional context Add any other context about the problem here.