unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Marius Bakke <marius@gnu.org>
Cc: 44417@debbugs.gnu.org
Subject: bug#44417: ungoogle-chromium crashes on Jitsi & co.
Date: Wed, 04 Nov 2020 11:16:06 +0100	[thread overview]
Message-ID: <87d00tbf6h.fsf@inria.fr> (raw)
In-Reply-To: <87r1paggv2.fsf@gnu.org> (Marius Bakke's message of "Wed, 04 Nov 2020 00:28:33 +0100")

Hi,

Marius Bakke <marius@gnu.org> skribis:

> Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>
>> Current ungoogle-chromium (commit
>> e1f5c2292b88525414b5d0336a00bfa6741d4f14) crashes upon displaying video
>> as in Jitsi (GPU_DEAD_UPON_ARRIVAL error, IIRC).
>
> The demo at https://meet.jit.si "works for me".  That is with
> "intel-vaapi-driver" installed.  Does that make a difference?

Hmm actually Jitsi works for me too.

The one that doesn’t is a private video-conferencing thing at work (not
running Jitsi but very similar).  With the commit above, it says “Error
code: 4” (the GPU error was with an older commit).

The console shows:

--8<---------------cut here---------------start------------->8---
[16695:19:1104/110713.814684:ERROR:audio_rtp_receiver.cc(89)] AudioRtpReceiver::OnSetVolume: No audio channel exists.
[16695:19:1104/110714.263441:ERROR:webrtc_video_engine.cc(3327)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
[16695:19:1104/110714.264357:ERROR:webrtc_video_engine.cc(3327)] Absent receive stream; ignoring clearing encoded frame sink for ssrc 0
--8<---------------cut here---------------end--------------->8---

> Probably not, because it works here even without $LIBVA_DRIVERS_PATH.
>
> Which GPU are you using?

It’s i915 and LIBVA_DRIVERS_PATH is unset.

> Recently Chromium started building its own libGL.so and complains about
> it not being found at startup (because it looks in $out/lib).  I'm
> currently testing a patch that makes it use Mesas libGL mainly to
> quiesce the warning.  Not sure if that is related, we'll see...

OK.

Thanks,
Ludo’.




  reply	other threads:[~2020-11-04 10:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 15:17 bug#44417: ungoogle-chromium crashes on Jitsi & co Ludovic Courtès
2020-11-03 23:28 ` Marius Bakke
2020-11-04 10:16   ` Ludovic Courtès [this message]
2020-11-30  3:48     ` Maxim Cournoyer
2020-11-30  8:06       ` Ludovic Courtès
2021-01-19  5:26         ` bug#44417: ungoogle-chromium crashes on some videoconf web sites Maxim Cournoyer
2021-01-25 17:12           ` Ludovic Courtès
2021-01-25 18:53             ` Maxim Cournoyer
2021-01-28  8:23               ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87d00tbf6h.fsf@inria.fr \
    --to=ludovic.courtes@inria.fr \
    --cc=44417@debbugs.gnu.org \
    --cc=marius@gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).