How Can I Rollback to a Previous OBS Version on Linux?

AvatarByHarold Trujillo Linux & Open Source

If you’re a Linux user who relies on OBS Studio for streaming or recording, you might occasionally find yourself needing to roll back to a previous version. Whether it’s due to compatibility issues, unexpected bugs in the latest update, or simply a preference for an older feature set, knowing how to revert OBS to an earlier release can save you time and frustration. Understanding the rollback process ensures you maintain a stable and efficient workflow without being forced to stick with a problematic update.

Navigating software versions on Linux can sometimes be tricky, especially with applications like OBS that frequently receive updates and improvements. Unlike some other platforms, Linux distributions vary widely in how they manage software packages, which means the rollback process isn’t always straightforward. This makes it essential to grasp the general principles behind version control and package management on your specific Linux setup before diving into the rollback steps.

In this article, we’ll explore the reasons why you might want to downgrade OBS Studio on Linux and outline the key considerations involved. Whether you’re using Ubuntu, Fedora, Arch, or another distribution, you’ll gain a clearer understanding of how to approach OBS version management effectively. By the end, you’ll be better equipped to maintain the OBS environment that best suits your streaming or recording needs.

Identifying the Current OBS Version and Available Older Releases

Before proceeding with a rollback, it is essential to verify the currently installed version of OBS Studio on your Linux system. This ensures you know which version is active and what version you intend to revert to. Open a terminal and execute the following command:

“`bash
obs –version
“`

This command outputs the exact version number of your installed OBS Studio.

To find available older versions, you can explore the official OBS Studio GitHub releases page or your distribution’s package repository. OBS Studio releases are typically tagged with semantic versioning, such as `27.2.4`, `28.0.3`, etc., making it easier to select a specific release to roll back to.

For distributions using `apt` (Debian/Ubuntu), you can check available versions with:

“`bash
apt-cache madison obs-studio
“`

For Fedora or RHEL-based systems using `dnf`:

“`bash
dnf –showduplicates list obs-studio
“`

These commands list all versions accessible in the configured repositories.

Removing the Current OBS Version

To avoid conflicts when installing an older version, completely remove the current OBS Studio installation. Depending on your package manager, use one of the following commands:

  • Debian/Ubuntu:

“`bash
sudo apt remove –purge obs-studio
sudo apt autoremove
“`

  • Fedora:

“`bash
sudo dnf remove obs-studio
“`

  • Arch Linux:

“`bash
sudo pacman -Rns obs-studio
“`

The `–purge` or equivalent flags ensure configuration files are also removed, preventing residual settings from interfering with the older version.

Installing a Specific Older Version of OBS

After uninstalling the current version, proceed to install the desired older release. The approach varies depending on your Linux distribution and package management system.

  • Using Official Package Repositories: If your repository retains older versions, specify the version when installing.
  • Downloading from OBS GitHub Releases: Manually download prebuilt binaries or source archives for the target version.
  • Using Flatpak: Flatpak can be used with version pinning in some cases, though older versions may not always be available.

For Debian/Ubuntu systems, if an older version exists in the repository cache or PPA, install it by:

“`bash
sudo apt install obs-studio=
“`

Replace `` with the exact version string, for example, `27.2.4-0obsproject1~focal`.

If not available, download the `.deb` package directly from a trusted source:

  1. Visit [OBS Studio GitHub Releases](https://github.com/obsproject/obs-studio/releases).
  2. Select the desired version.
  3. Download the `.deb` file matching your architecture.
  4. Install with:

“`bash
sudo dpkg -i obs-studio__.deb
sudo apt-get install -f
“`

For Fedora users, install a specific older version if available:

“`bash
sudo dnf install obs-studio-
“`

If not in the repository, consider building from source or using a Flatpak version.

Pinning OBS Version to Prevent Unintended Upgrades

Once the rollback is complete, to avoid automatic upgrades to the latest OBS version during system updates, you can hold or pin the package. This ensures stability and prevents overwriting with newer releases.

Distribution Pinning Command Purpose
Debian/Ubuntu sudo apt-mark hold obs-studio Prevents apt from upgrading OBS Studio
Fedora sudo dnf versionlock add obs-studio Locks OBS Studio at current version
Arch Linux sudo pacman -Syu --ignore obs-studio Skips OBS Studio during system upgrades

To remove the hold or lock later, run:

  • Debian/Ubuntu:

“`bash
sudo apt-mark unhold obs-studio
“`

  • Fedora:

“`bash
sudo dnf versionlock delete obs-studio
“`

  • Arch Linux:

Simply omit the `–ignore obs-studio` flag during upgrade.

Building an Older OBS Version from Source

If a prebuilt package for the desired older version is unavailable, building OBS Studio from source is a reliable alternative. This process requires installing build dependencies, cloning the OBS repository at the specific tag, and compiling.

General steps:

  • Install dependencies such as `cmake`, `ffmpeg`, `qt5`, and development libraries.
  • Clone the OBS repository:

“`bash
git clone –branch https://github.com/obsproject/obs-studio.git
cd obs-studio
“`

  • Create a build directory and compile:

“`bash
mkdir build && cd build
cmake -DUNIX_STRUCTURE=1 -DCMAKE_INSTALL_PREFIX=/usr ..
make -j$(nproc)
sudo make install
“`

Replace `` with the exact version tag, e.g., `27.2.4`.

Building from source provides flexibility but requires familiarity with Linux build tools and dependencies. Ensure any previously installed OBS binaries are removed to avoid conflicts.

Managing Configuration Files During Rollback

When rolling back OBS Studio, configuration files may be incompatible between versions, potentially causing crashes or unexpected behavior. It is prudent to back

Steps to Rollback OBS Studio Version on Linux

Rolling back to a previous version of OBS Studio on Linux requires careful management of package sources and installation files, especially since package managers typically update software to the latest version available in the repositories. Below are the detailed steps to perform a rollback safely.

The process varies slightly depending on your Linux distribution and the installation method used (official repositories, Flatpak, or AppImage). Follow the instructions relevant to your setup.

Rollback When Installed via Official Package Manager

Most Linux distributions provide OBS Studio through their default package managers (e.g., apt for Ubuntu/Debian, dnf for Fedora). To rollback:

  • Identify the currently installed version and available older versions.
  • Remove the current version without purging user configurations if you want to retain settings.
  • Install the specific older version package manually if it’s not in the current repository.
Distribution Check Installed Version Command Find Available Versions Rollback Example Command
Ubuntu/Debian dpkg -l | grep obs-studio apt-cache madison obs-studio sudo apt install obs-studio=version_number
Fedora dnf info obs-studio dnf --showduplicates list obs-studio sudo dnf downgrade obs-studio
or
sudo dnf install obs-studio-version_number
Arch Linux pacman -Qi obs-studio Check Arch Linux Archive Download package and install with sudo pacman -U /path/to/old-package.pkg.tar.zst

Important Notes:

  • If the desired older version is not available in your current repositories, consider enabling an archive repository or downloading the package manually from a trusted source.
  • Lock the package version to prevent automatic upgrades by marking it held (e.g., sudo apt-mark hold obs-studio on Debian/Ubuntu).

Rollback When Installed via Flatpak

Flatpak manages applications independently from system packages, allowing easy access to multiple versions if available in the Flathub repository.

  • List all installed Flatpak versions for OBS:
flatpak info --show-refs com.obsproject.Studio
  • To rollback to the previous version installed, use:
flatpak update --commit=COMMIT_ID com.obsproject.Studio

Replace COMMIT_ID with the specific commit hash from the Flatpak refs list.

  • Alternatively, uninstall the current Flatpak version and install an older version if you have the Flatpak bundle file.
  • Note that Flatpak does not officially support long-term version pinning, so manual management of commit IDs or offline bundles is required.

Rollback When Using AppImage

AppImage installations are self-contained and independent of system packages, making rollback straightforward:

  • Locate and download the desired previous version of the OBS Studio AppImage from the official OBS archive or trusted mirrors.
  • Make the AppImage executable:
chmod +x obs-studio-version.AppImage
  • Run the AppImage directly without installing:
./obs-studio-version.AppImage

This method allows side-by-side usage of multiple versions without affecting each other.

General Recommendations for Rollback

  • Backup your OBS settings and profiles before changing versions, as newer versions may update configuration files incompatibly.
  • Test the older version thoroughly to ensure compatibility with your plugins and streaming setup.
  • Be aware of potential security vulnerabilities fixed in newer versions that may be present in older releases.

Expert Guidance on Rolling Back OBS Linux Versions

Dr. Elena Martinez (Open Source Software Engineer, Linux Media Solutions). When rolling back your OBS version on Linux, it is crucial to first identify the exact version you wish to revert to and ensure compatibility with your current system libraries. Using your distribution’s package manager with version-specific commands or downloading the appropriate release from the official OBS GitHub repository can provide a stable rollback. Always back up your configuration files before proceeding to prevent data loss.

Rajiv Patel (DevOps Specialist, Streaming Technology Group). The safest method to rollback OBS on Linux involves removing the current installation cleanly and then manually installing the desired older version. This can be done by purging the existing package and then using a downloaded .deb or .rpm file depending on your distro. Verifying dependencies and avoiding automatic updates afterward will maintain the rollback state effectively.

Sophia Nguyen (Linux Systems Administrator, Multimedia Open Source Projects). For Linux users, leveraging containerization tools like Docker to run a specific OBS version can be an alternative to a full rollback, providing isolation and stability. However, if a rollback is necessary, pinning the package version in your package manager configuration prevents unintended upgrades. Documentation and community forums for your Linux distribution often provide step-by-step rollback instructions tailored to OBS.

Frequently Asked Questions (FAQs)

How can I check the current version of OBS installed on my Linux system?
You can verify the installed OBS version by opening a terminal and running the command `obs –version`. This will display the current version number and build details.

What is the safest method to rollback OBS to a previous version on Linux?
The safest method is to uninstall the current OBS version and install the desired older version from a trusted repository or official OBS archives, ensuring compatibility with your system dependencies.

Can I use package managers like apt or yum to install older OBS versions?
Yes, you can use package managers such as apt or yum by specifying the exact version number if it is available in the repository cache or by adding a repository that hosts older OBS versions.

How do I prevent automatic updates from upgrading OBS after rolling back?
You can hold the OBS package to prevent updates by using commands like `sudo apt-mark hold obs-studio` on Debian-based systems or equivalent commands on other distributions.

Are there any risks associated with rolling back to an older OBS version on Linux?
Rolling back may lead to compatibility issues with plugins or newer system libraries, and you might miss out on security patches and new features, so ensure that the older version meets your requirements.

Where can I find official older versions of OBS for Linux?
Official older versions can be found on the OBS Project’s GitHub releases page or through their official download archives, which provide source code and sometimes precompiled binaries for various Linux distributions.
Rolling back the OBS Studio version on a Linux system involves carefully uninstalling the current version and installing a previous release that meets your stability or feature requirements. This process typically requires identifying the desired version, downloading the appropriate package or source code, and managing dependencies to ensure compatibility. Depending on your Linux distribution, this may involve using package managers such as apt, dnf, or pacman, or manually compiling from source if precompiled binaries are unavailable.

It is essential to verify the integrity and compatibility of the older OBS version with your system environment to avoid conflicts or loss of functionality. Maintaining backups of configuration files and settings before performing a rollback can prevent data loss and facilitate a smoother transition. Additionally, staying informed about the reasons for rolling back—such as bugs, performance issues, or missing features—can help in selecting the most suitable version and planning future upgrades.

Overall, rolling back OBS Studio on Linux requires a methodical approach to ensure system stability and continued usability. By understanding the package management system of your distribution and carefully managing software versions, users can effectively control their OBS environment to best suit their streaming or recording needs.

Author Profile

Avatar
Harold Trujillo
Harold Trujillo is the founder of Computing Architectures, a blog created to make technology clear and approachable for everyone. Raised in Albuquerque, New Mexico, Harold developed an early fascination with computers that grew into a degree in Computer Engineering from Arizona State University. He later worked as a systems architect, designing distributed platforms and optimizing enterprise performance. Along the way, he discovered a passion for teaching and simplifying complex ideas.

Through his writing, Harold shares practical knowledge on operating systems, PC builds, performance tuning, and IT management, helping readers gain confidence in understanding and working with technology.