Re: [arch-general] Firefox-71.0-1 breaks WhatsApp Web
It's not on by default. Enabling/disabling doesn't help. Another website (discordapp.com) also has certain pages not working with this update. On Wed, Dec 4, 2019 at 2:23 PM Genes Lists via arch-general < arch-general@archlinux.org> wrote: > > I wonder if turning off DOH helps. i.e. in firefox: > > Settings -> network settings > > Then unselect DNS over https. >
Re: [arch-general] Firefox-71.0-1 breaks WhatsApp Web
On Wed, Dec 4, 2019 at 12:32 PM Oon-Ee Ng wrote: > On Wed, Dec 4, 2019 at 12:28 PM Oon-Ee Ng wrote: > >> After the update I can't seem to load WhatsApp Web. >> >> If I already logged in (using the QR code) it just doesn't load and >> eventually displays the 'connecting to WhatsApp' message which typically >> happens when the phone is offline. >> >> If I haven't logged in it will try to load the QR code for authentication >> and wait for that forever. The console shows the following:- >> >> Content Security Policy: Directive ‘child-src’ has been deprecated. >> Please use directive ‘worker-src’ to control workers, or directive >> ‘frame-src’ to control frames respectively. >> Firefox can’t establish a connection to the server at wss:// >> web.whatsapp.com/ws. app.fff9477f997fa1246faf.js:2:783554 >> >> Chromium on the same machine has no such issues. >> > > This link https://bugzilla.mozilla.org/show_bug.cgi?id=1468870 mentions > possible DNS issues. I'll have to retry on a different connection when I > get there. > Just to note (since I forgot to mention it in my original message), it seems to work on the same machine when downgrading only firefox (to 70.0.1-3)
Re: [arch-general] Firefox-71.0-1 breaks WhatsApp Web
On Wed, Dec 4, 2019 at 12:28 PM Oon-Ee Ng wrote: > After the update I can't seem to load WhatsApp Web. > > If I already logged in (using the QR code) it just doesn't load and > eventually displays the 'connecting to WhatsApp' message which typically > happens when the phone is offline. > > If I haven't logged in it will try to load the QR code for authentication > and wait for that forever. The console shows the following:- > > Content Security Policy: Directive ‘child-src’ has been deprecated. Please > use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to > control frames respectively. > Firefox can’t establish a connection to the server at wss:// > web.whatsapp.com/ws. app.fff9477f997fa1246faf.js:2:783554 > > Chromium on the same machine has no such issues. > This link https://bugzilla.mozilla.org/show_bug.cgi?id=1468870 mentions possible DNS issues. I'll have to retry on a different connection when I get there. > >
Re: [arch-general] Virtualbox Models for 5.2.34 (supported) Fail to Build against Linux 5.4
On 12/02/2019 10:49 PM, David C. Rankin wrote: > On 12/02/2019 07:36 PM, David C. Rankin wrote: >> All, >> >> Heads up to anyone still running Virtualbox 5.2.34 due to issues with >> headless clients in Virtualbox 6.x, the kernel modules for 5.2.34 will not >> build against Linux-5.4. >> >> Build failure details at: >> >> https://sourceforge.net/p/vbox-users/mailman/vbox-users-community/?viewmonth=201912 >> > > Oracle testcase build does work fine with Linux-5.4 > > https://www.virtualbox.org/download/testcase/VirtualBox-5.2.35-135095-Linux_amd64.run > https://www.virtualbox.org/download/testcase/VirtualBoxSDK-5.2.35-135095.zip > https://www.virtualbox.org/download/testcase/Oracle_VM_VirtualBox_Extension_Pack-5.2.35-135095.vbox-extpack > Already fixed, just waiting on upcoming 5.2.36 release: Ticket #18945 (closed defect: fixed) Linux 5.4: no more arbitrary executable pages and more changes https://www.virtualbox.org/ticket/18945 -- David C. Rankin, J.D.,P.E.
Re: [arch-general] 11/23 update caused httpd to coredump?
On 12/03/2019 11:28 AM, Genes Lists via arch-general wrote: > On 12/3/19 5:36 AM, Andy Pieters wrote: > >> I have experienced this last year and when I recompiled both apache >> and wsgi with debugging symbols to find out what's what, it suddenly >> worked again and has since! >> > That sounds like use of variable before set - as debugging initializes > variables to 0 (in C, C++ ... ). > > Could be buggy code. Nope, now wsgi... Funny thing is for 10 years I though all updates I have never had any problems with httpd. The whatever changed in the 11/23 updates it was segfaulting/coredumping repeatedly. I thought the follow-up updates solved it, but then found both servers websites down again. Restarting httpd brings the server back up, but it was shocking to look at the logs and see on one server: -rw-r--r-- 1 root root 71509927 Dec 2 19:22 error_log -rw-r--r-- 1 root root 24306916 Dec 1 00:00 error_log.1 -rw-r--r-- 1 root root 625 Nov 24 00:00 error_log.2 -rw-r--r-- 1 root root 1742 Nov 21 13:19 error_log.3 -rw-r--r-- 1 root root 504 Nov 10 00:00 error_log.4 and then on the other: -rw-r--r-- 1 root root 73141520 Dec 2 19:15 error_log -rw-r--r-- 1 root root 25049886 Dec 1 00:00 error_log.1 -rw-r--r-- 1 root root 1137 Nov 24 00:00 error_log.2 -rw-r--r-- 1 root root 1752 Nov 17 00:01 error_log.3 -rw-r--r-- 1 root root 504 Nov 10 00:00 error_log.4 Yikes! -- David C. Rankin, J.D.,P.E.
Re: [arch-general] 11/23 update caused httpd to coredump?
On 12/3/19 5:36 AM, Andy Pieters wrote: > > I have experienced this last year and when I recompiled both apache > and wsgi with debugging symbols to find out what's what, it suddenly > worked again and has since! > That sounds like use of variable before set - as debugging initializes variables to 0 (in C, C++ ... ). Could be buggy code.
Re: [arch-general] Failed to compile python 2.7.9 with pyenv on arch.
Eli Schwartz via arch-general 于2019年12月2日周一 下午2:38写道： > > On 12/2/19 1:00 AM, Hongyi Zhao via arch-general wrote: > > Hi, > > > > I try to compile python 2.7.9 with pyenv on arch linx with the > > following command: > > > > === > > $ pyenv install 2.7.9 > > Installing Python-2.7.9... > > patching file ./Lib/site.py > > patching file ./Lib/ssl.py > > ERROR: The Python ssl extension was not compiled. Missing the OpenSSL lib? > > > > Please consult to the Wiki page to fix the problem. > > https://github.com/pyenv/pyenv/wiki/Common-build-problems > > Well, the error message is pretty clear that the problem is "the OpenSSL > lib", so if you look on that wiki page for information about the OpenSSL > lib, you'll hit the following subcomponent of that page: > > https://github.com/pyenv/pyenv/wiki/Common-build-problems#error-the-python-ssl-extension-was-not-compiled-missing-the-openssl-lib Thanks a lot, based on this notes, I solved the problem. Regards > > It specifically calls out archlinux with an indication that this ancient > version of python requires an openssl version less than 1.1 (and > mentioning the name of the CFLAGS and LDFLAGS you'll need to > successfully compile ancient python in such cases). > > This matches the official python2 documentation: > https://docs.python.org/2.7/library/ssl.html > > "Changed in version 2.7.13: Updated to support linking with OpenSSL 1.1.0" > > > BUILD FAILED (Arch Linux using python-build 1.2.15-2-g22c0202) > > > > Inspect or clean up the working tree at > > /tmp/python-build.20191202134159.88051 > > Results logged to /tmp/python-build.20191202134159.88051.log > > > > Last 10 log lines: > > rm -f /home/werner/.pyenv/versions/2.7.9/share/man/man1/python.1 > > (cd /home/werner/.pyenv/versions/2.7.9/share/man/man1; ln -s python2.1 > > python.1) > > if test "xno" != "xno" ; then \ > > case no in \ > > upgrade) ensurepip="--upgrade" ;; \ > > install|*) ensurepip="" ;; \ > > esac; \ > > ./python -E -m ensurepip \ > > $ensurepip --root=/ ; \ > > fi > > == > > These log lines are useless, your problem has nothing to do with running > ensurepip. > > > -- > Eli Schwartz > Bug Wrangler and Trusted User > -- Hongsheng Zhao Institute of Semiconductors, Chinese Academy of Sciences GnuPG DSA: 0xD108493
