Unable to Share Screen via PipeWire in OBS Studio

[Timo Witte]

Hello,

please pull in this change:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2322

This is the relevant bug in the mutter repo:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2155

as it blocks OBS / Telegram from receiving screen sharing on AMD GPUs.

Mär 29 23:32:24 egal-12 gnome-shell[3219]: setup_framebuffers: assertion 'width > 0' failed
Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: [pipewire] desktop selected, setting up screencast
Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: [pipewire] server version: 0.3.48
Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: [pipewire] library version: 0.3.48
Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: [pipewire] header version: 0.3.48
Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: [pipewire] created stream 0x564c4e1f7480
Mär 29 23:32:26 egal-12 com.obsproject.Studio.desktop[55756]: info: [pipewire] playing stream…
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: No supported PipeWire stream buffer data type could be negotiated
Mär 29 23:32:26 egal-12 gnome-shell[3219]: pipewire remote error: id:0 connection error
Mär 29 23:32:26 egal-12 pipewire[2993]: spa.v4l2: wanted XR24 2560x1440, got YUYV 2304x1536
Mär 29 23:32:26 egal-12 pipewire[2993]: pw.link: tried to set output format:
Mär 29 23:32:26 egal-12 pipewire[2993]: default: Object: size 320, type Spa:Pod:Object:Param:Format (262147), id Spa:Enum:ParamId:Format (4)
Mär 29 23:32:26 egal-12 pipewire[2993]: default: Prop: key Spa:Pod:Object:Param:Format:mediaType (1), flags 00000000
Mär 29 23:32:26 egal-12 pipewire[2993]: default: Choice: type Spa:Enum:Choice:None, flags 00000000 20 4

[Timo Witte (spacefish)]

Just tried it out locally and rebuild the mutter package, worked like a charm.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "change which fixed the issue taken from upstream" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Daniel van Vugt (vanvugt)]

That fix is in mutter version "42.rc", which is already in the proposed pocket as "42.0-1ubuntu1"

[Marco Trevisan (Treviño) (3v1n0)]

This has been fixed on previous upload.