-
Notifications
You must be signed in to change notification settings - Fork 459
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
Error while installing #655
Comments
The readme should by now mention that you have to use If you have trouble with any of the backends you could always use I don't think that we currently provide binaries for linux that contain rodio. #610 has been merged today and some work is being done in #653. After that I will probably trigger a new build to generate new binaries. Those will actually contain all audio backends on all systems if you select the |
okay i'll give rodio a try. but i wanna try one last time. i'm running Ubuntu 20.04 if that helps |
Looks right. You sure that you installed pulseaudio on your system? The other parameters ( |
Try to run |
Do you see the panic message? If you run |
yeah i do get alsa backend listed it seems like there is a problem with the port or something |
You need to remove the proxy entry in the configuration file.
|
man i'm so dumb i just now noticed that and i removed that but it still doesn't work when i run spotifyd |
any solutions? |
Good question. A lot of people had that problem. I had no time to investigate it though. You might be missing a syslog logger on your system, which causes this issue. The log should contain a line telling you that it failed to initialize logging. For now you just have to run it using |
okay, alr cool. and one more thing every time i start spotifyd it sets the volume level to 94% which is annoying as i'm using earphones and it just blows my head out. is there a fix? and also i'm now able to control the playback using media control keys or playerctl or alsamixer even though i added the feature flags for media controls |
it depends on your environment if the media keys do indeed send commands through your running DBUS instance. You'd have to check yourself to see if they do and if not try to find a fix for it. There is not much I can do for you on that department. Regarding the volume: It's a known issue and I remember merging a PR that fixes it but maybe it broke again (or my mind plays on me). I'll take a look. |
alr cool thanks, i'll close this issue now |
running the command from this comment outputs: |
Sorry, no clue on that one! |
@sirwindfield does the snap package version support playerctl and other stuff or does it just support alsa? |
Just alsa, it's broken though. I don't have rights to push to the registry :( |
Compiling librespot v0.1.3
Compiling spotifyd v0.2.24 (/home/jedi/src/spotifyd)
error[E0063]: missing field
gapless
in initializer oflibrespot_playback::config::PlayerConfig
--> src/config.rs:732:24
|
732 | player_config: PlayerConfig {
| ^^^^^^^^^^^^ missing
gapless
error[E0560]: struct
librespot_core::config::ConnectConfig
has no field namedlinear_volume
--> src/main_loop.rs:172:25
|
172 | linear_volume: self.linear_volume,
| ^^^^^^^^^^^^^
librespot_core::config::ConnectConfig
does not have this field|
= note: available fields are:
name
,device_type
,volume
,volume_ctrl
,autoplay
error[E0027]: pattern does not mention fields
play_request_id
,position_ms
--> src/process.rs:65:9
|
65 | PlayerEvent::Started { track_id } => {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ missing fields
play_request_id
,position_ms
error[E0027]: pattern does not mention field
play_request_id
--> src/process.rs:69:9
|
69 | PlayerEvent::Stopped { track_id } => {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ missing field
play_request_id
error[E0560]: struct
librespot_core::config::ConnectConfig
has no field namedlinear_volume
--> src/setup.rs:97:13
|
97 | linear_volume,
| ^^^^^^^^^^^^^
librespot_core::config::ConnectConfig
does not have this field|
= note: available fields are:
name
,device_type
,volume
,volume_ctrl
,autoplay
error: aborting due to 5 previous errors
Some errors have detailed explanations: E0027, E0063, E0560.
For more information about an error, try
rustc --explain E0027
.error: failed to compile
spotifyd v0.2.24 (/home/jedi/src/spotifyd)
, intermediate artifacts can be found at/home/jedi/src/spotifyd/target
Caused by:
could not compile
spotifyd
.To learn more, run the command again with --verbose.
i solved it by adding --locked to the command cargo install --path . --locked
but i'm not able to use pulseaudio as backend
using alsa does not show my pc as a device in spt even while spotifyd in running.
The text was updated successfully, but these errors were encountered: