Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/6964e172-93a0-8013-9baf-b12d96b905a2
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Assistant: Good — that tells us something important. === Good — that tells us something important. If Step 3 (forcing XWayland) didn’t fix it but Discord Web still works, then this is not a simple Wayland toggle issue anymore. At this point, one of these is true: # Your native Discord package is broken with PipeWire # xdg-desktop-portal is misbehaving on Plasma # You’re using the wrong Discord build (native vs flatpak mismatch) # KDE’s screen portal is stuck (very common) We’ll go surgical. Follow exactly, in order. ==== Run: ==== <syntaxhighlight lang="bash">which discord </syntaxhighlight> And: <syntaxhighlight lang="bash">pacman -Qs discord </syntaxhighlight> Tell me: * Is it discord, discord-canary, or flatpak? ⚠️ Don’t skip this — the fix depends on it. ==== This fixes 70% of Plasma streaming bugs. ==== Close Discord. Then run: <syntaxhighlight lang="bash">systemctl --user stop xdg-desktop-portal systemctl --user stop xdg-desktop-portal-kde systemctl --user stop pipewire systemctl --user stop wireplumber </syntaxhighlight> Wait 10 seconds. Now start them 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> Now launch Discord from terminal: <syntaxhighlight lang="bash">DISCORD_USE_WAYLAND=0 discord </syntaxhighlight> Test streaming a window, not full screen. ==== Native Arch Discord is notorious for this exact issue. ==== ===== <syntaxhighlight lang="bash">sudo pacman -S flatpak ===== </syntaxhighlight> ===== <syntaxhighlight lang="bash">flatpak install flathub com.discordapp.Discord ===== </syntaxhighlight> ===== <syntaxhighlight lang="bash">flatpak run com.discordapp.Discord ===== </syntaxhighlight> ➡️ Try streaming. Why this works: Flatpak Discord ships newer Electron + correct PipeWire permissions. ==== To avoid conflicts: ==== <syntaxhighlight lang="bash">sudo pacman -R discord </syntaxhighlight> Keep Flatpak only. ==== Open: ==== <syntaxhighlight>System Settings → Privacy & Security → Screen Recording </syntaxhighlight> Make sure: * Discord is allowed * No global restriction is enabled ==== Run: ==== <syntaxhighlight lang="bash">journalctl --user -xe | grep -E "portal|pipewire|discord" </syntaxhighlight> If you see errors like: * Failed to create screencast session * No such interface org.freedesktop.portal.ScreenCast 👉 paste them here. ==== - Discord native on Arch/Wayland is unreliable ==== * Discord Web works because Chrome is better * Flatpak Discord is the real fix 9/10 times * CachyOS + Plasma is NOT the problem ===== 1. Output of which discord ===== # Whether Flatpak Discord works or not I’ll finish locking this down after that.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)