-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
i cannot run in fedora x86_64 #205
Comments
Is it possible you're running an older CPU? EDIT: you might also be able to check by running |
Also, could you try running this build? https://github.com/dmunozv04/iSponsorBlockTV/actions/runs/12334728600#artifacts |
i will answer myself ... i hope you could add this info in some tutorial... i installed isbtv PYTHON VERSION ... need some requirements before (not advised + not auto installed), install scripts seems to compile something that need previous requirements:
optional: install screen and let it running in background inside a screen (or install as a systemd unit if you know how):
but ANYWAY...linux release seem broken to me (fedora 41 x86_64) ... which ubuntu.... i am not using ubuntu, i have a SERVER |
Not having specific python instructions is on purpose since it isn't a recommended install method, but I'm glad you managed to get it working. |
After doing more testing myself, the CPU you're using is old, and iSponsorBlockTV works perfectly if using a "v1" binary like the one I've linked above. You can see sample console output from fedora
|
why? i see is running fine
how do you know my cpu is old?, i hadnt posted my pc specs yes it is faily old, but it should be compatible with a wide range of pcs, while it doesnt REQUIRE newer instructions like avx512 or so... isnt? i have a pentium xeon 3ghz 12 cores, is a server processor, until a bit old i think is powerful more than enough.. dont you? |
As I've explained before, the most likely cause of the binary not running is having a CPU older than this: 64-bit Intel/AMD CPUs approximately newer than Haswell (released in 2013) and Excavator (released in 2015). Ubuntu being mentioned on GitHub actions doesn't mean that the provided binary won't run on other linux distros, as I've said before I've got it successfully running on fedora. Installing with python isn't a supported method since (as you've discovered), every linux distro has a different way of installing python, pip and other dependencies; it's just not a good experience for a regular user that doesn't want to learn how python packaging works. Finally, if I've got all your issues sorted, please close the issue. Otherwise do let me know |
i am glad i feel my problem is unrelated with my cpu arch, but more with dinamically linked binary suppossing a library file located in a path other than expected |
That's fair. If the test build linked here works (the zip file called binaries-x86_64-linux), I can offer it on releases for people with older cpus and document it |
i tested and it seem to work ... what i dont know if it works because the previous files i installed or not (libraries, etc) ... i remove v2.2.1 crashes with same log message (No interpreter found blah), there are no more binary previous versions to test... so i must think this new CI binary has changed and corrected something :D tell me if you want me to try something else |
Before opening an issue make sure that there are no duplicates and that you are on the latest version.
Describe the bug
sadly the instructions are mainly for docker... i dont have docker (and maybe never will), i have a fedora home server instead (my website, nas, some game servers, download large files, personal projects, etc)... i want to add sponsorblock to my network throught iSponsorBlockTV to skip video ads annoyances
after download linux release and run through ssh console, however although the mentioned file is in place the only message i got is:
No interpreter found for path '/root/.cache/pyapp/distributions/_14656550572188801628/python/bin/python3' in managed installations or search path
... also if i run
file <isbtb-file>
i gotiSponsorBlockTV-x86_64-linux: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=fa04c9e3abed7d75e8b2fa5ddefe3fe0ccef1845, for GNU/Linux 3.2.0, stripped
i have the (required library?) file installed
/lib64/ld-linux-x86-64.so.2
i dont know if it has something to do ...i suspect the "iSponsorBlockTV-x86_64-linux" file is not actually compiled for linux but for DEBIAN instead
To Reproduce
Steps to reproduce the behavior:
No interpreter found for path '/root/.cache/pyapp/distributions/_14656550572188801628/python/bin/python3' in managed installations or search path
Expected behavior
A clear and concise description of what you expected to happen.
i never been able to run isponsorblocktv, but i think it must be show some log of what is happening, data loaded, device detected, skip events, etc
Screenshots
If applicable, add screenshots to help explain your problem.
iSponsorBlockTV server (please complete the following information):
Apple TV (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: