search

mrclksr / linux-browser-installer

Script to install Linux browsers under a Linux chroot on FreeBSD
165 stars 25 forks source link

Chrome browser: Netflix error code M7361-1253 #42

Closed q-pa closed 10 months ago

q-pa commented 11 months ago

Since 2023-08-24 or -25 I no longer can play content from Netflix (in Germany). The Chrome browser is kept up to date. I also tested lots of different user agents (with user agent switcher).

OS: GhostBSD

ryanavella commented 11 months ago

I'm also seeing the same with Amazon Prime, and it started happening roughly around the same time. (although I did recently upgrade to 13.2)

I don't think it is Chrome-specific, I see the same with Brave and Edge.

$ uname -mrsv
FreeBSD 13.2-RELEASE-p2 FreeBSD 13.2-RELEASE-p2 GENERIC amd64

For what it is worth, here is stdout/stderr from linux-chrome after I try to play a video:

Click to expand ```text [0907/191309.335003:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1) [0907/191309.335059:ERROR:proc_task_reader.cc(46)] format error [28135:105731:0907/191309.507003:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.507102:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.507179:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.507261:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.507362:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.507440:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.507531:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.507603:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.507692:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.507777:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.507858:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.507928:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.508003:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.508085:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.510955:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.511042:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [28135:105731:0907/191309.511122:ERROR:bus.cc(399)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ```
q-pa commented 11 months ago

$ uname -mrsv FreeBSD 13.2-STABLE FreeBSD 13.2-STABLE GENERIC amd64

This is the output of dmesg from /compat/ubuntu:

... / 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18275 (ThreadPoolForeg): unsupported TCP socket option TCP_INFO (11) [ 0.000000] linux: jid 0 pid 18409 (dmesg): syslog unsupported type 0xa

q-pa commented 10 months ago

I am on GhostBSD and updated my system to GhostBSD 23.10.1 amd64 today

$ uname -mrsv
FreeBSD 13.2-STABLE FreeBSD 13.2-STABLE GENERIC amd64

At least Netflix is working again, cannot test other DRM-related stuff at the moment.