Skip to main content ↑ ↓
Topic: [SOLVED] Librewolf errors out due to not finding libvpx.so.8 (Read 569 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[SOLVED] Librewolf errors out due to not finding libvpx.so.8

Hi all. After today's update, I tried to open my go to browser Librewolf with my usual keyboard macro, and lo and behold...no Librewolf.

Attempts at opening it from the terminal yield this error message:

Code: [Select]
XPCOMGlueLoad error for file /usr/lib/librewolf/libxul.so:
libvpx.so.8: cannot open shared object file: No such file or directory

I'm not sure which packages in the update today would have affected this lib, but here are the logs from today's -Syu:

Code: [Select]
upgraded cargo-make (0.37.7-1 -> 0.37.8-1)
upgraded docker-compose (2.24.2-1 -> 2.24.3-1)
upgraded eza (0.17.2-1 -> 0.17.3-1)
upgraded rav1e (0.6.6-3 -> 0.7.1-1)
upgraded libvpx (1.13.1-1 -> 1.14.0-1)
upgraded ffmpeg (2:6.1.1-2 -> 2:6.1.1-3)
upgraded gstreamer (1.22.8-2 -> 1.22.9-1)
upgraded gst-plugins-base-libs (1.22.8-2 -> 1.22.9-1)
upgraded gst-plugins-bad-libs (1.22.8-2 -> 1.22.9-1)
upgraded gst-plugins-base (1.22.8-2 -> 1.22.9-1)
upgraded gst-plugins-good (1.22.8-2 -> 1.22.9-1)
upgraded gst-plugins-ugly (1.22.8-2 -> 1.22.9-1)
upgraded gst-python (1.22.8-2 -> 1.22.9-1)
upgraded libavif (1.0.3-1 -> 1.0.3-2)
upgraded libheif (1.17.6-1 -> 1.17.6-3)
upgraded npm (10.3.0-1 -> 10.4.0-1)
upgraded pnpm (8.14.1-1 -> 8.14.3-1)
upgraded suitesparse (7.5.1-1 -> 7.6.0-1)
upgraded thunderbird (115.6.1-1 -> 115.7.0-2)

I'm not sure which of these packages would have had any effect on Librewolf like this, and I'm admittedly confused as I use my computer every day and Librewolf was working fine until today after this update. I have tried reinstalling Librewolf just to be sure, but to no avail of my predicament.

For further reference, I do update Librewolf from the omniverse repository, so I'm not sure if this is a packaging issue, but I'm not seeing any open issues regarding this on the official Librewolf repo over on codeberg.

Any ideas or insights on how to resolve this issue would be very much appreciated.

And as always, thanks in advance.

Re: Librewolf errors out due to not finding libvpx.so.8

Reply #1 –
Quote from: z3rOR0ne – on
I'm not sure which of these packages would have had any effect on Librewolf like this,
It's right there.
Code: [Select]
upgraded libvpx (1.13.1-1 -> 1.14.0-1)
Librewolf will need rebuilding.
As a workaround you could maybe link whatever version of the library libvpx just installed to libvpx.so.8 (doesn't always work)
You could get libvpx.so.8 from the last libvpx package either from your cache or the online archive and copy it to /usr/lib
Sometimes downgrading the package i.e libvpx is an option but I wouldn't have thought so here as other packages likely depend on the new library.
Or wait for a new Librewolf package


Re: Librewolf errors out due to not finding libvpx.so.8

Reply #2 –
Quote from: gripped – on
Quote from: z3rOR0ne – on
I'm not sure which of these packages would have had any effect on Librewolf like this,
It's right there.
Code: [Select]
upgraded libvpx (1.13.1-1 -> 1.14.0-1)
Librewolf will need rebuilding.
As a workaround you could maybe link whatever version of the library libvpx just installed to libvpx.so.8 (doesn't always work)
You could get libvpx.so.8 from the last libvpx package either from your cache or the online archive and copy it to /usr/lib
Sometimes downgrading the package i.e libvpx is an option but I wouldn't have thought so here as other packages likely depend on the new library.
Or wait for a new Librewolf package

Thank you, looks like I am blind when it comes to reviewing errors, at least initially. It took me a second after posting this to investigate the error further to recognize what exactly this was related. My attempts at downgrading libvpx back result in a dependency hell sort of series of warnings related to ffmpeg, etc.

Best practice is usually to wait for packages to be rebuilt, but at least now there's a record of it here for those who also encounter the error.

I really appreciate the suggestions and prompt response. I'll mark this as resolved once librewolf on the omniverse repo is rebuilt and this is resolved.

Thank you!

Re: Librewolf errors out due to not finding libvpx.so.8

Reply #3 –
rebuild was/is running, but takes a while; about 2 hrs left to go

artist
 

Re: Librewolf errors out due to not finding libvpx.so.8

Reply #4 –
Quote from: Artist – on
rebuild was/is running, but takes a while; about 2 hrs left to go

artist

Thank you so much. Just pulled in the fix. Very  much appreciated @Artist.