huzi.pk logohuzi.pk

Fedora: Wayland + Some Electron Apps Have No Audio – Unlocking the Silent Flatpak

tech

Fedora: Wayland + Some Electron Apps Have No Audio – Unlocking the Silent Flatpak

There's a special kind of silence that speaks volumes. It's not the peaceful quiet of a working machine, but the hollow absence where sound should be. Your music plays in Firefox, your system chimes are crisp, but you open Discord, Slack, or Element to join a call and… nothing. The audio level dances, your friends see you talking, but your world is mute. You've just met a classic Fedora-on-Wayland puzzle: the silent Electron app.

I've sat in that silent room, frustrated, clicking every volume slider to no avail. The issue, I discovered, isn't with your hardware or even a broken app. It's a permissions puzzle at the intersection of three modern Linux technologies: Wayland, PipeWire, and Flatpak. The good news? Solving it is about learning to speak the language of portals and sandboxes.

Let's get your conversations flowing again.

Understanding Why This Happens: The Three Walls

Before we fix it, let's understand the landscape. Modern Linux desktop security has built elegant walls, but sometimes they block the doors we need. If you understand the architecture, you'll be able to diagnose and fix similar issues in the future without hunting through forums.

  • Wayland: The new display protocol. It says, "Apps cannot spy on each other or grab input/output devices without explicit permission." Unlike X11, where any application could listen to any other's input, Wayland enforces strict isolation.
  • Flatpak: The universal packaging format. It says, "Apps run in a sandbox, isolated from the system for your safety." By default, this sandbox has no audio devices. The sandbox is defined by the app's manifest, and the permissions granted are the absolute minimum needed.
  • PipeWire: The modern audio/video server. It says, "I will manage all multimedia streams and provide a controlled interface." PipeWire replaced PulseAudio starting with Fedora 34, and it's the unified multimedia framework for both audio and video.

The xdg-desktop-portal is the diplomat that negotiates between these three. When an Electron app on Wayland (inside a Flatpak sandbox) wants audio, it must ask the portal, which asks you (or your stored permissions), then tells PipeWire to grant access. If any link in this chain is broken—a missing permission, a crashed portal, or an app not speaking the right Wayland dialect—you get silence.

The reason this disproportionately affects Electron apps is that they bundle their own Chromium runtime, which doesn't always integrate properly with the portal system. Native GTK or Qt apps follow the portal protocol naturally; Electron apps need extra configuration.

The Quick Fixes: Restore Audio in Minutes

Try these steps in order. One of them will likely be your key. I've ordered them from the most common fix to the most nuclear option.

Step 1: The Universal First Step – Grant Flatpak Permissions

If your silent app is a Flatpak (most are, if installed from Flathub or GNOME Software on Fedora), this is the most common fix. The app's sandbox simply doesn't have audio access.

Using GNOME Software (GUI method):

  1. Open GNOME Software.
  2. Go to the Installed tab.
  3. Find your app (e.g., Discord).
  4. Click Permissions.
  5. Ensure "Audio" and "Video" are toggled ON.

Using the terminal (recommended for precision):

# List current permissions for all Flatpak apps
flatpak permission-list

# Remove any conflicting old audio permission and reset it
flatpak permission-remove audio 

# Grant audio permission explicitly
flatpak permission-set audio  yes

Replace <app-id> with something like com.discordapp.Discord. You can find the app ID by running flatpak list --app.

For microphone access specifically:

flatpak permission-set devices  microphone yes

Alternative: Override permissions directly:

# Grant filesystem and device access for audio
flatpak override --socket=pulseaudio com.discordapp.Discord

The --socket=pulseaudio flag gives the Flatpak access to the PulseAudio/PipeWire socket, which is what most audio applications need.

Step 2: Check the PipeWire Portal – The Gatekeeper

Wayland apps need permission via a "portal" to access devices like your microphone and speakers. If the portal service crashes or isn't running, all permission requests silently fail.

  1. Open a terminal and check if the critical portal is running:
    systemctl --user status xdg-desktop-portal
  2. If it's inactive, enable and start it:
    systemctl --user enable --now xdg-desktop-portal
  3. Also check the GNOME-specific portal (Fedora uses GNOME by default):
    systemctl --user status xdg-desktop-portal-gnome

Often, a full restart of the portal system helps. This is the "turn it off and on again" of the Linux audio world:

systemctl --user restart pipewire pipewire-pulse xdg-desktop-portal xdg-desktop-portal-gnome

Important: After restarting portals, you must log out and log back in (or restart your session) for the changes to fully propagate to running applications. A simple app restart isn't always enough.

Step 3: Verify the App is Using Wayland Correctly

Electron apps can sometimes get stuck in an X11 compatibility mode (XWayland), which can cause audio routing issues. Launch them from the terminal with a Wayland flag to force the issue:

# For Discord
discord --enable-features=UseOzonePlatform --ozone-platform=wayland

If audio works with this flag, you can make it permanent by editing the app's desktop entry (usually in ~/.local/share/applications/):

# Copy the system desktop file to your local applications directory
cp /var/lib/flatpak/exports/share/applications/com.discordapp.Discord.desktop ~/.local/share/applications/

# Edit the Exec line to include the flags
nano ~/.local/share/applications/com.discordapp.Discord.desktop

Modify the Exec= line to:

Exec=/usr/bin/flatpak run --socket=pulseaudio --command=discord com.discordapp.Discord --enable-features=UseOzonePlatform --ozone-platform=wayland

For Fedora 41+ with Wayland by default: Most Electron apps should auto-detect Wayland. If you're still having issues, you may need to set the environment variable:

export ELECTRON_OZONE_PLATFORM_HINT=auto

Add this to your ~/.bashrc or ~/.zshrc for persistence.

Step 4: The Nuclear Option – Reinstall the Native Package

If the Flatpak version is stubborn, abandon the sandbox. Remove the Flatpak and install the native .rpm version. Native packages have direct system access and bypass these portal issues entirely.

  1. Remove the Flatpak:
    flatpak uninstall --delete-data
  2. Enable the RPM Fusion repository if you haven't:
    sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
  3. Install the native version. For apps like Discord:
    sudo dnf install discord
  4. For Slack:
    sudo dnf install slack

Native packages bypass Flatpak's sandbox entirely, so they have direct access to PipeWire and don't need portal permissions. The trade-off is slightly less security isolation, but for trusted communication apps, this is usually acceptable.

Step 5: Check PipeWire WirePlumber Configuration

Sometimes the issue isn't permissions but WirePlumber (PipeWire's session manager) not properly routing audio for specific app types.

# Check if WirePlumber is running
systemctl --user status wireplumber

# Restart it
systemctl --user restart wireplumber

# Check audio routing
wpctl status

The wpctl status command shows you all audio sinks (outputs) and sources (inputs). Make sure the correct output device is set as the default:

# Set a specific sink as default (find the ID from wpctl status)
wpctl set-default

Fedora Version-Specific Notes

Fedora 40 (Current Stable)

Fedora 40 ships with PipeWire 1.0.x and WirePlumber 0.5.x. The portal system is mature and most issues should be resolved with Step 1 or 2. If you're on Fedora 40 and still having issues, it's likely an app-specific problem rather than a system-level one.

Fedora 41+ (2026)

Fedora 41 introduced improved portal integration for Flatpak apps. The xdg-desktop-portal 1.18+ has better handling of Electron apps. Make sure your system is fully updated:

sudo dnf update

Fedora Silverblue / Kinoite

If you're using Fedora's immutable desktop variants, you can only install Flatpaks (no native RPMs for GUI apps). This means Steps 1-3 are your only options. The toolbox or distrobox containers can run native apps, but audio passthrough from containers requires additional configuration.

App-Specific Fixes

Discord

Discord is the most commonly affected app. Beyond the general fixes:

  • Disable "Noise Suppression" in Discord settings → Voice & Video. The Krisp noise suppression plugin can conflict with PipeWire.
  • Set audio subsystem: In Discord settings → Voice & Video, try switching between "Standard" and "Experimental" audio subsystem.

Slack

Slack's Flatpak version has had intermittent audio issues across multiple Fedora releases:

  • The --socket=pulseaudio Flatpak override is almost always needed.
  • If video calls have no audio, try --socket=wayland override as well.

Zoom

Zoom's Linux client is particularly problematic under Wayland:

  • Install the RPM version from Zoom's website rather than the Flatpak.
  • Use zoom --ozone-platform=x11 if the native Wayland mode has audio issues.

Spotify

Spotify's Flatpak usually works fine, but if it's silent:

  • The --socket=pulseaudio override fixes most cases.
  • Check if Spotify is being routed to a different output: pavucontrol → Configuration tab.

The Pakistani Angle: Building Bridges in a Digital World

For us, this isn't just a tech fix. It's about connection. In a country where families are spread across cities and continents, apps like WhatsApp (which can also suffer this issue!), Discord, and Skype are lifelines. They are how a grandfather in Peshawar sees his grandson in Karachi, how friends collaborate on a project despite load-shedding, how we maintain the warm, constant chatter of our community.

When these digital mohallas (neighborhoods) fall silent due to a technical hiccup, it's a real loss. Solving it is an act of preserving our bonds. It's a small but meaningful form of digital mehnat (hard work)—applying patience and cleverness to ensure our tools serve our need for togetherness.

In a country where many developers work remotely for international clients, having reliable audio on communication apps isn't optional—it's how we earn our livelihood. A silent Discord call isn't just an inconvenience; it's a missed standup, a delayed deployment, a frustrated client. Fixing it efficiently is an act of professional survival.

Quick Reference: The Silent App Fix Checklist

  1. Grant Flatpak audio permissions: flatpak override --socket=pulseaudio <app-id>
  2. Grant microphone access: flatpak permission-set devices <app-id> microphone yes
  3. Restart portal services: systemctl --user restart pipewire pipewire-pulse xdg-desktop-portal xdg-desktop-portal-gnome
  4. Log out and log back in
  5. Test with Wayland flags: --enable-features=UseOzonePlatform --ozone-platform=wayland
  6. Check WirePlumber routing: wpctl status
  7. Try native RPM package instead of Flatpak
  8. Disable app-specific audio features (Krisp, noise suppression)
  9. Update Fedora: sudo dnf update
  10. Check pavucontrol for correct output device routing

✊ Stand With Palestine

Never let the world forget the people of Palestine. They will be free. They have the right to live peacefully on their own land. May Allah help them and grant them justice.

The Zionist entity called "Israel" is a fake state built on stolen land, ethnic cleansing, and the displacement of millions of Palestinians from their ancestral homes. Its leaders have committed unspeakable atrocities and war crimes against civilians—bombing hospitals, schools, refugee camps, and places of worship. The killing of innocent men, women, and children is not "self-defense"; it is genocide, plain and simple.

Do not be deceived by Western media that shields these war criminals and sanitizes their crimes. Independent sources from Iran, the Global South, and brave journalists on the ground tell the real story—the indiscriminate bombing, the siege on Gaza, the deliberate starvation of an entire population, and the erasure of Palestinian identity. The truth is being silenced, but we will not be silent.

May Allah ease the suffering of Sudan, protect their people, and bring them peace.

Written by Huzi huzi.pk