all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: WebKit: Failing to play most HTML5 videos
Date: Fri, 21 Dec 2018 12:58:02 +0100	[thread overview]
Message-ID: <875zvnrt11.fsf@elephly.net> (raw)
In-Reply-To: <87tvj79mjv.fsf@ambrevar.xyz>


Pierre Neidhardt <mail@ambrevar.xyz> writes:

>> Instead we should run getenv to get the location from one
>> of the common environment variables and only fall back to
>> “/etc/ssl/certs/ca-certificates.crt” if it isn’t set.
>
> You mean add getenv in C, right?

Yes.

> Wouldn't there be a way with environment variables though?  From an executable
> wrapper, or maybe in ./etc/profile.

I haven’t looked if that’s possible.  Users of libcurl are supposed to
set the location of the cert bundle or else have to use the default for
*libcurl* provided at configure time.

This plugin does have a knob to override the location, but I don’t know
how to turn it.  It looks like it’s used as a command line argument, but
nobody uses this plugin on the command line.

If you can find a way that doesn’t involve patching in a getenv call I’d
be happier, but if we can’t figure out another way and the alternative
is to have a broken plugin I’d rather go down the getenv route.

What do you think?

>> Another thing: I found that my browser tab freezes when a video rewinds
>> to loop.  I have gst-libav installed (in addition to all the
>> “gst-plugins-*” packages), so that may be responsible here.
>
> I have the same issue.
> Which browser are you using?

I used epiphany for the test.

--
Ricardo

  reply	other threads:[~2018-12-21 12:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-08 12:30 WebKit: Failing to play most HTML5 videos Pierre Neidhardt
2018-12-08 12:39 ` Pierre Neidhardt
2018-12-08 14:31   ` swedebugia
2018-12-08 15:30     ` Pierre Neidhardt
2018-12-09  5:51 ` Leo Famulari
2018-12-09 12:21   ` Pierre Neidhardt
2018-12-11  7:23     ` swedebugia
2018-12-11  8:02     ` Ricardo Wurmus
2018-12-11  8:15 ` Ricardo Wurmus
2018-12-11 17:22   ` Pierre Neidhardt
2018-12-11 17:32     ` Pierre Neidhardt
2018-12-11 17:33       ` Pierre Neidhardt
2018-12-12  1:52       ` Ricardo Wurmus
2018-12-12  7:49         ` Ricardo Wurmus
2018-12-12  7:56           ` Ricardo Wurmus
2018-12-20 10:23             ` Pierre Neidhardt
2018-12-20 10:40               ` Ricardo Wurmus
2018-12-20 10:50                 ` Pierre Neidhardt
2018-12-20 14:31                   ` Ricardo Wurmus
2018-12-20 16:56                     ` Pierre Neidhardt
2018-12-20 21:23                       ` Ricardo Wurmus
2018-12-21 10:55                         ` Pierre Neidhardt
2018-12-21 11:58                           ` Ricardo Wurmus [this message]
2018-12-21 12:39                             ` Pierre Neidhardt
2019-01-13 19:40                               ` Pierre Neidhardt
2019-01-14 15:22                                 ` Pierre Neidhardt
2019-01-14 22:11                                   ` swedebugia
2019-01-14 22:42                                     ` Pierre Neidhardt
2019-02-05 17:55                                       ` Pierre Neidhardt
2019-02-10 18:27                                         ` Pierre Neidhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875zvnrt11.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.