Screensharing apps error

Support System Updates
1

When I use Signal or Discord to share my screen - all I ever needed was to choose which window to share.

Now, as of our beloved December system update - a new/additional, never-before-seen window pops up which says:

‘KDE portal integration failed to create pipewire context’

and I am not able to share my screen at all. Having read a few other threads my first lead:

pipewire-pulse

needs to be installed?

OK, now I know it is most likely because I am no longer on X11, it got switched to Wayland…

SO now I have to learn how to live in this environment.

Could switch back:

sudo pacman -S plasma-x11-session

But eventually x11 will be dropped so it isn’t a solution really.

Copy/ past is not working today on my laptop so I need the pastebin for now.

inxi -zv8:

pactl info:

2

PipeWire is audio not graphics. The relation to Wayland may only be that it is also the new stuff. Installing PipeWire properly could solve the issue. There is a meta package to help to do so: manjaro-pipewire. For Plasma check for kpipewire too.

3

Already installed in my system.

Proceed with:

manjaro-pipewire

?

4

Archwiki - PipeWire
PipeWire is a new low-level multimedia framework. It aims to offer capture and playback for both audio and video

PipeWire documentation - Overview
PipeWire is a graph-based processing framework, that focuses on handling multimedia data (audio, video and MIDI mainly).

signal-desktop has optional dependency xdg-desktop-portal for screen-sharing with Wayland

$ pamac info signal-desktop
Name                  : signal-desktop
Version               : 7.82.0-1
Description           : Signal Private Messenger for Linux
URL                   : https://signal.org

Optional Dependencies : xdg-desktop-portal: Screensharing with Wayland
 
Packager              : Christian Heusel <gromit@archlinux.org>
Build Date            : Thu 11 Dec 2025 12:56:31 GMT
2 Likes
5

Already in my system… what am I doing wrong, then?

6

Thanks for the correction - i should read the links i post. All i had in the back of my mind was that PipeWire replaced PulseAudio as sound server…

According to your inxi log you are still using PulseAudio, and i think this is the reason for getting:

Installing manjaro-pipewire should change to PipeWire.

1 Like
7

onto it…

which dependency will be crucial here to choose?

easyeffects - nah

jack support?

v4l2 interceptor?

x11 bell?

zeroconf support?

reali-time privileges?

8

Archwiki - PipeWire - Troubleshooting - Video - OBS (etc.) display nothing, even if they ask for a window/screen

If you are sure that you have xdg-desktop-portal installed as well as either xdg-desktop-portal-gtk or xdg-desktop-portal-kde, check the running state of the daemons.

Replacing audio servers is not necessary to resolve a screen sharing issue

ArchWiki - Wireplumber - Disable audio stack integration

If you do not want PipeWire/Wireplumber to take over control of your audio devices because you are opting for a different audio solution (e.g. PulseAudio/JACK/ALSA) but still want it to be available for screen sharing/video purposes you can make use of the wireplumber@.service template unit to enable a different set of default profiles. Wireplumber ships with a profile configuration that enables only the video parts and disables audio integration (including Bluetooth audio) by enabling the video-only template user unit.

Disable wireplumber.service user unit and enable wireplumber@video-only.service user unit.

inxi shows system has pipewire installed with pipewire-media-session

  Server-2: PipeWire v: 1.4.9 status: off with: pipewire-media-session
    status: off tools: pw-cat,pw-cli

ArchWiki - PipeWire - Session Manager

Like JACK, PipeWire implements no connection logic internally. The burden of watching for new streams and connecting them to the appropriate output device or application is left to an external component known as a session manager.

WirePlumber

WirePlumber is the recommended session manager. It is based on a modular design, with Lua plugins that implement the actual management functionality.

PipeWire Media Session

pipewire-media-session is deprecated and no longer recommended. It was mostly implemented for testing and as an example for building new session managers.

9

I am not sure i can handle the tast without going back to X11…

If I stop from playing with

manjaro-pipewire

then comes:

WirePlumber

right?

and it seems complicated, never managed to understand how audio works on Linux

10

none of the optional dependencies are crucial

1 Like
11

‘KDE portal integration failed to create pipewire context’ typically occur when the xdg-desktop-portal-kde backend failing to connect to PipeWire.

Ensure Required Packages Are Installed . Install PipeWire and KDE portal backend

sudo pacman -Syu pipewire wireplumber pipewire-pulse xdg-desktop-portal-kde

For Flatpak apps, also install xdg-desktop-portal-gtk as a fallback.

Enable and Start PipeWire Services. PipeWire runs as user services

systemctl --user --now enable pipewire pipewire-pulse wireplumber

Restart portal services

systemctl --user restart xdg-desktop-portal xdg-desktop-portal-kde

Reboot

Check status

systemctl --user status pipewire pipewire-pulse wireplumber

systemctl --user status xdg-desktop-portal xdg-desktop-portal-kde

If everything is active, check the screen sharing

1 Like