Returning an empty `icon_name` in `tray_linux_ksni.rs` forces SNI
panels (e.g., KDE Plasma) to render the explicit `IconPixmap` data.
This prevents panels from incorrectly resolving the full-color app icon
from the system theme instead of the intended monochrome tray glyph.
Also updates `src-tauri/icons/icon-symbolic.svg` and regenerates
all `tray-dark-*.png` and `tray-light-*.png` assets.
Adds `static/logo.svg` as the main application logo.
Triggered by release-linux completion (same as AUR).
Updates ebuilds in vicrodh/qbz-overlay with new version.
Requires OVERLAY_PAT secret for cross-repo push.
cc
loadFolders was marking ALL network folders as inaccessible when
offline, regardless of the reason. Manual offline mode and
not-logged-in still have LAN access for NAS/Plex — only no_network
should hide them. Now uses shouldExcludeNetworkFolders() which
already had the correct logic.
cc
activate_offline_session was only initializing library, offline,
offline_cache, audio_settings, and playback_prefs. Missing stores
caused "No active session" errors for:
- download_settings (Show in Local Library toggle)
- session_store (session persistence)
- favorites_cache/prefs (favorites view)
- tray_settings (tray icon settings)
Now mirrors activate_session but skips online-only services
(MusicBrainz, ListenBrainz, Last.fm, API cache, artist vectors).
cc
Two bugs:
1. mainContentEl teardown crash on logout — the $effect cleanup used
non-null assertion (!) on an element that becomes null when the DOM
is destroyed during logout. Changed to optional chaining (?.).
This TypeError was blocking the render, causing the spinner to hang
instead of showing the login form.
2. deactivate_session was clearing last_user_id, which broke offline
mode after logout. The user's data stays on disk — only factory
reset should clear the last_user_id marker.
cc
Three bugs prevented offline mode from working after V2 migration:
1. activate_offline_session used user_id=0 (empty profile) instead of
the last known user_id, so the user's library/settings were invisible
2. setManualOffline was called BEFORE activate_offline_session, but it
requires the offline store to be initialized (which happens during
session activation). Reordered: activate session first, then set
manual offline.
3. LoginView called setManualOffline directly instead of delegating to
the parent's handleStartOffline which has the correct order.
Also added "noPreviousSession" i18n message for users who never logged
in — they need to create a profile first before offline mode works.
cc
runtime_bootstrap returns Err(RuntimeDegraded) when bundle extraction
fails (no network), which throws an exception in the frontend. The
catch block was formatting the raw error object as JSON instead of
showing the connection failed message with the offline button.
Now detects BundleExtractionFailed/Network error in the catch block
and shows the proper i18n connection error, making the "Start Offline"
button accessible.
cc
When get_stream_url_with_fallback internally falls back from UltraHiRes
to HiRes (due to restrictions), the retry logic was requesting a fresh
URL at the original UltraHiRes quality — triggering another fallback
cycle and CDN connection issues.
Now tracks the effective quality from stream_url.format_id and retries
at that quality directly. Applied to both streaming and standard
download paths.
cc
When ALSA Direct hw: is active but a remote device (phone, speaker) is
the active renderer via QConnect, volume changes go to the remote device
not the local DAC. The 100% lock should only apply to local playback.
cc
In compiled builds, the session snapshot can be stale when the badge
popup opens — the deferred_renderer_join completes after the initial
snapshot was fetched, so QBZ doesn't appear in the renderer list.
Now fetches a fresh snapshot from the backend every time the popup
opens, ensuring the renderer list is always current. Uses a local
$state copy that syncs from the prop but can be updated independently.
cc
In Flatpak, the default temp dir is inside the sandbox and invisible
to the host's KDE StatusNotifierWatcher. libayatana-appindicator writes
the PNG to temp dir and calls set_icon_theme_path, but KDE can't see
sandbox paths. Use ~/.local/share/icons which is exported to the host
via Flatpak filesystem permissions.
Non-Flatpak installs continue using XDG_RUNTIME_DIR.
cc
AlbumCard large is 210px but the grids used minmax(180px, 1fr),
causing cards to squeeze and overlap. Updated to minmax(220px, 1fr)
with 24px gap in both LocalLibrary artist view and Favorites artist
sidebar.
cc
Rust:
- Remove unused get_screen_resolution() function
- Remove unused DEFAULT_QCONNECT_DEVICE_NAME constant
Svelte:
- Add tabindex=-1 to TitleBarNav menu dropdowns (a11y)
- Make volumeRef reactive with $state() in NowPlayingBar
- Remove unused .section-separator CSS from NowPlayingBar
- Remove unused .artist-albums CSS from SearchView and Grid
- Remove unused .artist-list-meta CSS from ArtistList
cc
rcgen 0.14 breaking changes:
- CertificateParams::new() takes Vec<String> not Vec<SanType>
- Certificate::from_params() replaced by params.self_signed(&key_pair)
- cert.serialize_pem() replaced by cert.pem()
- cert.serialize_private_key_pem() replaced by key_pair.serialize_pem()
- Ia5String no longer public, DNS SANs passed as strings
Also prefixed unused _envelope variable in qconnect_service.rs.
cc
QconnectBadge was passing { rendererId } instead of
{ request: { renderer_id: rendererId } } to v2_qconnect_set_active_renderer,
causing "missing required key request" error on every handoff attempt.
Also fixed TypeError when event.payload is a string ("TransportConnected")
instead of an object — the 'in' operator requires an object operand.
cc
QBZ wasn't appearing as a renderer on first connect because the
frontend snapshot was emitted before the deferred renderer join
completed. After joining as renderer, wait 500ms and re-request
session state so the server sends an updated renderer list that
includes QBZ.
cc
Major rewrite reflecting current state of the project:
- Qobuz Connect as headline feature
- No API keys needed (proxy-based architecture)
- API proxy self-hosting instructions for source builds
- Updated tech stack (rodio 0.22, MuPDF 0.6, ashpd, 5 locales)
- 13 crates including 4 QConnect crates
- Removed outdated sections (KWin title bar, vendored rodio, data migration)
- Streamlined installation and known issues
cc
Camera raised (y: 1738 -> 2200) and tilted steeper (x: -0.65 -> -0.78)
so the entire bed is visible without overflowing the bottom edge.
Also avoids covering the track info in the lower-right corner.
cc
Nix sets HOME=/homeless-shelter during builds, which makes
dirs::config_dir() return a technically writable but unusable path.
The keyring/D-Bus is also unavailable in the sandbox.
Added detection for HOME containing "homeless-shelter" or
"/nix/store", and NIX_BUILD_TOP env var, to skip credential
roundtrip tests in Nix builds.
cc
MediaControlError doesn't impl Display on all platforms. Using {}
would fail to compile on non-Linux targets. Use {:?} (Debug) instead.
Cherry-picked from PR #181 by @afonsojramos.
cc
The mpris slot requires an auto-connect review from Canonical that has
been pending for 9+ days. Remove it to unblock the version bump from
1.1.18 to 1.1.20. MPRIS media controls will not work in the snap
build until the review is approved in a future release.
cc
MusicBrainz is a one-way pull — QBZ fetches public data but never
sends user data back. Added this clarification to the help text in
all 5 locales and to the wiki Integrations page.
cc
- devalue 5.6.3 -> 5.6.4: fixes prototype pollution in parse/unflatten
(GHSA #23, #24)
- @sveltejs/kit -> 2.53.3: fixes deserialization DoS in form actions
cc
Replaces placeholder-text markdown templates with structured YAML
issue forms. Dropdowns for installation method, display server, and
audio backend. Required fields for description, steps, and version.
Same output format when reading submitted issues.
cc
Exclusive Mode, DAC Passthrough, and Force Bit-Perfect now have (?)
help icons that show detailed explanations on hover:
- What backend each setting requires (ALSA Direct vs PipeWire)
- What PipeWire properties they affect (clock.force-rate, quantum)
- How they relate to each other (dependency chain)
- What happens without them (resampling to default rate)
i18n help texts added to all 5 locales.
cc
v2_query_dac_capabilities was returning hardcoded sample rates
(44.1-192kHz including 176.4kHz) instead of querying the actual
hardware. This caused incorrect configuration for DACs that don't
support all rates (e.g. DacMagic Plus doesn't support 176.4kHz).
Now queries /proc/asound/cardN/stream0 via PipeWire sink mapping
or ALSA device ID to get the real discrete rates from the USB
descriptor. Falls back to defaults only if detection fails.
cc
Tauri invoke errors are objects with { code, details, message } fields.
Template literal interpolation with ${err} produces [object Object].
Extract .message or .details, falling back to JSON.stringify().
The quality fallback itself (UltraHiRes -> HiRes) is already handled
by get_stream_url_with_fallback in qbz-core.
cc
loadFollowingPlaylists was calling non-existent v2_get_runtime_status
command. Fixed to use getUserInfo() from authStore instead.
Also fixed loadFavoritePlaylists early return when no favorites exist
— it was skipping the loadFollowingPlaylists() call entirely.
cc
Separates playlists into two sub-tabs:
- Favorites: playlists marked with the heart icon (local QBZ feature)
- Following: playlists subscribed on Qobuz (owner.id != current user)
The Following tab shows playlists from getUserPlaylists where the
owner is not the current user, matching Qobuz's subscription model.
i18n keys added to all 5 locales.
cc
Qobuz API's albums_count on Artist objects includes compilations,
tributes, appearances, and other non-album releases, showing
exaggerated numbers (e.g. 647 albums for an artist with ~20 releases).
Removed the count display from:
- Favorites artist list view
- Favorites artist grid view
- Search results artist cards
The accurate album count is available inside ArtistDetailView where
the actual releases are loaded and filtered.
cc
Discovered undocumented Qobuz API endpoints from bundle analysis:
- POST /playlist/subscribe { playlist_id }
- POST /playlist/unsubscribe { playlist_id }
This is the native "follow playlist" feature that syncs across all
Qobuz clients, separate from QBZ's existing "Copy to Library" (local
copy) and "Favorite" (local flag) features.
Added:
- subscribe_playlist/unsubscribe_playlist in both qbz-qobuz and legacy client
- v2_qobuz_subscribe_playlist / v2_qobuz_unsubscribe_playlist commands
- Bookmark toggle button in PlaylistDetailView (next to Copy button)
- i18n keys in all 5 locales
cc
USB hubs/docks (e.g. Razer USB4 Dock) may need longer than 300ms for
sample rate switching. When PipeWire hasn't finished reconfiguring,
96K/192K tracks play at wrong speed (half/quarter) and sound distorted.
Changes:
- Increase initial clock.force-rate delay from 300ms to 500ms
- After stream creation, query pw-metadata clock.rate to verify the
actual graph rate matches what was requested
- If mismatch detected, retry with additional 500ms delay and re-force
- Log warnings when rate can't be verified so users can report
cc
mupdf 0.5 had struct size mismatches on Arch Linux (mupdf-sys bindings
incompatible with system MuPDF headers). Upgrading to mupdf 0.6 fixes
the bindings.
- Removed the booklet feature gate — mupdf is now a direct dependency
again, matching the v1.1.19 configuration
- Removed stub implementation (always compile real MuPDF backend)
- sys-lib-libjpeg remains excluded (cross-distro libjpeg incompatibility)
cc
xdpyinfo returns combined multi-monitor resolution (e.g. 6000x1600 for
dual monitors), causing false positives like clamping 1926x1590 to
5700x1520. The 95% multiplier made things worse — the fallback size was
larger than any single monitor.
Replace with simple corruption guard: only clamp values above 8K
(obviously corrupt DB entries), fallback to 1920x1080. The window
manager already handles fitting windows to the actual display.
cc
The KWin window rule approach (kwinrulesrc + qdbus reconfigure) was
never actually active because GDK_BACKEND is unset on most KDE Wayland
sessions. In v1.1.18 this meant decorations(use_system_titlebar) was
used directly — GTK CSD appeared (ugly but functional, no CPU issues).
The hack itself, when triggered, caused double titlebar and a CPU busy
loop that blocked networking. Remove all KDE-specific detection and
KWin rule setup. Window now simply uses decorations(use_system_titlebar)
on all platforms, matching the effective behavior of v1.1.18.
The one-time cleanup of stale kwinrulesrc entries is preserved so users
who had the rule from v1.1.14-v1.1.19 get it cleaned up automatically.
cc
When BundleExtractionFailed (no network), the error box only showed
"Retry" with no way to enter offline mode. The timeout case and login
form both had the offline button, but the error state was missing it.
Added "Start Offline" button using existing offline-btn CSS and
i18n keys. Also replaced hardcoded strings with $t() calls.
cc
With ALSA Direct hw: there is no software mixer — volume must be
controlled at the DAC/hardware level. Software volume attenuation
would reduce bit depth and defeat the purpose of bit-perfect playback.
Backend: v2_set_volume forces volume to 1.0 when backend=Alsa+plugin=Hw
Frontend: volume slider disabled (grayed out at 100%), mute/step buttons
hidden, handleVolumeChange and handleToggleMute return early.
Settings callbacks notify +page.svelte when backend/plugin changes to
update the lock state in real-time.
i18n: volumeLockedHw tooltip added to all 5 locales.
cc
Two additional gaps found during audio settings sync audit:
1. convert_to_qbz_audio_settings() hardcoded alsa_hardware_volume to
false instead of reading settings.alsa_hardware_volume. This meant
the player never received the user's ALSA hardware volume preference.
2. v2_reset_audio_settings saved defaults to DB but never synced them
to the CoreBridge player, leaving stale settings in memory.
cc
Two bugs caused the exclusive mode to not work when QConnect was active:
1. Critical audio setters (backend_type, exclusive_mode, dac_passthrough,
output_device, alsa_plugin, pw_force_bitperfect, sample_rate,
alsa_hardware_volume) saved to the per-user store but never called
reload_settings() on the CoreBridge player. The Player kept using
stale settings (often defaults with backend_type=None), falling back
to CPAL/PipeWire instead of ALSA Direct.
2. After login, per-user audio settings were loaded into AudioSettingsState
but never pushed into the CoreBridge player, which was created at
startup with flat-path defaults.
Fix: Add sync_audio_settings_to_player() helper and call it from all
critical audio setters. Also sync settings in activate_session() and
activate_offline_session() right after audio_settings.init_at().
cc
Developer Mode: toggle to show/hide QConnect dev panel button in
the player bar (hidden by default, persisted in localStorage).
Integrations: editable device name input for Qobuz Connect with
default "Qbz - {hostname}". Backend commands v2_qconnect_get/set
_device_name and v2_get_hostname. Custom name is used during the
WS bootstrap handshake.
cc
Place QConnect badge as direct child of badges-group with 3px gap
matching DAC/EXC spacing. Two-row vertical layout: icon on top,
Qobuz/Connect text below. Wire props from +page.svelte to both
NowPlayingBar instances. Add qconnect i18n keys to de/fr/pt locales.
cc
resolve_core_shuffle_order was reordering the server's shuffle_order
to put the current track first. This destroyed the server's concept
of "already played" vs "upcoming" — CoreBridge showed all tracks as
upcoming while the web player correctly split them.
Now the server's raw shuffle_order is passed through unchanged.
CoreBridge's set_queue_with_order finds shuffle_position from
current_index, preserving the played/upcoming split.
cc
mupdf-sys 0.5.0 bindings are incompatible with the current system
MuPDF library (struct size assertions overflow). Gate mupdf behind
a booklet feature flag (disabled by default). When disabled, booklet
commands return an error instead of crashing the build.
cc
- setAutoplayMode now sends autoplay preference to QConnect server
- queue_load_tracks syncs local autoplay mode after loading
- QConnect panel shows autoplay_mode status
Backend _if_remote methods for QConnect autoplay protocol:
- set_autoplay_mode_if_remote: toggles autoplay on the QConnect server
- autoplay_load_tracks_if_remote: loads track IDs into the autoplay pool
Both follow the established _if_remote pattern with diagnostics.
Prevents double-bootstrap on initial connect. The Subscribed
handler now only calls bootstrap_remote_presence when the
connection was previously lost (has_disconnected=true), not
on the first connect where connect() already bootstraps.
Also sets has_disconnected=true in the Disconnected handler.
New _if_remote backend commands for set_volume and mute_volume.
handleVolumeChange and handleToggleMute in both main view and miniplayer
now check for peer renderer before setting volume locally. Media
control set_volume also routed through the guard. When no peer is
active, volume is set locally and reported to QConnect server.
When a peer renderer is active, the MPRIS/media-key stop command now
sends SetPlayerState(STOPPED) to the QConnect server instead of stopping
local playback. Falls back to local stop on error or when no peer is
active.
Replace immediate seek-on-drag with the NowPlayingBar pattern:
preview the position visually during drag, commit the seek only on
mouseup. Both PlayerControlsCompact and MiniPlayerFooter now use
dragPreviewTime/effectiveTime, matching NowPlayingBar behavior.
Replace local isMuted/previousVolume state in PlayerControlsCompact and
MiniPlayerFooter with the global toggleMute from playerStore. Muted
state is now derived from volume === 0, matching NowPlayingBar behavior.
Pre-mute volume is persisted in localStorage by the store.
When a peer renderer is active, shuffle/repeat/queue-play/history-play
commands are now routed to the QConnect server instead of being applied
locally. Two new backend commands (toggle_shuffle_if_remote,
cycle_repeat_if_remote) follow the existing _if_remote pattern.
Guards added to both +page.svelte (main + immersive) and miniplayer.
When QBZ is the local renderer in a QConnect session and the web player
presses next, the server sends SET_STATE with the new track. The backend
correctly starts playback, but the frontend's gapless transition handler
saw the track_id change, treated it as a local gapless event, and called
nextTrack() — which advanced the CoreBridge queue every 1s polling cycle,
flooding the queue and destroying the shuffle order.
Root cause: shouldQconnectSuppressLocalPlaybackAutomation only suppressed
when a peer renderer was active (activeRendererId !== localRendererId).
When QBZ IS the renderer, remoteControlMode stayed false, so all local
automation (gapless, auto-advance, resume-from-stop) remained active and
fought the server.
Fix: suppress local playback automation whenever QConnect is connected,
regardless of which renderer is active. The server is the authority for
track transitions in all QConnect scenarios.
cc
SrvrCtrlQueueTracksReordered and SrvrCtrlQueueTracksRemoved were not
triggering AskForQueueState, so the local queue never reflected
reorder/remove actions performed via QConnect. Same pattern as the
existing shuffle resync.
cc
vicrodh