Verify Browser Notification Permissions
Modern browsers like Firefox and Chromium block autoplaying media unless the user explicitly grants permission. When Facebook sends a notification, it attempts to trigger an audio file immediately. If the browser treats this as "autoplay," it will silence the sound silently. You must verify that the site has full permissions for notifications and media. Open your browser settings and navigate to the Privacy & Security section. Look for Site Settings or Content Permissions. Find Facebook in the list of sites with stored data. Ensure that Notifications is set to Allow. More importantly, check if there is a separate setting for Autoplay. In Chrome, this is under Autoplay; in Firefox, it may be under Media. Set Autoplay to allow all audio and video, or specifically allow audio for facebook.com. This change forces the browser to respect the audio trigger from the notification service. If you are using the native desktop app for Facebook, ensure that the application itself is not running in a suspended state. Linux power management can suspend background processes to save resources. Check your system tray icon for Facebook. Right-click it and select Open or Resume. If the app is minimized, it might not receive the audio event properly depending on how the desktop environment handles process priorities.Check System Sound Channels
KDE Plasma uses either PulseAudio or PipeWire for sound management. Both systems have separate volume controls for different types of audio streams. It is possible that your general music volume is high, but the "Notification" or "Alert" channel is muted or set to zero. This is a frequent point of confusion for users who cannot hear alerts despite having working speakers. Open the Volume Control application in KDE Plasma. If you do not see individual channels, installpavucontrol via the terminal using sudo pacman -S pavucontrol. Launch PulseAudio Volume Control. Navigate to the Output Devices tab. You will see a list of active streams. Trigger a Facebook notification while watching this window. A new stream should appear labeled something like "Web Audio API" or "Firefox/Chrome."
Click on that stream and look at the Mute button. Ensure it is not crossed out. Also, check the Balance slider to ensure it is centered. If the stream does not appear when you trigger a notification, the browser is likely not sending the audio signal at all, which points back to browser permissions or codec issues. If the stream appears but is silent, lower the master volume slightly and raise the notification channel volume to test.
Install Web Audio Codecs
Browsers rely on system libraries to decode audio formats like AAC, MP3, and Opus. Manjaro, being Arch-based, often separates multimedia support into distinct packages. If your browser cannot decode the format Facebook uses for its alert sounds, it will fail to play them silently. This is different from installing proprietary drivers for video; this is about basic media decoding. For Chromium-based browsers, you need thelibvpx and opus libraries. For Firefox, it usually bundles its own codecs, but it may fall back to system libraries for certain hardware acceleration paths. Run the following command to ensure your base system has the necessary multimedia support:
sudo pacman -S ffmpeg libx264 libvpx opusDisable Hardware Acceleration Temporarily
Sometimes, GPU-accelerated audio processing can cause conflicts with desktop environments, especially during wake-from-suspend events. Disabling hardware acceleration in the browser forces it to use the CPU for rendering and audio processing, which is more compatible with standard desktop audio servers. In Chrome or Edge, go to Settings > System. Toggle off "Use graphics acceleration when available." In Firefox, go to Settings > General > Performance and uncheck "Use recommended performance settings," then uncheck "Use hardware acceleration when available." Restart the browser. This step is a diagnostic measure. If notifications start working, you know there is a conflict with your GPU drivers or the Wayland/X11 compositing. You may need to update your graphics drivers or switch display protocols.Frequently Asked Questions
Why do I hear other notification sounds but not Facebook?
This indicates that your system audio is working correctly, but the specific application is blocked or misconfigured. Check the browser's site-specific permissions for Facebook, as other apps like Discord or Slack may have already granted broader permissions that Facebook lacks.
Does switching from PulseAudio to PipeWire fix this?
Switching audio servers rarely fixes notification issues directly. However, PipeWire handles stream routing differently. If you switch, ensure your browser is restarted so it detects the new server instance, as some applications cache the audio backend path on launch.
Can I customize the Facebook notification sound in KDE?
No, Facebook controls the audio file served to the browser. You can only mute or unmute the entire stream. To customize, you would need to use a third-party extension that overrides web audio, which is complex and often breaks with site updates.
What if the notification sound works on Windows but not Manjaro?
This suggests a difference in how the desktop environment handles web APIs. Manjaro may have stricter default privacy settings in its browser profiles. Resetting your browser profile or creating a fresh profile often resolves these cross-platform inconsistencies.
Is it safe to ignore these notification sounds?
Yes, ignoring them does not affect your system stability. However, you may miss important messages. If you rely on these alerts, troubleshooting the audio pipeline is necessary for effective communication through the platform.