You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cannot select the sunshine binary in "Privacy" System Preferences.
Binary File Shows up as document File.
Additionally MacOS seems to think it is a document with extension ".0"
This is on a relatively fresh install.
Maybe this is not a sunshine issue but a macports issue.
Is anyone else seeing this?
Expected Behavior
Able to select binary file "/opt/local/bin/sunshine-0.16.0" under "System Preferences" -> "Privacy" -> "Screen Capture"
Neither pressing (Plus Symbol) , nor dragging and dropping works.
From terminal when you execute sunshine it will ask to change the permissions. It will show as terminal having the permissions, which is probably not the greatest option.
We could use some help on improving the macos packages, though.
Let's close this and move any relevant details to #186 as they are pretty close to the same issue.
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the nightly release?
Describe the Bug
Cannot select the sunshine binary in "Privacy" System Preferences.
Binary File Shows up as document File.
Additionally MacOS seems to think it is a document with extension ".0"
This is on a relatively fresh install.
Maybe this is not a sunshine issue but a macports issue.
Is anyone else seeing this?
Expected Behavior
Able to select binary file "/opt/local/bin/sunshine-0.16.0" under "System Preferences" -> "Privacy" -> "Screen Capture"
Neither pressing (Plus Symbol) , nor dragging and dropping works.
Additional Context
Tested with nightly release
2b1514b
Intel Mac with MacOS 12.6.2
Host Operating System
macOS
Operating System Version
12.6.2
Architecture
64 bit
Sunshine commit or version
nightly - 2b1514b
Package
macOS - Portfile
GPU Type
Intel
GPU Model
none
GPU Driver/Mesa Version
unknown
Capture Method (Linux Only)
No response
Relevant log output
The text was updated successfully, but these errors were encountered: