Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: spotifyd panics `Couldn't initialize logger` (Read 2757 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

spotifyd panics `Couldn't initialize logger`

I have recently tried setting up spotifyd for spotify-tui. When I go to activate the daemon via "spotifyd" cmd, it errors with this:

thread 'main' panicked at 'Couldn't initialize logger: Error(Initialization, State { next_error: Some(Error(Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }), State { next_error: None, backtrace: None })), backtrace: None })', src/main.rs:39:51
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I have not been able to find a solution.

NOTE: This is my first week using linux, etc. I have tried doing my research before making this post.

Any help is much appreciated.
exotic

Re: spotifyd panics `Couldn't initialize logger`

Reply #1 –
spotifyd and services have already been added to Universe repo, please use those by adding to your /etc/pacman.conf the following lines:

Code: [Select]
[universe]

https://universe.artixlinux.org/$arch

Re: spotifyd panics `Couldn't initialize logger`

Reply #2 –
How does this help?

I simply just downloaded it from another repo?

I still get this error.

thread 'main' panicked at 'Couldn't initialize logger: Error(Initialization, State { next_error: Some(Error(Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }), State { next_error: None, backtrace: None })), backtrace: None })', src/main.rs:38:51
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
exotic

Re: spotifyd panics `Couldn't initialize logger`

Reply #3 –
Use in bash "export RUST_BACKTRACE=1"

Re: spotifyd panics `Couldn't initialize logger`

Reply #4 –
Quote from: exoticmeiz – on
How does this help?

I simply just downloaded it from another repo?

I still get this error.

thread 'main' panicked at 'Couldn't initialize logger: Error(Initialization, State { next_error: Some(Error(Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }), State { next_error: None, backtrace: None })), backtrace: None })', src/main.rs:38:51
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Installation from another repo has references and services for systemd, not for our init systems

So, the case differs for daemon activation per init (below is Runit).




Re: spotifyd panics `Couldn't initialize logger`

Reply #5 –
I cannot run spotifyd, how does trying to activate it help?

I also cannot locate the service? Do I need to create it manually?

Once again, I get the error:

thread 'main' panicked at 'Couldn't initialize logger: Error(Initialization, State { next_error: Some(Error(Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }), State { next_error: None, backtrace: None })), backtrace: None })', src/main.rs:38:51
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I don't understand how trying to activate the daemon will help, when i cannot do it via cmd?
exotic

Re: spotifyd panics `Couldn't initialize logger`

Reply #6 –
thread 'main' panicked at 'Couldn't initialize logger: Error(Initialization, State { next_error: Some(Error(Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }), State { next_error: None, backtrace: Some(stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: main
  10: __libc_start_main
  11: <unknown>
) })), backtrace: Some(stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: main
  10: __libc_start_main
  11: <unknown>
) })', src/main.rs:38:51
exotic

Re: spotifyd panics `Couldn't initialize logger`

Reply #7 –
You have not yet described how you run spotifyd daemon

The daemon command line is shown above:
Code: [Select]
spotifyd -b pulseaudio --no-daemon

This is been executed as a service, if you install spotifyd and sporifyd-<init> service from universe.

<init> : openrc or runit or s6

After that, just enable the service as per our wiki for your init.

Do so, so to have a common base.
 

Re: spotifyd panics `Couldn't initialize logger`

Reply #8 –
I cannot run:

spotifyd -b pulseaudio --no-daemon

It errors with the error shown above ^
exotic

Re: spotifyd panics `Couldn't initialize logger`

Reply #9 –
Quote from: exoticmeiz – on
I cannot run:

spotifyd -b pulseaudio --no-daemon

It errors with the error shown above ^

^ therefore install our packages from Universe, we did not build them for fun

On runit with rsm:

Re: spotifyd panics `Couldn't initialize logger`

Reply #10 –
I have already done this, yet the same occurs.

I'm not sure what you expect to happen?
exotic

Re: spotifyd panics `Couldn't initialize logger`

Reply #11 –
send the output of service spotifyd, is it up?

Re: spotifyd panics `Couldn't initialize logger`

Reply #12 –
It is not in: 'sudo rsm'.

But that's cause the startup, run won't work? Is it not?

If the exec for run doesn't work manually.
exotic

Re: spotifyd panics `Couldn't initialize logger`

Reply #13 –
if you use runit and you have rsm installed, use

Code: [Select]
sudo rsm enable spotifyd
sudo rsm start spotifyd
sudo rsm status spotifyd

rsm wiki

Re: spotifyd panics `Couldn't initialize logger`

Reply #14 –
The service is down, when I try to start it, it says:

~ ⬢  sudo rsm start spotifyd
[rsm] Running sv command (SVDIR=/run/runit/service/ sv start spotifyd):
timeout: down: spotifyd: 1s, normally up, want up
[rsm] [sv start spotifyd], exit code: 1
exotic