bug#44417: ungoogle-chromium crashes on Jitsi & co.

[Maxim Cournoyer]

Hi Ludo,

Ludovic Courtès <ludovic.courtes@inria.fr> writes:

> 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:
>
> [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
>
>> 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’.

Just a friendly ping on this issue; at least the title needs to be
updated :-).  What are the '& co'; are there other publicly available
services we can try to reproduce with?

Thanks,

Maxim