You are not logged in.
I'm still getting the failure on chromium, too. I could live with it if it was just FF until FF was updated, but on both, upgrading glibc is a non-starter for the moment.
I have no TV, and rely on those two streaming services for entertainment.
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
Offline
You could bisect glibc between 2.30 and 2.31 to find the causal commit or report the bug without the bisection.
Online
or in firefox about:config security.sandbox.content.syscall_whitelist set the string to __NR_clock_gettime64
For that about:config value you need syscall numbers, not text.
security.sandbox.content.syscall_whitelist
Comma-seperated list of additional system call numbers that should be allowed in the content process. These affect the seccomp-bpf filter.
Edit: You can get the numbers from e.g. /usr/include/asm/unistd_64.h, which is packaged in linux-api-headers
Last edited by progandy (2020-02-08 18:52:19)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
You could try chromium --no-sandbox to see if it is one of the sandboxing features failing with the new glibc.
or in firefox about:config security.sandbox.content.syscall_whitelist set the string to __NR_clock_gettime64
Edit:
@Roken I think that dlopen signal trapping was fixed by https://github.com/bminor/glibc/commit/ … 4d9c12784cMOZ_DISABLE_CONTENT_SANDBOX=1 looks like another option to test with firefox.
MOZ_SANDBOX_LOGGING=1 to produce relevant logging if it is the sandbox.
The dlopen signal trapping fix landed in the glibc release tag, so it seems unrelated.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
I downgrade the glibc package to glibc-2.30-3 and now Netflix is working again, thx guys.
sudo pacman -U /var/cache/pacman/pkg/glibc-2.30-3-x86_64.pkg.tar.xz /var/cache/pacman/pkg/lib32-glibc-2.30-3-x86_64.pkg.tar.xz
Offline
A temporary workaround for now.
export MOZ_DISABLE_CONTENT_SANDBOX=1
export MOZ_DISABLE_GMP_SANDBOX=1
Offline
A temporary workaround for now.
export MOZ_DISABLE_CONTENT_SANDBOX=1
export MOZ_DISABLE_GMP_SANDBOX=1
Bug & Fix: https://bugzilla.mozilla.org/show_bug.cgi?id=1614535
Seems like the fix should be available in firefox-developer-edition as of 74.0b3
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
craig_mc wrote:A temporary workaround for now.
export MOZ_DISABLE_CONTENT_SANDBOX=1
export MOZ_DISABLE_GMP_SANDBOX=1Bug & Fix: https://bugzilla.mozilla.org/show_bug.cgi?id=1614535
Seems like the fix should be available in firefox-developer-edition as of 74.0b3
Thank you. That does fix in FF.
It doesn't help Chromium, of course, but that's not an issue for me. I've finally been able to remove the pin on glibc.
EDIT: For info - the dev edition does appear to have fixed it.
Last edited by Roken (2020-02-14 21:19:26)
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
Offline
I've set these values inside of firefox at about:config and reloaded FF but no change. I also placed both of those exports in my ~/.bash_profile and sourced it (and confirmed those values are set) however after restarting firefox I still have this issue. I am running the latest updates for all packages (nothing downgraded). What am I missing/doing wrong?
Last edited by ipyakuza (2020-02-18 13:23:14)
Offline
I also tested with chromium --no-sandbox and it noted security/unsupported/potential instability (expected) yet still couldnt get Hulu or Netflix to run.
I downgraded my package(s) to glibc 2.30 and restarted firefox and it worked. Guess I have to wait here for a bit until the updated FF/widevine is released.
Last edited by ipyakuza (2020-02-18 13:53:11)
Offline
I've set these values inside of firefox at about:config and reloaded FF but no change. I also placed both of those exports in my ~/.bash_profile and sourced it (and confirmed those values are set) however after restarting firefox I still have this issue. I am running the latest updates for all packages (nothing downgraded). What am I missing/doing wrong?
Instead of exporting those variables in .bash_profile, try running Firefox as
MOZ_DISABLE_GMP_SANDBOX=1 firefox
Also, Firefox has just been flagged out of date, so this workaround should not be necessary for long.
Offline
It supposed to be fixed with FF 73.0.1
Offline
Looks like Chromium and FF packages were updated in the last 24 hours, I've since updated all the packages (include glibc to 2.31) and everything is working again.
Offline
Looks like Chromium and FF packages were updated in the last 24 hours, I've since updated all the packages (include glibc to 2.31) and everything is working again.
I can confirm with FF. I've dumped Chromium.
Back to fully updated with official repos now. Still have a couple of Aur packages causing problems, but completely unrelated.
Last edited by Roken (2020-02-19 20:14:40)
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
Offline