-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spotifyd crashes after update (to 0.3.0) #765
Comments
Thats probably an issue which will affect most of the upgraded clients. Upgrade your config file to the format shown on the readme. We have added a breaking change to this release so parsing configs will fail if you used the old version in combination with a config file. |
I updated my config file according to the readme and it would seem
After my update, I was able to get spotifyd running, but I am now seeing other errors. I use Click to show logs
|
the arch linux bug report you linked should be the same as #744, i think the user of that issue was compiling from master and thus already using new code (eventhough the report says 0.2.24) |
0.2.25 is a breaking change? Shouldn't the version be 0.3.0 then? Edit: I always thought that this was inside the specification, but it seems it's not. "Anything can change at any time" is their wording. But I think that pumping the minor might still be a good idea to indicate a larger change and not just "a fix or patch". |
That might have been better!, maybe at some point we should bump it to 1.0 to promise a stable release as anything < 1.0 has to guaranties in semantic versioning |
Ye, I always hesitated to bump to v1 as even the features that are available aren't complete or buggy (like MPRIS). If those are fixed I'd be happy to go for the v1 I think. |
as we already released to crates.io im not sure if there is a way to reverse the release? |
ye, you can yank releases on crates.io: https://doc.rust-lang.org/cargo/reference/publishing.html#cargo-yank. |
also the newest CI job/tag is on the HEAD and not on the same commit as the crates.io release. So i think yanking the release and making a new release/tag on 0.3 might be a good idea |
Definitely! |
the 0.2.25 release is yanked from crates.io and from github releases, and a new crates.io/github release has been make. And the binaries are succesfully pushed by cd to the release page 🎉 |
I deleted the client.yml file in .config/spotify-tui directory and reconfigured spotify-tui and it works fine |
Was hitting issue: Spotifyd/spotifyd#786 (real issue: Spotifyd/spotifyd#765), but updating to the latest configuration file changes (https://spotifyd.github.io/spotifyd/config/File.html) fixed my `spotifyd` service from running.
Important, you'll like hit this [upstream issue][1] and see something like: ``` thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { inner: ErrorInner { kind: Custom, line: Some(64), col: 17, at: Some(1937), message: "invalid type: integer `90`, expected a string", key: ["global", "initial_volume"] } }', src/config.rs:468:67 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` This is due to the config format changing and values needing quoting. Adds a new patch [based on this PR][2]. [1]: Spotifyd/spotifyd#765 [2]: Spotifyd/spotifyd#796
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hijacking for visibility: Make sure to update to the new TOML config file format (see README) when using 0.3.0!!!
Edited by @sirwindfield
Description
spotifyd does not start after updating from version 0.2.24 to 0.2.25. Downgrading to 0.2.24 works.
Expected behavior
For spotifyd to launch in the background withour errors.
Logs
Click to show logs
journalctl logDisabling the systemd unit and running manually:
Versions (please complete the following information):
Comments:
The Arch linux package has a bug report here, that looks like the same issue:
https://bugs.archlinux.org/task/69308?project=5&string=spotifyd
The bug report on Arch also points to #719
The text was updated successfully, but these errors were encountered: