-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Obs browser crashes OBS Interface #11812
Comments
Well. No jack issues like last time I'm closing this issue, not because the issues fixed but because i no longer care about fixing it as other versions seem to work better. if @tytan652 reads this, i wish you best of luck with trying to fix it - i wouldnt be surprised if it wasnt broken on your end -, don't hesitate to reach out, but given the instability and the unanswered questions people have asked on the AUR, i doubt you will. If anyone comes accross this and wants to fix it, feel free to reopen it. |
I also have this issue, and it exists both in the default arch repo and the obs-studio-browser AUR. |
Reopening due to other people having this issue To reiterate: issue is present on AUR releases It is not present on Flatpak current release. |
Neither of the three Arch releases listed (default, tytan652, obs-studio-browser) are official. The only official OBS release for Arch is the Flatpak, which you say works fine. |
Operating System Info
Other
Other OS
Arch Linux
OBS Studio Version
31.0.1
OBS Studio Version (Other)
31.0.1-tytan652-1
OBS Studio Log URL
https://obsproject.com/logs/Geww1bVmtn559uKJ
OBS Studio Crash Log URL
No response
Expected Behavior
The interface continues to run after the creation of browser sources is attempted or obs is launched from a profile with a browser source is launched.
Current Behavior
When launching in my original saved profile, OBS will launch but the interface will never initialize - the program will essentially be running in the background. From what i see in the logs, it doesnt appear to be reporting any obvious issues.
when Launching in a fresh new profile, OBS launches correctly, however, upon the attempted creation of a browser source, the interface will freeze and the app will hang... the new source doesnt even make it to the log.
Steps to Reproduce
...?
profit!
Anything else we should know?
Any version ive installed from v31 and above, seems to have this problem.
The last version i ran that worked was 30.2.3-tytan652
Im kinda in a rut here as i have done a clean build and no longer have all my old packages of obs cached up. Also my python got upgraded in one of my last upgrades and as a result some of my other software broke when i last downgraded. As a result i will not be avaliable to downgrade again.
Flatpak has never agreed with my setup for various reasons.
FULL VERSION INFORMATION/ OS DATA
DE: Hyprland, wayland
Distro: Arch Linux
Kernel: Linux 6.12.10-arch1-1
QT: 6.8.1 (runtime & compiled)
CPU: Intel Core I5-4690
GPU: NVIDIA GeForce GTX 1070
GPU Driver: Propietary 565.77, shader language 3.30
VAAPI API 1.22
VLC 3.0.21 Vetinari (from AUR vlc-luajit)
current issue version
obs-studio:
obs-browser: 2.24.4
cef: 127.0.6533.100 (from obsproject downloads - cef_binary_6533)
python: 3.13.1
last known working version
obs-studio: 30.2.3-tytan652-3
obs-browser: 2.23.6
cef: 103.0.5060.134 (from AUR - cef-minimal-
obs-bin)
python: 3.12.7-1
Image of moment of crash, after resizing windows to show the interface has indeed halted. log in terminal to the right

Log file of last known working configuration, loading my original profile, i couldnt upload with normal mechanism due to the issue and also due to the wiping of profiles:
2025-02-01 15-15-34.txt
And lastly, here is a log file of when i tried to load my profile with the issue version - as you can see.. it doesn't even get to loading my profile properly, all scene data was never loaded.
2025-02-01 20-58-39.txt
The text was updated successfully, but these errors were encountered: