obsproject/obs-studio

Plugins not loading from /usr/lib/obs-plugins

Closed this issue · 7 comments

Operating System Info

Other

Other OS

CachyOS

OBS Studio Version

Git

OBS Studio Version (Other)

ee212e8

OBS Studio Log URL

https://obsproject.com/logs/5bEOyqdVXp06WEpA

OBS Studio Crash Log URL

No response

Expected Behavior

Plugins installed in /usr/lib/obs-plugins are loaded.

Current Behavior

It seems plugins from /usr/lib/obs-plugins are no longer being loaded. This is being installed from the obs-studio-git package on the AUR which sets:

    -DCMAKE_INSTALL_PREFIX='/usr'
    -DCMAKE_INSTALL_LIBDIR='lib'

Steps to Reproduce

  1. Install obs with
    -DCMAKE_INSTALL_PREFIX='/usr'
    -DCMAKE_INSTALL_LIBDIR='lib'
  1. Install a plugin in /usr/lib/obs-plugins
  2. Plugin is not loaded when opening obs

Anything else we should know?

No response

If the plugins you're installing were built for OBS < 32, they are not gonna work and will need to be rebuilt for OBS 32 since #12566. But I think this is going to be reverted.

I have rebuilt the plugins after the update and they still don't load, currently going through commits to find out where it broke. Will double check the commit you link.

It looks like that is in-fact the issue, plugins load on 11b9f1a (the commit before those patches) but do not load on a7b5aef (the commit after those patches). Not sure if I should just close this or not, it seems rebuilding the plugins after the new version should allow them to load unless downstream changes are needed in the plugins.

It seems the patch was reverted, try with at least 21f2d97

Reinstalled from the AUR which at the time of writing installed 99c3a4b and everything is working as expected.

For what it is worth, having tested the particular pull request on Gentoo Linux, the plug-ins here are installed under /usr/lib64/obs-plugins/ instead of /usr/lib/obs-plugins/, and do get loaded, but I don't see why that would make a difference like so...

To rebuild the plugins I reinstalled them from the AUR, but in hindsight that might have just reinstalled a cached copy of the previous build.