Re: [arch-general] Firefox-71.0-1 breaks WhatsApp Web
On 12/9/19 11:01 AM, David Rosenstrauch wrote: > > > On 12/9/19 6:48 AM, Giancarlo Razzolini via arch-general wrote: >> You should not upgrade the firefox package while it's open. That's a >> lesson I've >> learned when I've also lost a profile. Everytime you see firefox in >> the upgrade >> packages list, I suggest you close it and then upgrade. > > IMHO, you really shouldn't upgrade any package while it's running. I > always use "pacman -Syuw" to download all needed updates, then drop into > single user mode to actually install everything with "pacman -Su". Seems > like that would be a best practice to me. You can use `checkupdates -d` to download packages using a temporary database, thus avoiding: https://wiki.archlinux.org/index.php/System_maintenance#Avoid_certain_pacman_commands Which may lead to accidental cases of: https://wiki.archlinux.org/index.php/System_maintenance#Partial_upgrades_are_unsupported -- Eli Schwartz Bug Wrangler and Trusted User signature.asc Description: OpenPGP digital signature
Re: [arch-general] Firefox-71.0-1 breaks WhatsApp Web
On 12/9/19 6:48 AM, Giancarlo Razzolini via arch-general wrote: You should not upgrade the firefox package while it's open. That's a lesson I've learned when I've also lost a profile. Everytime you see firefox in the upgrade packages list, I suggest you close it and then upgrade. IMHO, you really shouldn't upgrade any package while it's running. I always use "pacman -Syuw" to download all needed updates, then drop into single user mode to actually install everything with "pacman -Su". Seems like that would be a best practice to me. DR
Re: [arch-general] Firefox-71.0-1 breaks WhatsApp Web
Em dezembro 9, 2019 0:55 Oon-Ee Ng via arch-general escreveu: After more investigation and travelling back and forth, it appears the issue had at least 2 roots. One is that the update process somehow broke my existing profile. A new profile solves that. The second is that the latest version of firefox seems to not be able to authenticate with an NTLM proxy specifically for web.whatsapp.com. This has happened before - https://bugzilla.mozilla.org/show_bug.cgi?id=1536787 shows almost identical behaviour to what I am experiencing. However I was not using Firefox at that time. Perhaps I'll just switch back to Chromium for whatsapp web. You should not upgrade the firefox package while it's open. That's a lesson I've learned when I've also lost a profile. Everytime you see firefox in the upgrade packages list, I suggest you close it and then upgrade. Regards, Giancarlo Razzolini pgp2YAajqZs8t.pgp Description: PGP signature
Re: [arch-general] Firefox-71.0-1 breaks WhatsApp Web
After more investigation and travelling back and forth, it appears the issue had at least 2 roots. One is that the update process somehow broke my existing profile. A new profile solves that. The second is that the latest version of firefox seems to not be able to authenticate with an NTLM proxy specifically for web.whatsapp.com. This has happened before - https://bugzilla.mozilla.org/show_bug.cgi?id=1536787 shows almost identical behaviour to what I am experiencing. However I was not using Firefox at that time. Perhaps I'll just switch back to Chromium for whatsapp web.
Re: [arch-general] Firefox-71.0-1 breaks WhatsApp Web
On Wed, Dec 4, 2019 at 9:11 PM Giancarlo Razzolini wrote: > Em dezembro 4, 2019 1:28 Oon-Ee Ng via arch-general escreveu: > > 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. > > > > It is working here. I have deauthenticated and authenticated again using > the > qrcode. > > Try using a clean profile. > > Regards, > Giancarlo Razzolini Oddly enough, yesterday I tried a clean profile and had the same issue. Today a clean profile works (my main profile doesn't). However I'm on a different (less restrictive) network today so that may explain it.
Re: [arch-general] Firefox-71.0-1 breaks WhatsApp Web
Em dezembro 4, 2019 1:28 Oon-Ee Ng via arch-general escreveu: 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. It is working here. I have deauthenticated and authenticated again using the qrcode. Try using a clean profile. Regards, Giancarlo Razzolini pgpASJ5ujefVw.pgp Description: PGP signature
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. > >
