Netflix, Amazon Prime Video, and Chromium.

[stozi]

Now I get this

Code:

$ sudo chromium-armhf
[sudo] password for xxx:
Enabling XHost Forwarding
non-network local connections being added to access control list
Searching for Docker image ...
Found and using d8a602e8d767
/usr/bin/chromium-browser: line 133: lsb_release: command not found
/usr/bin/chromium-browser: line 134: lsb_release: command not found
[1:1:0812/132917.203417:ERROR:process_singleton_posix.cc(294)] The profile appears to be in use by another Chromium process (1) on another computer (dcaa9e9df785). Chromium has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chromium.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
[1:23:0812/132925.392315:FATAL:gpu_data_manager_impl_private.cc(986)] The display compositor is frequently crashing. Goodbye.

lsb_release is installed. usually to solve the singleton error you'd delete .config/chromium/singletonLOCK, but that does nothing, and 'find' doesn't find another singleton file anywhere else on the system. This is the first time I've used docker, I guess these problems are within the Docker image and I need some analogy of chroot to edit it?

[spikerguy]

Thank you everyone. I am working on installing Chromium.  As you guys know i am a complete novice concerning Linux code. When I get Chromium installed or running off an SD card I will post my success. I really appreciate all the help.

Yes its ok we all learn slowly by practicing.

First you need to share what Operating system are you using?

If you're using Manjaro ARM Linux then I can help you as I am the maintainer of `chromium-docker` package.

Try this:
This will remove the existing chromium-docker package

Code:

sudo pacman -Rnsc chromium-docker

Then install again using

Code:

sudo pacman -S chromium-docker

then just reboot and try to open it from the start menu.

Regarding the profile issue you can just restart your pc and the profile issue should be resolved but I prefer starting fresh just to clear anything that have messed up the profile in your first try.

[vb_linux]

If you're using Manjaro ARM Linux then I can help you as I am the maintainer of `chromium-docker` package.

Does the Chromium ever updates in Chromium docker? How to update it to latest version?

[spikerguy]

If you're using Manjaro ARM Linux then I can help you as I am the maintainer of `chromium-docker` package.

Does the Chromium ever updates in Chromium docker? How to update it to latest version?

It does but It cannot be as updated as the regular Chromium.

Technical Reason: We need to find compatible lib-widevine to work with the Chromium version which is dependant on the CHROME-OS Image if they  upgrade lib-widevine then we can upgrade the chromium.

I try to update it but it takes quite some time to find the right matching Chromium version for the widevine we fetch from CHROME-OS recovery Image.

Good question but that is the reason it is recommeded to use chromium-dockers for only DRM content and not for normal browsing.