Hello, I already opened an issue with the Nyxt project and they think the problem is related to a conflict between guix and fedora. The issue in the Nyxt project is: https://github.com/atlas-engineer/nyxt/issues/1132 As the initial post and discussion is already rather long it seems better, to me to reference the issue instead of posting my description again. Regards, Roland Everaert --- Use the F.O.S.S., Luke Sent with [ProtonMail](https://protonmail.com/) Secure Email.
Hi, On Mon, 22 Feb 2021 at 20:14, Roland Everaert via <help-guix@gnu.org> wrote: > I already opened an issue with the Nyxt project and they think the problem is related to a conflict between guix and fedora. > > The issue in the Nyxt project is: > https://github.com/atlas-engineer/nyxt/issues/1132 Could you try: --8<---------------cut here---------------start------------->8--- guix environment --preserve='^DISPLAY$' --container --network \ --expose=/etc/machine-id \ --expose=/etc/ssl/certs/ \ --share=$HOME/.local/share/nyxt/=$HOME/.local/share/nyxt/ \ --ad-hoc nyxt nss-certs dbus -- nyxt --8<---------------cut here---------------end--------------->8--- ? From <https://guix.gnu.org/manual/devel/en/guix.html#Invoking-guix-environment>. The ’--container’ part removes any potential conflicts between Guix and Fedora. Then, --8<---------------cut here---------------start------------->8--- guix environment --pure \ --ad-hoc nyxt nss-certs dbus -- nyxt --8<---------------cut here---------------end--------------->8--- ? Thanks, simon
Roland Everaert
---
Use the F.O.S.S., Luke
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Le mercredi 24 février 2021 à 10:28, zimoun <zimon.toutoune@gmail.com> a écrit :
> Hi,
>
> On Mon, 22 Feb 2021 at 20:14, Roland Everaert via help-guix@gnu.org wrote:
>
> > I already opened an issue with the Nyxt project and they think the problem is related to a conflict between guix and fedora.
> >
> > The issue in the Nyxt project is:
> >
> > https://github.com/atlas-engineer/nyxt/issues/1132
>
> Could you try:
>
> --8<---------------cut here---------------start------------->8---
>
> guix environment --preserve='^DISPLAY$' --container --network \
>
> --expose=/etc/machine-id \
>
> --expose=/etc/ssl/certs/ \
>
> --share=$HOME/.local/share/nyxt/=$HOME/.local/share/nyxt/ \
>
> --ad-hoc nyxt nss-certs dbus -- nyxt
>
> --8<---------------cut here---------------end--------------->8---
>
> ? From https://guix.gnu.org/manual/devel/en/guix.html#Invoking-guix-environment.
>
> The ’--container’ part removes any potential conflicts between Guix and
>
> Fedora.
>
> Then,
>
> --8<---------------cut here---------------start------------->8---
>
> guix environment --pure \
>
> --ad-hoc nyxt nss-certs dbus -- nyxt
>
> --8<---------------cut here---------------end--------------->8---
>
> ?
>
> Thanks,
>
> simon
Hello,
Unfortunately, I still face the same problem. The only notable difference, is the fact that nyxt don't trust the certificate from duckduckgo. But, once I add it with the function add-domain-to-certificate-exceptions, the problem with webkitgtk arise.
Hi, > > --8<---------------cut here---------------start------------->8--- > > guix environment --preserve='^DISPLAY$' --container --network \ > > --expose=/etc/machine-id \ > > --expose=/etc/ssl/certs/ \ > > --share=$HOME/.local/share/nyxt/=$HOME/.local/share/nyxt/ \ > > --ad-hoc nyxt nss-certs dbus -- nyxt > > --8<---------------cut here---------------end--------------->8--- > > The ’--container’ part removes any potential conflicts between Guix and > > Fedora. > > --8<---------------cut here---------------start------------->8--- > > guix environment --pure \ > > --ad-hoc nyxt nss-certs dbus -- nyxt > > --8<---------------cut here---------------end--------------->8--- > Unfortunately, I still face the same problem. The only notable difference, is the fact that nyxt don't trust the certificate from duckduckgo. But, once I add it with the function add-domain-to-certificate-exceptions, the problem with webkitgtk arise. Do you mean using the command with '--container'? Maybe 1. you have a problem of config on your side with the certificates; from where do they come from? What does ot happens for other website than duckduckgo? Then 2. the 'add-domain-to-certicate-exceptions' looks like a bug on the Nyxt side. Hope that helps, simon
[-- Attachment #1: Type: text/plain, Size: 899 bytes --] zimoun <zimon.toutoune@gmail.com> writes: >> Unfortunately, I still face the same problem. The only notable difference, is the fact that nyxt don't trust the certificate from duckduckgo. But, once I add it with the function add-domain-to-certificate-exceptions, the problem with webkitgtk arise. > > Do you mean using the command with '--container'? > > Maybe 1. you have a problem of config on your side with the > certificates; from where do they come from? What does ot happens for > other website than duckduckgo? Then 2. the > 'add-domain-to-certicate-exceptions' looks like a bug on the Nyxt > side. add-domain-to-certificate-exceptions is the Nyxt equivalent of Firefox "Add exception" or something like that: it ignores bad certificates for the HTTPS connection to a given host. This is the expected behaviour I believe. -- Pierre Neidhardt https://ambrevar.xyz/ [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 511 bytes --]