(08-09-2020, 02:48 PM)TheBackburner Wrote:

(07-30-2020, 12:03 PM)spikerguy Wrote: Hello,

Can you provide some logs so someone can look into it and know what might be causing the issue.

Please share the output of the logs when it is trying to install the package.

Sorry for the inconvenience caused.

@spikerguy , is what you need the output when trying to run chromium-docker? If so, see below:

Code:

Enabling XHost Forwarding
non-network local connections being added to access control list
Searching for Docker image ...
Found and using d7150613eb67
/usr/bin/chromium-browser: line 133: lsb_release: command not found
/usr/bin/chromium-browser: line 134: lsb_release: command not found
[1:1:0809/202837.988206:ERROR:process_singleton_posix.cc(294)] The profile appears to be in use by another Chromium process (1) on another computer (1851c23db1a3). 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:21:0809/202845.472653:FATAL:gpu_data_manager_impl_private.cc(986)] The display compositor is frequently crashing. Goodbye.

If there's something else needed, could you help me out with what commands or program I would need to run to get the output you're looking for? I'm a bit of a Linux noob, so I'm not even sure what providing logs entails, and I didn't have much success Googling the topic. I'd love to get this program running again, so I'd be happy to provide any output you might need. Please let me know what I can do to help. Thanks!

(08-14-2020, 06:28 AM)spikerguy Wrote: Can anyone do the following and report if netflix and amazon works or not as my accounts have expired so I cannot test it. I tested youtube over chromiun-docker updated app and it works fine again.

(09-06-2020, 11:42 PM)appelgriebsch Wrote: [quote pid='76759' dateline='1599414565']
I ran into another issue. I can't start the application from the applications menu. A terminal window opens and quickly closes. I tried to open the application from the terminal and received a 'permission denied'.

Code:

$ chromium-armhf
Set host IP for Pulseaudio
Enabling XHost Forwarding
non-network local connections being added to access control list
Searching for Docker image ...
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.40/images/json?filters=%7B%22reference%22%3A%7B%22hthiemann%2Fchromium-armhf%3Alatest%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied
Found and using
"docker run" requires at least 1 argument.
See 'docker run --help'.

Usage:  docker run [OPTIONS] IMAGE [COMMAND] [ARG...]

Run a command in a new container

The application can be run with sudo. Afaik, that is something to be avoided. Do you know any possible causes for that? Do you need any further information on the issue?

Thank you for your work. The effort of the Manjaro team in the development for the PBP is really amazing!

Regards

Diadochokinetic

(09-06-2020, 11:42 PM)appelgriebsch Wrote: As docker is run as daemon in the background you need to be part of a specific ‘docker’ group to be able to use it from a normal user account.
To enable your current logged on user you will have to:
1. go to a terminal
2. run sudo usermod -aG docker <username>
3. log off and on again to activate the changes
4. you can check your group membership with the groups command in a terminal. It should list the docker group.

(09-09-2020, 08:44 AM)3xC0MM Wrote:

(09-06-2020, 11:42 PM)appelgriebsch Wrote: [quote pid='76759' dateline='1599414565']
I ran into another issue. I can't start the application from the applications menu. A terminal window opens and quickly closes. I tried to open the application from the terminal and received a 'permission denied'.

Code:

$ chromium-armhf
Set host IP for Pulseaudio
Enabling XHost Forwarding
non-network local connections being added to access control list
Searching for Docker image ...
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.40/images/json?filters=%7B%22reference%22%3A%7B%22hthiemann%2Fchromium-armhf%3Alatest%22%3Atrue%7D%7D": dial unix /var/run/docker.sock: connect: permission denied
Found and using
"docker run" requires at least 1 argument.
See 'docker run --help'.

Usage:  docker run [OPTIONS] IMAGE [COMMAND] [ARG...]

Run a command in a new container

The application can be run with sudo. Afaik, that is something to be avoided. Do you know any possible causes for that? Do you need any further information on the issue?

Thank you for your work. The effort of the Manjaro team in the development for the PBP is really amazing!

Regards

Diadochokinetic

As docker is run as daemon in the background you need to be part of a specific ‘docker’ group to be able to use it from a normal user account.
To enable your current logged on user you will have to:
1. go to a terminal
2. run sudo usermod -aG docker <username>
3. log off and on again to activate the changes
4. you can check your group membership with the groups command in a terminal. It should list the docker group.

Quote:Please do

Code:

sudo pacman -Rnsc chromium-docker

sudo pacman -S chromium-docker

First command will remove all the old chromium-docker content while second one will install it fresh.

Hope this will solve your issue.

Quote:UPDATE:
Added pulseaudio handling over network so paprefs becomes a dependency which will be installed but user will have to enable it
Open paprefs - sound server preference
and just enable as per the below pic.

(09-10-2020, 03:36 AM)3xC0MM Wrote:

Quote:Please do

Code:

sudo pacman -Rnsc chromium-docker

sudo pacman -S chromium-docker

First command will remove all the old chromium-docker content while second one will install it fresh.

Hope this will solve your issue.

Thank you, that was it!

Quote:UPDATE:
Added pulseaudio handling over network so paprefs becomes a dependency which will be installed but user will have to enable it
Open paprefs - sound server preference
and just enable as per the below pic.

You mention this in the post above, but the picture does not show. Can you please repost it?
BR

(09-26-2020, 12:05 PM)wrzomar Wrote:

(09-10-2020, 03:36 AM)3xC0MM Wrote:

Quote:Please do

Code:

sudo pacman -Rnsc chromium-docker

sudo pacman -S chromium-docker

First command will remove all the old chromium-docker content while second one will install it fresh.

Hope this will solve your issue.

Thank you, that was it!

Quote:UPDATE:
Added pulseaudio handling over network so paprefs becomes a dependency which will be installed but user will have to enable it
Open paprefs - sound server preference
and just enable as per the below pic.

You mention this in the post above, but the picture does not show. Can you please repost it?
BR

Also, if someone has enabled the firewall, they will have to allow TCP connections to port 4713 from docker subnet. For ufw it would be:

Code:

sudo ufw allow proto tcp to any port 4713 from `docker network inspect bridge --format='{{(index .IPAM.Config 0).Subnet}}'`

PS. I've changed the addrip variable in the chromium-armhf script to the docker gateway address. As long as docker0 interface is up, audio should work. Now the line looks like this:

Code:

addrip="$(docker network inspect bridge --format='{{(index .IPAM.Config 0).Gateway}}')"

PPS. To decode this image you need to copy everything between '[img]data:image/png;base64,' and '[/img]', paste it to text editor and save it, then use base64 command to decode.

Code:

base64 -d base64_encoded_png.txt > image.png

It shows PulseAudio Preferences window with Network Server tab opened, 'Enable network access to local sound devices' and 'Don't require authentication' options are checked.
PPPS. I've installed Manjaro on emmc a few days ago, Spikerguy's post about updating to Chromium 84 is month old but I've just checked Chromium version and it says it's 78 but the base is bionic. Do I have to switch branch to testing or unstable to get this update?
Here is proof:
Chromium-docker package details
About Chromium page
@spikerguy, Where is this updated Chromium? The installed version keeps complaining about upgrading to a newer version.

I've tried updating the chromium but it widevine doesn't support newer version of chromium, we're dependent on ChromeOS to update their widevine to support latest version of chromium. 

I can try it in the coming week to see if I can get a newer version of chromium to work with the ChromeOS widevine but I will need someone to share a Netflix or amazon account for testing as I've stopped mine and can no longer get a few trial too