-
-
Notifications
You must be signed in to change notification settings - Fork 45
Troubleshooting
vicrodh edited this page Mar 15, 2026
·
5 revisions
Symptoms: Audio plays through laptop speakers instead of your DAC, or no sound at all.
Fix:
- Go to Settings > Audio
- Verify the correct Output Device is selected
- If using PipeWire, ensure your DAC is set as the default sink:
# List available sinks pactl list sinks short # Set your DAC as default pactl set-default-sink <sink-name>
- Restart QBZ after changing the audio device
Symptoms: Your DAC display shows 48000 Hz regardless of the track's actual sample rate.
Fix:
- Switch to ALSA Direct backend for guaranteed bit-perfect output
- If using PipeWire, enable Force Bit-Perfect in Settings > Audio
- Verify with a known Hi-Res track (96 kHz or 192 kHz) — your DAC display should match
Possible causes:
- Buffer too small — increase Stream Buffer in Settings > Audio
- System under load — close resource-heavy applications
- USB DAC power — try a powered USB hub or a different USB port
- Verify the DAC is connected and powered on
- Check if the system sees it:
# List ALSA devices aplay -l # List PipeWire devices pw-cli list-objects Node
- Try unplugging and reconnecting the DAC
- Restart QBZ
QBZ uses hardware-accelerated rendering by default. Some GPU/driver combinations may cause issues.
Quick fixes (in order of severity):
# 1. Reset graphics settings to safe defaults
qbz --reset-graphics
# 2. Disable GPU hardware acceleration entirely
QBZ_HARDWARE_ACCEL=0 qbz
# 3. Force X11 instead of Wayland (common fix for NVIDIA)
QBZ_FORCE_X11=1 qbzYou can combine flags:
QBZ_HARDWARE_ACCEL=0 QBZ_FORCE_X11=1 qbzIf running QBZ from Flathub:
QBZ_HARDWARE_ACCEL=0 flatpak run com.blitzfc.qbz-
Try resetting graphics settings:
qbz --reset-graphics
-
Check logs for errors:
# System journal journalctl --user -u qbz --since "5 minutes ago" # Or launch from terminal to see output qbz
-
If using Flatpak:
flatpak run com.blitzfc.qbz --reset-graphics
If QBZ opens to a broken or blank view, it may be due to a corrupted session state:
# For development builds
npm run -s dev:reset-last-view
# For installed versions, the session database is at:
# ~/.local/share/qbz/users/<user-id>/session.db
# Delete or rename it to reset the session state- Verify your Qobuz credentials work on the Qobuz website
- Check your internet connection
- If you recently changed your Qobuz password, you may need to re-login in QBZ
Ensure PipeWire permissions are granted:
# Check permissions
flatpak info --show-permissions com.blitzfc.qbz
# Reset permissions if needed
flatpak override --user --reset com.blitzfc.qbzFlatpak sandboxes file access. Grant access to your music directories:
flatpak override --user --filesystem=/path/to/your/music com.blitzfc.qbzIf your issue isn't covered here:
- Check the GitHub Issues for existing reports
- Open a new issue with:
- QBZ version (Settings > About)
- Linux distribution and version
- Audio backend and device
- Steps to reproduce the issue
- Any relevant log output
Getting Started
Audio
Appearance
My QBZ
Features
Help