obsproject / obsproject/obs-studio
Flatpak crashing: obs killed by SIGSEGV
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
Fedora release 43
OBS Studio Version
Other
OBS Studio Version (Other)
32.0.4
OBS Studio Log URL
https://obsproject.com/logs/YtTOl9qOoSgvXJN9
OBS Studio Crash Log URL
No response
Expected Behavior
OBS flatpak should exit cleanly.
Current Behavior
OBS flatpak crashing on Fedora 43 KDE, has the same issue on Fedora 42 Gnome.
Works fine for most recording sessions, rarely and intermittently crashes when recording.
Consistantly crashes when existing the application and OS generates a crash report.
Steps to Reproduce
- Launch OBS flatpak
- Record or have OBS up for a couple min.
- Exit application
- OS notices OBS crash...
Anything else we should know?
Likely crash reason: Jump to an invalid address
Exploitable rating (0-9 scale): 6
OS crash report
PID: 12268 (obs)<br>
UID: 1000 (user)<br>
GID: 1000 (user)<br>
Signal: 11 (SEGV)<br>
Timestamp: Wed 2025-12-24 00:33:32 MST (10min ago)<br>
Command Line: obs<br>
Executable: /app/bin/obs<br>
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-flatpak-com.obsproject.Studio-3836801433.scope<br>
Unit: user@1000.service<br>
User Unit: app-flatpak-com.obsproject.Studio-3836801433.scope<br>
Slice: user-1000.slice<br>
Owner UID: 1000 (user)<br>
Boot ID: 683d72c176e94b678b4b29c442e619c2<br>
Machine ID: 07a981d03c4e48938947478beb7cad7b<br>
Hostname: ApexFedora.lan<br>
Storage: /var/lib/systemd/coredump/core.obs.1000.683d72c176e94b678b4b29c442e619c2.12268.1766561612000000.zst (present)<br>
Size on Disk: 13.3M<br>
Message: Process 12268 (obs) of user 1000 dumped core.<br><br>
Stack trace of thread 2:
#0 0x00007f4aac366a04 n/a (/usr/lib/x86_64-linux-gnu/libKF6StatusNotifierItem.so.6.18.0 + 0x1da04)
#1 0x00007f4aac366d15 n/a (/usr/lib/x86_64-linux-gnu/libKF6StatusNotifierItem.so.6.18.0 + 0x1dd15)
#2 0x00007f4aac7a171f n/a (/usr/lib/plugins/platformthemes/KDEPlasmaPlatformTheme6.so + 0x4671f)
#3 0x00007f4ab4ca1a57 n/a (/usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6.8.3 + 0x2a1a57)
#4 0x00007f4ab4ca1a85 n/a (/usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6.8.3 + 0x2a1a85)
#5 0x000055fe9d050a70 n/a (/app/bin/obs + 0x2c0a70)
#6 0x000055fe9d051da5 n/a (/app/bin/obs + 0x2c1da5)
#7 0x00007f4ab39f64ce n/a (/usr/lib/x86_64-linux-gnu/libQt6Core.so.6.8.3 + 0x1f64ce)
#8 0x00007f4ab4ba04f8 n/a (/usr/lib/x86_64-linux-gnu/libQt6Widgets.so.6.8.3 + 0x1a04f8)
#9 0x00007f4ab399e050 n/a (/usr/lib/x86_64-linux-gnu/libQt6Core.so.6.8.3 + 0x19e050)
#10 0x00007f4ab39a1a12 n/a (/usr/lib/x86_64-linux-gnu/libQt6Core.so.6.8.3 + 0x1a1a12)
#11 0x00007f4ab3cb3b5f n/a (/usr/lib/x86_64-linux-gnu/libQt6Core.so.6.8.3 + 0x4b3b5f)
#12 0x00007f4ab0bc93d6 n/a (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.8200.5 + 0x633d6)
#13 0x00007f4ab0c2a047 n/a (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.8200.5 + 0xc4047)
#14 0x00007f4ab0bc8863 n/a (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.8200.5 + 0x62863)
#15 0x00007f4ab3cb32b3 n/a (/usr/lib/x86_64-linux-gnu/libQt6Core.so.6.8.3 + 0x4b32b3)
#16 0x00007f4ab39ab453 n/a (/usr/lib/x86_64-linux-gnu/libQt6Core.so.6.8.3 + 0x1ab453)
#17 0x00007f4ab39a6a2e n/a (/usr/lib/x86_64-linux-gnu/libQt6Core.so.6.8.3 + 0x1a6a2e)
#18 0x000055fe9ce73536 n/a (/app/bin/obs + 0xe3536)
#19 0x00007f4ab322b3c8 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a3c8)
#20 0x00007f4ab322b48b n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2a48b)
#21 0x000055fe9ce74a45 n/a (/app/bin/obs + 0xe4a45)
ELF object binary architecture: AMD x86-64
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked OBS log and the attached systemd coredump stack, focusing on the launch, recording, and exit sequence on Fedora KDE and GNOME. Done means reproducing the reported scenario without a SIGSEGV or crash report when OBS exits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, fedora, linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100