Change:
--target ${target}  -Dhost_arch=${host}  -Duse_system_zlib=1  <ins> --enable-libpkix  </ins> ${stdenv.lib.optionalString stdenv.isDarwin "--clang"}  ${stdenv.lib.optionalString (stdenv.hostPlatform != stdenv.buildPlatform) "--disable-tests"}

Discussion:
Describe the bug Recently I noticed that the Electron applications I commonly used ceased to be able to connect to the internet. Spotify, Discord, Slack cannot connect anymore. To Reproduce Steps to reproduce the behavior: latest nixpkgs channel Slack, Spotify or Discord cannot connect to their respective servers Expected behavior They should be able to connect to the internet. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Got a similar issue, but Discord and Spotify works. For me it's slack-specific. EDIT: Nevermind looks like I am getting only slack from unstable channel :facepalm:
I don’t think it is Electron specific. I see the same issue with qutebrowser
I confirm I can reproduce it with . Might be WebKit related ?
I have issues with qutebrowser aswell, with every https:// site, http:// works. Getting errors like this: But my qutebrowser uses QtWebEngine, not WebKit afaik. I've rolled back so can't double check.
I've been able to track back the issue to the commit Before this commit it works perfectly. EDIT: It seems that there is an update related to in this commit (see ) I believe that could be related to this specific change.
Interestingly, it seems that not all Electron apps are affected. Signal still works, for instance, but Discord and Slack don't.
This also affects Bitwarden and potentially Steam. Temporarily using nss344 for the nss package in Bitwarden & Discord works.
Steam indeed doesn't work.
cc
For reference, so this (hopefully) shows up in search results: ERR_FAILED is the error code qutebrowser shows.
I'm using the canary release and it's working, unfortunately it demands an update from 0.0.104 to 0.0.105
Slack also seems to work with , but not
I see that and had some similar issues with other programs while handling , they fixed it by simply use a previous version of for those programs. Maybe we should do the same ? I'm not completely sure this is the right solution since the list of broken programs seems to be quite long.
Rambox (electron) also seems to be affected
Probably switch the default to the older version? At least that's what this sounds like at a quick look.

(i.e. only use the new one for the new Firefox and Thunderbird branches)
Thanks I'm not sure how to achieve this, I will check it out later but if somebody with the knowledge can help that would be really cool :).
So much for "NSS 3.54 shared libraries are backward compatible with all older NSS 3.x shared libraries. A program linked with older NSS 3.x shared libraries will work with NSS 3.54 shared libraries without recompiling or relinking. Furthermore, applications that restrict their use of NSS APIs to the functions listed in NSS Public Functions will remain compatible with future versions of the NSS shared libraries." I guess maybe all of this stuff isn't "restricting their use of NSS APIs to the functions listed in NSS Public Functions". We can switch the default to 3.44.x, but I'm not sure if that will be supported after Firefox ESR 68 is EOL, which will be in a month iirc.
A temp workaround for now is to chuck something like the following in an overlay to build the derivation with the older 3.44 NSS (using discord as an example here):
An alternative workaround that I'm currently using is to replace with in .
Arch has discord (and everything else) using and I'm assuming it works
We use , but I believe this is unrelated ?
is 3.55, if you want to give that a go. Probably doesn't help much, though.
Im aware we're on just wondering if it's an issue affecting other releases on other distros, or a exclusive thing They also appear to have been using for a month too:
Maybe we broke something in the makefile -gyp based build system transition. Apparently that all came down to the default make target being wrong, so what you could do is revert that whole change, append to the makeFlags, update to a newer release, rebuild everything and see if that fixes anything.
Steam, Discord and Bitwarden stopped working for me.
Slack stopped working for me as well. I don't use Steam, Discord, or Bitwarden (the Linux app-- I use it in the browser only). However, using fixed it, as per Thanks!
So for now?
Not sure if related but dropbox doesn't currently work for me.
This might be related, but vscode doesn't connect to the network either.

I tried overriding it with nss 3.44 but apparently it doesn't depend on it:
VSCode is pulling nss from atomEnv which is it at On Wed, Jul 29, 2020 at 22:58, Matthew Levan <:
Great. So how would I go about succinctly overriding 's within the expression?
Maybe an overlay for atomEnv. I'm not good with the nix language so I don't have any specifics.
How is everyone using ? It does not exist for me and it clearly does not exist in the stable repo.
No results found.
!
Doesn't show up on stable qutebrowser. ! Works on firefox but can't test unstable qutebrowser because it can't access the internet.
Works here on stable qutebrowser !
Anyways to get back on topic here... How do overlays work and is this the appropriate quick fix for someone like me waiting for a PR to be merged into unstable? theGeekPirate <:
I can't replicate it with so I have no idea what's going on.
The simplest solution is to use the stable version of whichever application(s) is/are causing you trouble until is merged.
Great, thank you. theGeekPirate <:
For someone that has many unstable packages that are broken, is an overlay the way to fix the issue for every conceivable package that depends on the troublesome package without having anonymous functions filled with overrides everywhere?
My Nix-fu isn't great, but I'm assuming there's a way to override nss to use that unstable package globally, instead. Hopefully someone else more knowledgeable can step in and help you.
In case anyone is wondering how to use a package from another channel, .
Thank you for the merge. I've renamed the issue so people that are searching with "my [app] is not connecting anymore" won't get confused by this quite specific nss issue.
Thank you all for finding the source of the problem fast.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Both channels have updated already to contain the fix.