Linux: CMD could not be loaded
See original GitHub issueAttempting to load a DRM protected video results in errors stating permission issue.
[40000:1206/093724.862067:ERROR:cdm_module.cc(138)] CDM at /home/nullrequest/.config/Skye/WidevineCdm/4.10.2391.0/_platform_specific/linux_x64/libwidevinecdm.so could not be loaded.
[40000:1206/093724.862293:ERROR:cdm_module.cc(139)] Error: /home/nullrequest/.config/Skye/WidevineCdm/4.10.2391.0/_platform_specific/linux_x64/libwidevinecdm.so: cannot open shared object file: Operation not permitted
Issue Analytics
- State:
- Created 2 years ago
- Comments:7
Top Results From Across the Web
How to fix a "Command not found" error in Linux - Red Hat
5 ways to fix "Command not found" errors · 1. Include the path · 2. Add a new path · 3. Copy a...
Read more >The command could not be located - Unix Stack Exchange
There are two ways to fix this: Put /bin and /usr/bin back into your path so that commands in your shell init files...
Read more >You intended to execute a .NET application: - Ask Ubuntu
22.04 - The command could not be loaded, possibly because: * You intended to execute a . NET application: - Ask Ubuntu.
Read more >Linux / UNIX: Command Not Found Error and Solution - nixCraft
It means either program is not installed or PATH variable in your environment is not pointing to it. Learn how to fix command...
Read more >How to Fix the "make: command not found" Error in Ubuntu
Want to build a package but stuck with the "make: command not found" error in Ubuntu? Here's how you can get rid of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
it looks like the issue resolved its self after I removed the downloaded components and restarted
I just confirmed that it does work on my box with
v16.0.4+wvcus.1
, again (whereasv16.0.4+wvcus
showed the same issue you are seeing). Are you sure your electron was updated correctly? Please make sure that is the case:If the issues still persists there is probably something else at play as well. Do you maybe have your home folder mounted as non-executable?