Couldn't load XPCOM

[Arndorferd]

Newest update causes

XPCOMGlueLoad error for file /usr/lib/firedragon/libxul.so: libvpx.so.9: cannot open shared object file: No such file or directory Couldn't load XPCOM.

when trying to open firedragon in 6.7.0-0-MANJARO

[Technetium1]

Cannot reproduce; but not using Manjaro. What is your output for this? Please confirm you're up to date too.

[tech@lynx ~]$ sudo pacman -Fy libvpx.so
:: Synchronizing package databases...
extra/libvpx 1.14.0-1 [installed]
    usr/lib/libvpx.so
multilib/lib32-libvpx 1.14.0-1
    usr/lib32/libvpx.so

[dr460nf1r3]

Self-built from AUR?

[Arndorferd]

Cannot reproduce; but not using Manjaro. What is your output for this? Please confirm you're up to date too.

[tech@lynx ~]$ sudo pacman -Fy libvpx.so
:: Synchronizing package databases...
extra/libvpx 1.14.0-1 [installed]
    usr/lib/libvpx.so
multilib/lib32-libvpx 1.14.0-1
    usr/lib32/libvpx.so

Mine is

:: Synchronizing package databases... core extra community multilib chaotic-aur extra/libvpx 1.13.1-1 [installed] usr/lib/libvpx.so multilib/lib32-libvpx 1.13.1-1 [installed] usr/lib32/libvpx.so

[dr460nf1r3]

chaotic-aur

Using Chaotic-AUR with Manjaro makes such errors expected as package versions may lag behind. I suggest building it yourself from AUR to work around that.

[Arndorferd]

Lol no, the version is behind in the AUR itself, Chaotic aur just gives options, I dont need to use it.

[Arndorferd]

[dr460nf1r3]

So is the firedragon package self-built or is it the one from CAUR? In any case sourcing from there makes such errors expected as we build against Arch lib versions.

Libvpx should be provided by your distribution if I'm not mistaken.

[Arndorferd]

So is the firedragon package self-built or is it the one from CAUR? In any case sourcing from there makes such errors expected as we build against Arch lib versions.

I dont believe it matters, I think its because libvpx is out of date in the AUR. Im getting this only after an update of firedragon.

[Arndorferd]

Manjaro is often slow in updating its packages

[dr460nf1r3]

So is the firedragon package self-built or is it the one from CAUR? In any case sourcing from there makes such errors expected as we build against Arch lib versions.

I dont believe it matters, I think its because libvpx is out of date in the AUR. Im getting this only after an update of firedragon.

I don't think I understand. What does the AUR package have to do with it? Libvpx should be a package provided by Manjaro which, as you noted yourself, is slower with updating packages. Library version mismatches are a known issue with Chaotic-AUR and Manjaro, arising from these slower updates.

[Technetium1]

I think its because libvpx is out of date in the AUR

This is not the case, as it is actually provided in Arch's extra repo. For this reason, you can blame Manjaro, and you will continue to have issues when not building it yourself in the context of correct dependencies.

Manjaro is often slow in updating its packages

Yes; exactly 😞… The issue you have is that Manjaro doesn't push the new version to their mirrors, so it will fail until then. Your best bet is going to be opening a Manjaro forum post and requesting that the package gets bumped.

[Arndorferd]

Is there a reason though the package requirements for this are so bleeding edge though. Manjaro is a bit annoying in that regard and it has happened with other things but I think its happened several times for just firedragon and not other similar programs like firefox.

[Arndorferd]

Also I saw

This is not the case, as it is actually provided in Arch's extra repo. For this reason, you can blame Manjaro, and you will continue to have issues when not building it yourself in the context of correct dependencies.

but it has no git clone even and I have extra in my repository list as you saw here

core extra community multilib chaotic-aur extra/libvpx 1.13.1-1 [installed] usr/lib/libvpx.so multilib/lib32-libvpx 1.13.1-1 [installed] usr/lib32/libvpx.so

so I wasnt sure if that package was even in a ready to use state?

[Arndorferd]

Ok so I guess these extra repositories can be installed using pacman -U after downloading their respective zips directly which I didnt realize and they do work. It was kinda a dependency hell but I did update things manually. My question remains though why does firedragon have such bleeding edge requirements?

[dr460nf1r3]

I would be careful about simply upgrading like that. It might break every other package depending on that package..

It does not need bleeding edge deps, it's simply built against those libs. Have version x while compiling? You now need it at runtime too. It's y? Well sure but now you need y and can't run it with x.

[Technetium1]

@Arndorferd as just mentioned, you will possibly break some things as a consequence, so you should look at the Required By column for libvpx to see what can be affected. I personally tend to share a lot of similar grievances towards Manjaro for same issue you're currently experiencing: https://github.com/arindas/manjarno

[Arndorferd]

I understand the risks but it was only ffmpeg and its dependancies that stood in the way and I updated what was required without flags. Ill take it as it comes but I dont think anything I need will be of issue.