Package: obs-studio
Version: 30.0.2+dfsg~
Followup-For: Bug #1051418
Unfortunately I can confirm the bug at question with the (not yet uploaded)
obs-studio 30.0.2.
the OBS shipped by flatpak does not have this problem, so it appears to be
Debian packaging problem.
I'm seeing the same bug in the latest Debian testing updated this morning.
Specifically, if I have the following github page open in my browser clicking
the xcomposite window source cases a seg fault as reported.
https://github.com/pjreddie/darknet/issues/553
This results in a window name ofÂ
Same story on xorg.
-- System Information:
Debian Release: trixie/sid
APT prefers oldoldstable-updates
APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable'), (500,
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-2-amd64 (SMP w/12 CPU threads;
Package: obs-studio
Version: 29.1.3+dfsg-2
Severity: important
Hi,
after upgrading from 29.0.2+dfsg-1+b1 to 29.1.3+dfsg-2 (bookworm to trixie) I
couldn't work with the xcomposite window source anymore. In fact, a
pre-existing scene that was set up to use that source makes obs segfault
4 matches
Mail list logo
