obsproject / obsproject/obs-studio

Browser sources broken on Flatpak in 32.0.4

Open
#12,944 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
76.4k
Forks
10.2k
Avg merge
4d 23h
Merged PRs (30d)
12

Description

Operating System Info

Other

Other OS

OpenSUSE

OBS Studio Version

Other

OBS Studio Version (Other)

32.0.4

OBS Studio Log URL

https://obsproject.com/logs/is9rCpIljaP5GADR

OBS Studio Crash Log URL

No response

Expected Behavior

Browser sources should render both in the preview window and in the properties tab, and this behavior should be retained through reboot.

Current Behavior

Upon reboot, browser sources are still present in the sources list, but do not render. This is because CEF fails to initialize.

Image
Steps to Reproduce
  1. Install and launch OBS Studio 32.0.4.
  2. Create a browser source, then close OBS and restart your system.
  3. Launch OBS. CEF should now fail to initialize, causing the browser source not to render.
Anything else we should know?

Once 32.0.4 has been installed, browser sources appear to permanently break even when rolling back to older updates. OBS must be fully uninstalled and 32.0.2 must be installed in order to prevent the issue.

My best guess is that this has something to do with the changes to shutdown logic in 32.0.3, but this is speculative.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked OBS log and reproducing the browser-source failure on OpenSUSE after a reboot with OBS 32.0.4. Trace where CEF initialization is handled during startup and shutdown; done means browser sources render in both the preview and properties tab after reboot, without breaking after rollback.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.