Something's not working
The problems people run into most, and what fixes them. If yours isn't here, check the log. It usually names the culprit.
Installing
It isn't. Sonora isn't signed with an Apple developer certificate yet, so macOS quarantines it. Clear the flag once after installing.
xattr -dr com.apple.quarantine /Applications/Sonora.app
Once in a while, macOS may show this dialog again even after whitelisting the app. Run this command again to get rid of it.
The Windows builds aren't code-signed yet. We've applied to the SignPath Foundation for that. Until it comes through, click More infoRun anyway the first time.
On Linux, Sonora draws with Vulkan, and the Vulkan loader alone isn't enough. You need a
driver for your GPU, such as mesa-vulkan-drivers, vulkan-radeon, vulkan-intel or the proprietary NVIDIA driver. Run vulkaninfo --summary to see whether one works.
If Sonora starts but feels sluggish, SONORA_BLUR=0 turns off the lyric blur,
edge fades and visualizer.
Sonora plays through ALSA. If it says Sonora cannot reach your sound server, you're missing the ALSA bridge to your sound server. Install pipewire-alsa on PipeWire or pulseaudio-alsa on PulseAudio, then
restart Sonora. The AppImage doesn't bundle it either.
No sound output means the bridge is there but your audio device didn't open. Check that it's connected and that no other app holds it.
Yes. Every night main is built into the nightly prerelease, with the same installers, AppImages and binaries as a release. On Arch, install sonora-nightly-bin.
yay -S sonora-nightly-bin
With Nix, run the flake at its nightly tag.
nix run github:sonorahq/sonora/nightly
If Sonora updates itself, as the Windows installer, the macOS disk image and the AppImage do, switch between releases and nightlies with SettingsAboutRelease channel. Nightlies skip the testing a release gets, so say you're on one when you report a bug.
Signing in
- Free accounts don't get in. You need Premium.
- The sign-in window hands the session back to Sonora on
127.0.0.1:8989. Close whatever else holds that port and try again. - A region error means Spotify won't serve your account from where you're connecting.
The login windows for YouTube Music, Apple Music and Deezer need WebKitGTK, either webkit2gtk-4.1 or 4.0. Without it Sonora shows Browser sign-in is unavailable and offers cookie pasting instead. That works
just as well.
Sonora waits five minutes for Last.fm on 127.0.0.1:8990. Make sure that
port is free, then approve Sonora in the browser before the time runs out. Last.fm also
needs your own API key and secret; see Scrobbling.
Playback
If every track fails with Spotify is not granting this account playback keys, Spotify won't work for your account in Sonora. Sonora plays Spotify through librespot, and librespot issue 1649 tracks the problem.
Apple Music needs the Widevine module. When none of your browsers has a copy, Sonora offers to download it from Google. If you dismissed that or it never showed up, get it from SettingsPlaybackWidevine module.
If tracks fail because your browser's copy is out of date, download Google's copy in the same place.
Apple Music downloads need an internet connection to play. Downloads from other services play offline. See Downloads and offline.
Settings
You probably broke the formatting of settings.json. Sonora shows Fix line N of settings.json to save changes and won't save anything until you fix it. See Settings file.
If your settings are lost, the previous version is in sonora.backup.json next
to settings.json.
Still stuck? See Getting help.