OBS Studio installation package for Ubuntu 24.04

FabioElizeu

FabioElizeu

Member
I would like to suggest that the .DEB packages have their installation directories adjusted. Ubuntu 24.04-based distributions use the standard structure in /usr, while the currently available packages mount their structures in /usr/local, which causes problems with adding plugins, among other things.

Although the PPA version of OBS is installed in the appropriate directories on Ubuntu 24.04-based distributions, I believe that having the option of offline installation is important to revert or switch between OBS versions in some situations.

If the current structure of the OBS .DEB installation packages must be maintained for some reason, I suggest making .DEB installation packages available that direct the directory structures and shortcuts to a structure compatible with Ubuntu 24.04-based distributions.

Alternatively, I have extracted the contents of the .DEB packages and manually allocated the directory structures, but I believe this is not ideal and also creates difficulties for some users.

I really like this project and I thank you in advance.
 
Tuna said:
Click to expand...
Hi @Tuna

Thank you for your feedback. I understand the recommendation in the cited reference, but couldn't the DEB package also fit the context "Locally installed software must be placed within /usr/local rather than /usr unless it is being installed to replace or upgrade software in /usr," since the version distributed via PPA is installed in /usr, as stated in the cited reference itself?

I believe that a large portion of OBS users also use plugins. In my tests, I detected that several plugins have DEB packages that are installed in /usr and are not recognized by OBS Studio when the program is installed in /usr/local. There is also a range of plugins that, even when inserted into the structure in /usr/local, end up not finding OBS Studio libraries, which makes it necessary to create symbolic links manually and still leaves room for errors. When allocating plugins in the user profile structure, we also have problems when OBS is in /usr/local.

Given the context, and considering all the difficulties users face in structuring plugins with OBS Studio in /usr/local, do you suggest another viable alternative to avoid having an OBS Studio DEB package structuring the installation in /usr?

Thank you very much in advance!
 
As "not a Linux dev" myself, I really don't care all that much about the underlying organizational structure. I just want things to work.

If the online PPA and offline DEB put things in different places, and both the program itself and its plugins assume only one of them, thus creating a mismatch that doesn't work, then that's a problem that needs to be fixed. There are several ways to fix it, but it does need to be fixed.
 
FabioElizeu said:
Here's a link with instructions I found online.
Click to expand...
FINALLY got back to this! My schedule is a mess...

Anyway, that worked. Thank you! Unpacked the .DEB from github, moved everything from usr/local to just usr, fixed up the other files that that affects, re-packaged, and installed that. But it's not as straightforward as the article implies:
  • The .DEB from github has a different structure. It unpacks just fine, but if you keep that structure, dpkg-deb doesn't like it at the end. So you have to think a bit more and convert it manually to what the article says, and *then* dpkg-deb will take it.
  • The article implies that dpkg-deb needs to run inside of the package's root folder. That is not true. It needs to run outside of it, and the last argument according to the article (the name) needs to be that root folder. The resulting .DEB will have the same name as that folder.
  • Don't know if I *had* to remove OBS first, before installing the fixed version, but I did, and it worked. sudo apt remove obs-studio, not the .DEB filename that it originally installed from. It also removed the plugins, which I guess is understandable, so after the first run of the fixed OBS, I reinstalled those like normal. They all work too.
 
AaronD said:
FINALLY got back to this! My schedule is a mess...

Anyway, that worked. Thank you! Unpacked the .DEB from github, moved everything from usr/local to just usr, fixed up the other files that that affects, re-packaged, and installed that. But it's not as straightforward as the article implies:
  • The .DEB from github has a different structure. It unpacks just fine, but if you keep that structure, dpkg-deb doesn't like it at the end. So you have to think a bit more and convert it manually to what the article says, and *then* dpkg-deb will take it.
  • The article implies that dpkg-deb needs to run inside of the package's root folder. That is not true. It needs to run outside of it, and the last argument according to the article (the name) needs to be that root folder. The resulting .DEB will have the same name as that folder.
  • Don't know if I *had* to remove OBS first, before installing the fixed version, but I did, and it worked. sudo apt remove obs-studio, not the .DEB filename that it originally installed from. It also removed the plugins, which I guess is understandable, so after the first run of the fixed OBS, I reinstalled those like normal. They all work too.
Click to expand...

I posted about this in the announcement for the new version of OBS Studio. I hope there's some adjustment that can solve the issue.

FabioElizeu

Post in thread 'OBS Studio 32.1 Beta'

Penwy said:
For the record, the recommended and supported plugin installation location for a linux system install is in the user config folder, at ~/.config/obs-studio/plugins, which wouldn't be affected by this.
I know a fair few developpers package into debs that install to the obs install folder, but they should be asked to repackage into something that uses the proper third-party plugins folder.
Click to expand...
Hi @Penwy

Thank you for your feedback.

In my experience, I've noticed that some plugins don't function correctly when placed in user configuration directories, leading some developers to...
 
You must log in or register to reply here.
Back
Top