Package Details: mopyrust-git r1.0000000-1

Git Clone URL: https://aur.archlinux.org/mopyrust-git.git (read-only, click to copy)
Package Base: mopyrust-git
Description: Native Mopidy client for desktop, written in Rust + Tauri + Svelte
Upstream URL: https://github.com/prietus/mopyrust
Licenses: MIT
Conflicts: mopyrust
Provides: mopyrust
Submitter: prietus
Maintainer: prietus
Last Packager: prietus
Votes: 0
Popularity: 0.000000
First Submitted: 2026-05-09 23:39 (UTC)
Last Updated: 2026-05-09 23:51 (UTC)

Latest Comments

prietus commented on 2026-05-27 23:16 (UTC) (edited on 2026-05-28 00:29 (UTC) by prietus)

Your mopidy4 is missing the compatibility shim that re-exports PlaybackState under its old name in mopidy.core. On the install where it works, the AUR mopidy4 package (4.0.0-2) has this line at the top of /usr/lib/python3.14/site-packages/mopidy/core/init.py: from mopidy.types import PlaybackState # noqa: F401 compat shim for mopidy-mpd 3.x

Without that shim, mopidy-mpd 3.3.0 fails during setup (ImportError: cannot import name 'PlaybackState' from 'mopidy.core' so the MPD listener on port 6600 never opens. Mopidy's HTTP/JSON-RPC on 6680 still comes up fine, which is why mopidy logs "connection established" when mopyrust starts — that's the HTTP side. The "Connection refused" mopyrust shows is from its second connection, the MPD one on 6600, which has nothing listening. Quick workaround: add that line by hand to /usr/lib/python3.14/site-packages/mopidy/core/init.py and restart mopidy — ss -tlnp | grep 6600 should then show mopidy listening, and mopyrust will connect. The clean fix is on the packaging side: either the mopidy4 package you're using should include the shim, or mopidy-mpd needs to be patched to import from mopidy.types directly. Which mopidy4 AUR/repo are you pulling from? That's where the divergence is.

prietus commented on 2026-05-27 21:32 (UTC)

please provide ss -tlnp | grep 6600 and mopidy logs and I'll check

prietus commented on 2026-05-27 21:27 (UTC)

let me investigate

renyuneyun commented on 2026-05-25 03:02 (UTC)

I encounter "Connection refused" when launching the application. I have mopidy4 and mopidy-mpd (applied mopidy4 patch) installed, and can see everything loads correctly from mopidy (I run it via commandline directly). The mopidy output also says connection established every time I run mopyrust.

Could this be a compatibility issue for mopidy4 (packaging issue), or an upstream issue?