From: nospam@needed.invalid
On Mon, 3/31/2025 10:18 AM, Davey wrote:
> On Mon, 31 Mar 2025 07:08:50 -0400
> Paul wrote:
>
>> On Mon, 3/31/2025 5:45 AM, Davey wrote:
>>
>>>
>>> Thanks for the replies. I mostly don't understand them, they are way
>>> above my skill level. But I do remember recently finding that I had
>>> to turn off Hardware Acceleration for something, I believe
>>> concerning playback in some circumstances on VLC. The installation
>>> on this PC would not play a network stream, that played perfectly
>>> well on a different PC, (and on the previous 18.04 setup), and I
>>> believe it was turning off Hardware Acceleration that fixed it. I
>>> think. Firefox did indeed open, I will see what happens next time I
>>> shut down and reboot.
>>> Re: CPU usage. I rarely watch videos on this machine, that's what
>>> the DVR is for.
>>>
>>
>> Try the "vainfo" command and see what it says.
>>
>> Your CPU might be a third generation (like an ivy Bridge).
>> And have an iGPU inside it.
>>
>> inxi -F
>>
>> can give you more info on your hardware.
>>
>> Paul
>
> $ vainfo
> libva info: VA-API version 1.14.0
> libva info: Trying to open
> /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init
> function __vaDriverInit_1_14 libva info: va_openDriver() returns 0
> vainfo: VA-API version: 1.14 (libva 2.12.0)
> vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics -
> 22.3.1 () vainfo: Supported profile and entrypoints
> VAProfileMPEG2Simple : VAEntrypointVLD
> VAProfileMPEG2Main : VAEntrypointVLD
> VAProfileH264Main : VAEntrypointVLD
> VAProfileH264Main : VAEntrypointEncSliceLP
> VAProfileH264High : VAEntrypointVLD
> VAProfileH264High : VAEntrypointEncSliceLP
> VAProfileJPEGBaseline : VAEntrypointVLD
> VAProfileJPEGBaseline : VAEntrypointEncPicture
> VAProfileH264ConstrainedBaseline: VAEntrypointVLD
> VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
> VAProfileVP8Version0_3 : VAEntrypointVLD
> VAProfileHEVCMain : VAEntrypointVLD
> VAProfileHEVCMain10 : VAEntrypointVLD
> VAProfileVP9Profile0 : VAEntrypointVLD
> VAProfileVP9Profile2 : VAEntrypointVLD
>
> $ inxi -F
> System:
> Host: david-NL40-50CU Kernel: 6.8.0-52-generic x86_64 bits: 64
> Desktop: GNOME 42.9 Distro: Ubuntu 22.04.5 LTS (Jammy Jellyfish)
> Machine:
> Type: Laptop System: Notebook product: NL40_50CU v: N/A
> serial:
> Mobo: Notebook model: NL40_50CU serial: UEFI:
> INSYDE v: 1.07.06TPCS date: 09/14/2019
> Battery:
> ID-1: BAT0 charge: 29.8 Wh (100.0%) condition: 29.8/36.2 Wh (82.2%)
> CPU:
> Info: quad core model: Intel Core i7-10510U bits: 64 type: MT MCP
> cache: L2: 1024 KiB
> Speed (MHz): avg: 794 min/max: 400/4900 cores: 1: 800 2: 759 3: 800
> 4: 800 5: 800 6: 800 7: 800 8: 800
> Graphics:
> Device-1: Intel CometLake-U GT2 [UHD Graphics] driver: i915 v: kernel
> Device-2: Acer BisonCam NB Pro type: USB driver: uvcvideo
> Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1
> compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
> OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2)
> v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.3
> Audio:
> Device-1: Intel Comet Lake PCH-LP cAVS driver: snd_hda_intel
> Sound Server-1: ALSA v: k6.8.0-52-generic running: yes
> Sound Server-2: PulseAudio v: 15.99.1 running: yes
> Sound Server-3: PipeWire v: 0.3.48 running: yes
>
> etc etc.
>
That puts a different complexion on the situation.
Your processor is a lot newer than I expected. It's 10th generation.
vainfo, which is not inside a SNAP, is showing quite different version
numbers than is shown inside the SNAP. I would guess the "channel error"
is related to the version and perhaps the resulting differences
in the API.
I would guess this should be filed as a bug against the Firefox SNAP.
Because as a user, it looks to you like it is at fault.
In any event, if seeking help from the distro, you should provide
the information you have uncovered so far. Your SNAP item startup error on
the one hand. Your vainfo and inxi output on the other hand (which in
my opinion, don't align). You can also report to them, whether disabling
HW Acceleration helped or not, to "fix" the situation.
I don't know how SNAPs are supposed to handle this sort of versioning info.
The idea of a SNAP, was it "carried all its dependencies inside the container".
Yet, this error is caused by a mismatch between a driver (in the kernel) and
the software inside the SNAP.
*******
"Disabling hardware acceleration in Firefox: Open Mozilla Firefox;
click on the Firefox [Hamburger] and select "Settings". On the
"General" tab, scroll down to "Performance". Make sure the
"Use recommended performance settings" checkbox is disabled and
disable the "Use hardware acceleration when available" option."
[Picture]
https://i.postimg.cc/KY1gwt0Z/firefox-disable-hw-acceleration-U2404.gif
In about:config, this seems to be the same as:
layers.acceleration.disabled (Boolean) TRUE
and to edit this if Firefox won't start, you would navigate to
cd ~/snap/firefox/common/.mozilla/firefox/b1oalq9y.default #
Your value is not "b1oalq9y"
gedit prefs.js # The
profile 8 characters are random.
The new preference value should look like this:
user_pref("layers.acceleration.disabled", true);
Whether that will disabled the Quicksync Intel video decoder (also
known as VAAPI acceleration), while Firefox runs, who knows. You will know I
guess.
And I don't have to worry about you editing that prefs.js while Firefox
is running, as Firefox won't run right now :-)
*******
Summary: Disable hardware acceleration for immediate relief.
There could be two prefs.js in the ~/.mozilla area,
and you'd want to look at the top level one.
File a bug to get it fixed.
Paul
--- SoupGate-DOS v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
