Latest version available for Linux?

Minoscereb

New Member
Hello,
Linux beginner here. I started on Nobara, which seems to have its own OBS build as a standalone package, but am trying out Pop OS now, and I'm confused about the versions of OBS available. I've realised that the flatpak version is a no-go despite being fully up to date because it doesn't seem to pick up plugins (unless there's some kind of workaround for that), so I've tried installing the ppa repository instead, but that gives me an almost a year old version of OBS (30.x.x) on both the stable and the unstable repository. Is this intentional, or am I missing something about how to update the package?

I noticed the Github has a 31.0.3 build as .deb. Can I install that on Pop OS since it's debian based? (I'm guessing yes, since the Ubuntu ppa works?)
 
Last edited:

hurikhan77

New Member
The flatpak actually expects the plugins and configuration in another directory, probably: `$HOME/.var/app/com.obsproject.Studio` or similar. Some plugins require a special flatpak version to be downloaded and put there. Other plugins have a native flatpak package.
 

Minoscereb

New Member
Yeah, I experimented with so many folders on the flatpak version, and the specific plugin I need (Ratwithacompiler's CC plugin) doesn't seem to have a flatpak installer that I've seen (I'd love to be corrected on that), that I finally decided to just install Pop 24.04 instead (despite it's DE being in Alpha) to get an up to date native OBS install.

The .deb for OBS from Github does not work on Pop 22.04, since it's built for Ubuntu 24.04, I learned the hard way.
 

hurikhan77

New Member
Yes, I used flatpak on Gentoo for a while because it has native Twitch panel integration. But it has 5-10% more CPU overhead compared to the native version. So I've gone back to the native version and use Twitch as a PWA instead. OTOH, there are web docks which could be used to replicate the native integration. But in reality, I can use screen real estate more efficiently if I use multiple monitors instead of having everything docked inside OBS.

But at least, back in my flatpak times, I installed plugins into `$HOME/.var/app/com.obsproject.Studio`, sometimes by unpacking deb files manually. You could probably even symlink your native config and plugin directory to the flatpak location, and switch back and forth (unless there's a version difference).

Plugins depending on portals or access to certain directories will require a native flatpak version of the plugin. It doesn't need to come from the flatpak repository, it can also just be put into the plugin directory manually (sometimes with some subdirectory adjustments).
 
Top