Editing Openai/6964e172-93a0-8013-9baf-b12d96b905a2 (section)

=== Assistant: Alright. ===
Alright. If even Flatpak Discord doesn’t stream, then we’re past “Discord being Discord” and into a broken Wayland screencast stack on KDE.

I’m going to be very direct and very precise now.

At this point, there are only two real possibilities left:

==== Your KDE Wayland ScreenCast portal is broken or unreachable. ====

That’s why:
* Discord native ❌
* Discord Flatpak ❌
* Discord Web (Chrome) ✅ (Chrome uses a different capture path)

This is a known KDE Plasma Wayland failure mode.

==== Run this exact command: ====

<syntaxhighlight lang="bash">qdbus org.freedesktop.portal.Desktop /org/freedesktop/portal/desktop org.freedesktop.portal.ScreenCast

</syntaxhighlight>

===== You’ll see method info / no error. =====

===== You’ll see: =====

<syntaxhighlight>Service 'org.freedesktop.portal.Desktop' does not exist

</syntaxhighlight>

or

<syntaxhighlight>No such interface org.freedesktop.portal.ScreenCast

</syntaxhighlight>

➡️ Tell me exactly what it outputs.

==== Sometimes Plasma silently falls back to the wrong portal. ====

Run:

<syntaxhighlight lang="bash">echo $XDG_CURRENT_DESKTOP

</syntaxhighlight>

If it says KDE, continue.

Now run:

<syntaxhighlight lang="bash">ls /usr/share/xdg-desktop-portal/portals/

</syntaxhighlight>

You MUST see:

<syntaxhighlight>kde.portal

</syntaxhighlight>

If you don’t — streaming will NEVER work.

==== ⚠️ This does not reboot your system. ====

<syntaxhighlight lang="bash">systemctl --user stop xdg-desktop-portal
systemctl --user stop xdg-desktop-portal-kde
systemctl --user stop pipewire
systemctl --user stop wireplumber

rm -rf ~/.cache/xdg-desktop-portal
rm -rf ~/.config/xdg-desktop-portal

</syntaxhighlight>

Now start everything again:

<syntaxhighlight lang="bash">systemctl --user start pipewire
systemctl --user start wireplumber
systemctl --user start xdg-desktop-portal
systemctl --user start xdg-desktop-portal-kde

</syntaxhighlight>

Wait 15 seconds, then try Discord again.

==== I won’t sugarcoat this: ====

===== Even when everything is “correct”. =====

===== Use an X11 Plasma session. =====

==== At the login screen: ====
# Click Session
# Choose Plasma (X11) — NOT Wayland
# Log in
# Launch Discord (Flatpak or native)
# Stream → works instantly

No flags. No hacks. No pain.

This is what many KDE users quietly do.

==== - Your hardware is fine ====
* PipeWire is installed
* Web Discord works
* Multiple Discord builds failed
* This isolates to Wayland screencast portal

==== - 🟡 Want Wayland purity → accept broken Discord ====
* 🟢 Want working streaming → use Plasma X11
* 🔵 Want perfect Wayland → GNOME (handles portals better)

===== 1. Output of the qdbus command =====
# Whether you’re willing to switch to Plasma X11

I’ll guide you cleanly either way.