Bug 250498 - audio/spotifyd will not launch as user/nobody only as root
Summary: audio/spotifyd will not launch as user/nobody only as root
Status: Closed Not Enough Information
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Rodrigo Osorio
Depends on:
Reported: 2020-10-21 01:50 UTC by break19
Modified: 2021-04-27 21:37 UTC (History)
3 users (show)

See Also:
fernape: maintainer-feedback? (rodrigo)


Note You need to log in before you can comment on or make changes to this bug.
Description break19 2020-10-21 01:50:01 UTC
FreeBSD13-CURRENT, not sure if it's affect elsewhere, or what about my system has it affecting me.

I had to modify the rc.d script to run spotifyd as root instead of as nobody. It complains that an address already exists and fails to launch when launching as any user.
Comment 1 Fernando Apesteguía freebsd_committer 2020-11-10 08:24:57 UTC
Informing maintainer.
Comment 2 Rodrigo Osorio freebsd_committer 2021-03-23 09:53:57 UTC
(In reply to break19 from comment #0)
Are you using chrome(ium) on the same computer ?
Comment 3 break19 2021-03-23 13:18:59 UTC
(In reply to Rodrigo Osorio from comment #2)
No. I don't use chrome at all on any of my devices. Firefox only.
Comment 4 Steve Wills freebsd_committer 2021-03-23 15:17:14 UTC
(In reply to break19 from comment #0)
Hmm, I use spotifyd as my user without issues. I have these values in rc.conf:

spotifyd_env="HOME=/usr/home/swills XDG_RUNTIME_DIR=/var/run/user/1001"

What exactly have you changed and what is the text of the error message you are seeing?
Comment 5 Rodrigo Osorio freebsd_committer 2021-04-09 22:02:59 UTC
(In reply to break19 from comment #3)


Can you run spotifyd manually an see what's the output message ?
The is the command :

/usr/local/bin/spotifyd --no-daemon --verbose --config-path /usr/local/etc/spotifyd.conf
Comment 6 Rodrigo Osorio freebsd_committer 2021-04-27 21:37:09 UTC
@break19: I'm closing this issue since no additional details where provided,
          to help us to diagnose the issue. You can reopen the issue anytime
          if you have new elements to provide or have a fix for your issue

-- rodrigo