void-linux / void-linux/void-packages
spotify-player fails to connect to device
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Is this a new report?
Yes
System Info
Void 6.1.34_1 x86_64-musl GenuineIntel uptodate
Package(s) Affected
spotify-player-0.14.0_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
There's no upstream bug. The issue is due to the Void build itself.
Expected behaviour
spotify-player should be able to find the desired backend.
Actual behaviour
spotify-player is unable to find a backend.
Steps to reproduce
Install spotify-player having only alsa installed and launch the application.
REASON FOR FAILURE:
The package is built with the default features, i.e. there are no configure_args= in the template.
Building the package with cargo using cargo build --release --no-default-features --features alsa-backend produces a working binary.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the spotify-player package template in the void-packages repository and inspect how its Cargo features are configured. Compare the current default build with the reported cargo build --release --no-default-features --features alsa-backend command; done means the package built with only ALSA installed can find a backend.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, shell
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100