| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 28 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 64:04:36 |
| Calls: | 425 |
| Calls today: | 3 |
| Files: | 1,025 |
| Messages: | 91,325 |
| Posted today: | 1 |
Booted up this morning, Ubuntu 22.04, In was using Firefox last night
until I went to bed. This morning, all I could get was the spinning
wheel, then nothing. Repeatedly.
Tried 'firefox' from the command line, was told it didn't exist, but
could be installed by 'sudo apt install firefox'.
So what happened to the previous version?
It installed firefox snapd, and luckily, all my previous tabs are still there.
But the terminal shows unhappiness:
08:15:47.118: Not loading module "atk-bridge": The functionality is
provided by GTK natively. Please try to not load it. libva info: VA-API version 1.20.0 libva info: Trying to open /snap/firefox/5917/gnome-platform/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 ^CExiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
It did not finish the installation on its own, it left it hanging at
'Exiting due to channel error'.The 'unhappiness' means nothing to me.
Channel error? Who he?
On Mon, 3/31/2025 3:27 AM, Davey wrote:
Booted up this morning, Ubuntu 22.04, In was using Firefox last night
until I went to bed. This morning, all I could get was the spinning
wheel, then nothing. Repeatedly.
Tried 'firefox' from the command line, was told it didn't exist, but
could be installed by 'sudo apt install firefox'.
So what happened to the previous version?
It installed firefox snapd, and luckily, all my previous tabs are still
there.
But the terminal shows unhappiness:
08:15:47.118: Not loading module "atk-bridge": The functionality is
provided by GTK natively. Please try to not load it. libva info: VA-API
version 1.20.0 libva info: Trying to open
/snap/firefox/5917/gnome-platform/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_20 libva info:
va_openDriver() returns 0 ^CExiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
It did not finish the installation on its own, it left it hanging at
'Exiting due to channel error'.The 'unhappiness' means nothing to me.
Channel error? Who he?
It could be that the line:
/snap/firefox/5917/gnome-platform/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
is erroneous. The software doing that, may be trying iHD first, in preference to i965. Something like this before running it, may cause the driver
logic to stop trying iHD at all, and trying the driver your hardware
really uses.
export LIBVA_DRIVER_NAME=i965
A person doing that, was getting this from inxi -F. And in their
opinion, the i965 would be a better choice than iHD.
Graphics:
Device-1: Intel 3rd Gen Core processor Graphics vendor: Hewlett-Packard
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0166
Display: x11 server: X.Org 1.20.9 compositor: compton driver: intel
unloaded: modesetting alternate: fbdev,vesa display ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 99 s-size: 352x198mm (13.9x7.8")
s-diag: 404mm (15.9")
Monitor-1: LVDS1 res: 1366x768 hz: 60 dpi: 112 size: 310x170mm (12.2x6.7")
diag: 354mm (13.9")
OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2)
v: 4.2 Mesa 20.1.8 compat-v: 3.0 direct render: Yes
What is supposed to happen, apparently, is some piece of code tries
iHD first, and when that fails, it is supposed to try i965. Doing the
Export above, tries to get it to use the second one immediately.
*******
At some previous point in time, hardware acceleration was broken,
and Firefox users frequently had to find some preference (Configuration Editor?)
to turn off hardware acceleration. Then it should stop trying for things
like the item above. If you can't get Firefox open, you can look for
prefs.js and edit with a text editor (that's the file that corresponds
to Configuration Editor).
The reason you might want it to use vaapi, is to reduce the loading on
the CPU, when playing a video. It's really hard on the CPU, to have
all the graphics operations go to fallback code. You need like a quad core, to keep up.
Paul
On Mon, 3/31/2025 3:27 AM, Davey wrote:
Booted up this morning, Ubuntu 22.04, In was using Firefox last
night until I went to bed. This morning, all I could get was the
spinning wheel, then nothing. Repeatedly.
Tried 'firefox' from the command line, was told it didn't exist, but
could be installed by 'sudo apt install firefox'.
So what happened to the previous version?
It installed firefox snapd, and luckily, all my previous tabs are
still there.
But the terminal shows unhappiness:
08:15:47.118: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. libva info:
VA-API version 1.20.0 libva info: Trying to open /snap/firefox/5917/gnome-platform/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 ^CExiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
It did not finish the installation on its own, it left it hanging at 'Exiting due to channel error'.The 'unhappiness' means nothing to
me. Channel error? Who he?
It could be that the line:
/snap/firefox/5917/gnome-platform/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
is erroneous. The software doing that, may be trying iHD first, in
preference to i965. Something like this before running it, may cause
the driver logic to stop trying iHD at all, and trying the driver
your hardware really uses.
export LIBVA_DRIVER_NAME=i965
A person doing that, was getting this from inxi -F. And in their
opinion, the i965 would be a better choice than iHD.
Graphics:
Device-1: Intel 3rd Gen Core processor Graphics vendor:
Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 chip ID:
8086:0166 Display: x11 server: X.Org 1.20.9 compositor: compton
driver: intel unloaded: modesetting alternate: fbdev,vesa display ID:
:0.0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 99 s-size:
352x198mm (13.9x7.8") s-diag: 404mm (15.9")
Monitor-1: LVDS1 res: 1366x768 hz: 60 dpi: 112 size: 310x170mm
(12.2x6.7") diag: 354mm (13.9")
OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2)
v: 4.2 Mesa 20.1.8 compat-v: 3.0 direct render: Yes
What is supposed to happen, apparently, is some piece of code tries
iHD first, and when that fails, it is supposed to try i965. Doing the
Export above, tries to get it to use the second one immediately.
*******
At some previous point in time, hardware acceleration was broken,
and Firefox users frequently had to find some preference
(Configuration Editor?) to turn off hardware acceleration. Then it
should stop trying for things like the item above. If you can't get
Firefox open, you can look for prefs.js and edit with a text editor
(that's the file that corresponds to Configuration Editor).
The reason you might want it to use vaapi, is to reduce the loading on
the CPU, when playing a video. It's really hard on the CPU, to have
all the graphics operations go to fallback code. You need like a quad
core, to keep up.
Paul
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.
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
On Mon, 31 Mar 2025 07:08:50 -0400
Paul <nospam@needed.invalid> 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: <superuser required>
Mobo: Notebook model: NL40_50CU serial: <superuser required> 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.
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.
