-
-
Notifications
You must be signed in to change notification settings - Fork 11.4k
ERROR: '/usr/local/share/scrcpy/scrcpy-server' does not exist or is not a regular file #1870
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
Comments
What is the result of? echo $SCRCPY_SERVER_PATH ? |
The result for echo $SCRCPY_SERVER_PATH and
are root@rayan: scrcpy v1.16 from sisco311 installed |
cc @sisco311 |
@littleIdiotperson Could you try building it manually (instead of using the snap package)? https://github.com/Genymobile/scrcpy/blob/master/BUILD.md |
@rom1v Thank you rom1v for ur care about fixing my problem. The output of run-tme dependencies is
and from client build dependencies is
the meson my system is going to install is version 0.45.1 which is not supported for scrcpy as far as I know.. why didn't scrcpy detected that I have already installed meson and the output of meson --version is
is this snap issues or what ? either scrcpy can't detect meson or meson is installed wrong or something else idk? |
Just searched for "scrcpy-server" in system files to detect where it went, I found it in the directory |
+1 |
Environment
Describe the bug
A clear and concise description of what the bug is.
whenever I install scrcpy this error came out ERROR: '/usr/local/share/scrcpy/scrcpy-server' does not exist or is not a regular file
and when I go to the directory I see NO scrcpy folder! Even after creating 2 folders (scrcpy and scrcpy-server) the error still there
Please notice I already tried looking for issues #1002 and #1692 but I don't know how to apply the solution for my machine, please Explain in details what should I do
On errors, please provide the output of the console (and
adb logcat
if relevant).Please do not post screenshots of your terminal, just post the content as text instead.
The text was updated successfully, but these errors were encountered: