obs-studio
obs-studio copied to clipboard
obsproject
OBS starts with the new "safe mode" prompt after reboot (Linux)
Operating System Info
Other
Other OS
NixOS
OBS Studio Version
30.0.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/d7YEvfIg4gg030Rm
OBS Studio Crash Log URL
No response
Expected Behavior
Send SIGTERM to obs and it exits cleanly. Not showing a popup when starting it again
Current Behavior
Send SIGTERM to obs and it does not exit cleanly. Popup for safe mode shows.
Steps to Reproduce
- Start obs
- pgrep obs
- kill
Anything else we should know?
Is the lInux version of issue #9877
SIGTERM is supposed to cause a clean exit. Proper signal handling is required.
(Possible cross-plattform solution by using Qt libraries?)
Same issue. If I start OBS and the close on next run OBS start with safe mode prompt.
info: ==== Shutting down ==================================================
info: pulse-input: Stopped recording from 'my_sink.monitor'
info: pulse-input: Got 1020 packets with 1224000 frames
info: [obs-scripting]: Unloaded lua script: countdown.lua
info: All scene data cleared
info: ------------------------------------------------
info: [obs-websocket] [obs_module_unload] Shutting down...
error: Tried to call obs_frontend_remove_event_callback with no callbacks!
info: [obs-websocket] [obs_module_unload] Finished shutting down.
Segmentation fault (core dumped)
Same issue. If I start OBS and the close on next run OBS start with safe mode prompt.
info: ==== Shutting down ================================================== info: pulse-input: Stopped recording from 'my_sink.monitor' info: pulse-input: Got 1020 packets with 1224000 frames info: [obs-scripting]: Unloaded lua script: countdown.lua info: All scene data cleared info: ------------------------------------------------ info: [obs-websocket] [obs_module_unload] Shutting down... error: Tried to call obs_frontend_remove_event_callback with no callbacks! info: [obs-websocket] [obs_module_unload] Finished shutting down. Segmentation fault (core dumped)
If the previous OBS session ends in a segfault, then that is an unsafe shutdown and OBS will prompt you to start in Safe Mode when you next launch it.
As this Issue describes, if you use SIGTERM to terminate the OBS process, that is also currently regarding as an unsafe shutdown as we do not handle that signal.
I used the automatic configuration wizard = No segmentation fault anymore.
I enabled the chat and stream information docks = Segmentation faults are back.
I think it's not the same issue than Mikilio's because he doesn't have any segmentation fault.
If I close the chat and stream information docks = No segmentation fault anymore.
I've been having a similar issue on a brand new computer and OBS install. I wanted to confirm what @luc2 posted:
Here's my startup info from a terminal:
warning: [Safe Mode] User elected to launch normally.
info: Using EGL/X11
info: CPU Name: Intel(R) Celeron(R) N5105 @ 2.00GHz
info: CPU Speed: 2787.340MHz
info: Physical Cores: 4, Logical Cores: 4
info: Physical Memory: 15743MB Total, 14164MB Free
info: Kernel Version: Linux 6.6.19-1-MANJARO
info: Distribution: "Manjaro Linux" Unknown
info: Desktop Environment: XFCE (xfce)
info: Session Type: x11
info: Window System: X11.0, Vendor: The X.Org Foundation, Version: 1.21.1
info: Qt Version: 6.6.2 (runtime), 6.6.2 (compiled)
info: Portable mode: false
info: OBS 30.1.0 (linux)
and here's the output when I try to close OBS with File > Quit:
error: Tried to call obs_frontend_remove_event_callback with no callbacks!
info: [obs-websocket] [obs_module_unload] Shutting down...
error: Tried to call obs_frontend_remove_event_callback with no callbacks!
info: [obs-websocket] [obs_module_unload] Finished shutting down.
Segmentation fault (core dumped)
But, if I CLOSE the TWITCH CHAT DOCK before I quit OBS, then everything closes normally, no seg fault, and no warning when I start OBS again.
But, if I CLOSE the TWITCH CHAT DOCK before I quit OBS, then everything closes normally, no seg fault, and no warning when I start OBS again.
As previously mentioned:
If the previous OBS session ends in a segfault, then that is an unsafe shutdown and OBS will prompt you to start in Safe Mode when you next launch it.
Your case is not the same as the OP. Someone needs to figure out why browser panels/docks are crashing on Linux to fix your issue. It is not the same as sending a SIGTERM to OBS.
If I close the chat and stream information docks = No segmentation fault anymore.
this work around works for me too. Waiting for build with correction