Your message dated Sat, 24 Oct 2026 19:01:02 +0200
with message-id <[email protected]>
and subject line Re: Bug#1149576: obs-studio: Segfaults at startup when running 
under Wayland
has caused the Debian Bug report #1149576,
regarding obs-studio: Segfaults at startup when running under Wayland
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1149576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1149576
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: obs-studio
Version: 32.2.2+ds-1+b1
Severity: important
X-Debbugs-Cc: [email protected]

Upon starting obs-studio, I get the following messages spewed to the
terminal, and obs immediately crashes:

    $ obs
    debug: Attempted path: /usr/bin/../share/obs/obs-studio/locale/en-US.ini
    debug: Attempted path: /usr/bin/../share/obs/obs-studio/locale.ini
    debug: Attempted path: /usr/bin/../share/obs/obs-studio/themes
    debug: Attempted path: /usr/bin/../share/obs/obs-studio/themes/
    warning: Get on org.freedesktop.portal.Settings returned an invalid reply
    warning: Native interface revision mismatch (requested 1 / available 2) for 
interface QWaylandApplication
    Segmentation fault         obs

My environment includes QT_QPA_PLATFORM=wayland; changing it to
QT_QPA_PLATFORM=xcb allows obs-studio to run successfully.

I use obs at least twice a week. My systems are reasonably well updated, so
I think the culprit _might_ be qt6-wayland, as it was uploaded to unstable
on September 20. I am filing the bug with obs-studio as I haven't found
this behavior with any other tool, and the changelog for 6.11.2-1 includes
the mention it had an ABI bump; hopefully, an obs-studio rebuild will fix
the issue (“requested 1 / available 2”).

Thank you very much,

 — Gunnar.

-- System Information:
Debian Release: forky/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 7.1.13+deb14-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages obs-studio depends on:
ii  libavcodec63               7:9.0.2-1
ii  libavdevice63              7:9.0.2-1
ii  libavformat63              7:9.0.2-1
ii  libavutil61                7:9.0.2-1
ii  libc6                      2.43-6
ii  libcurl4-gnutls            8.23.0~rc2-1
ii  libegl1                    1.7.0-3+b1
ii  libfontconfig1             2.17.1-5
ii  libfreetype6               2.14.3+dfsg-2
ii  libgcc-s1                  16.2.0-3
ii  libglx0                    1.7.0-3+b1
ii  libjansson4                2.15.1-1
ii  libluajit-5.1-2            2.1.0+openresty20251030-1+b2
ii  libmbedcrypto16            3.6.7-3
ii  libmbedtls21               3.6.7-3
ii  libmbedx509-7              3.6.7-3
ii  libobs0t64                 32.2.2+ds-1+b1
ii  libopengl0                 1.7.0-3+b1
ii  libpci3                    1:3.15.0-2
ii  libpulse0                  17.0+dfsg1-3
ii  libpython3.14              3.14.7-5
ii  libqrcodegencpp1           1.8.0-1.2+b3
ii  libqt6core6t64             6.11.2+dfsg-5
ii  libqt6dbus6                6.11.2+dfsg-5
ii  libqt6gui6                 6.11.2+dfsg-5
ii  libqt6network6             6.11.2+dfsg-5
ii  libqt6svg6                 6.11.2-2
ii  libqt6widgets6             6.11.2+dfsg-5
ii  libqt6xml6                 6.11.2+dfsg-5
ii  librist4                   0.2.20+dfsg-1
ii  libspeexdsp1               1.2.1-4
ii  libsrt1.5-openssl          1.5.7-1
ii  libstdc++6                 16.2.0-3
ii  libswscale10               7:9.0.2-1
ii  libudev1                   262-1
ii  libv4l-0t64                1.32.0-5
ii  libva-drm2                 2.24.1-2
ii  libva2                     2.24.1-2
ii  libvpl2                    1:2.17.0-1
ii  libx11-6                   2:1.8.13-1
ii  libx264-165                2:0.165.3223+git20250910.0480cb0-1+b1
ii  libxcb-composite0          1.17.0-2+b2
ii  libxcb-randr0              1.17.0-2+b2
ii  libxcb-shm0                1.17.0-2+b2
ii  libxcb-xfixes0             1.17.0-2+b2
ii  libxcb-xinerama0           1.17.0-2+b2
ii  libxcb1                    1.17.0-2+b2
ii  obs-studio-common          32.2.2+ds-1
ii  python3                    3.14.7-3
ii  python3.14                 3.14.7-5
ii  qt6-image-formats-plugins  6.11.2-2
ii  qt6-svg-plugins            6.11.2-2
ii  qt6-wayland                6.11.2-2

Versions of packages obs-studio recommends:
ii  obs-plugins  32.2.2+ds-1+b1

Versions of packages obs-studio suggests:
ii  pkexec             127-3
ii  polkitd            127-3
ii  v4l2loopback-dkms  0.15.4-2

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi

On 2026-10-10 08:29:13 +0200, Thomas Glanzmann wrote:
> Hello,
> this bug is caused by:
> 
> - /usr/bin/obs ︎was compiled against Qt 6.10.2 ( ︎qt_version_tag ︎ symbol 
> version  ︎Qt_6.10 ︎, compiled version string  ︎6.10.2 ︎).
> - The system now provides Qt 6.11.2 at runtime.
> - The OBS binary calls private Qt Wayland interfaces via  
> ︎QWaylandApplication ︎. Between 6.10 and 6.11 Qt bumped the native interface 
> revision from 1 to 2, so the request gets a  ︎NULL ︎ interface pointer, 
> dereferenced later → SIGSEGV at address NULL.         
> 
> Fix: Recompile it with current qt version in Debian testing. I tested
> this locally and it works.

This issue was caused by
https://github.com/qt/qtbase/commit/d7b1910575a87d06ec6af8257bd85d3e4ac6ac91.
obs-studio was rebuilt and libqt6gui6 will gain a Breaks as this change
is outside of what we can typically handle via our machinery. The change
influences a templated function call
(nativeInterface<QNativeInterface::QWaylandApplication>()) that does not
appear as symbol coming from Qt 6.

Cheers
-- 
Sebastian Ramacher

--- End Message ---

Reply via email to