Pulseaudio and systemd --user: DBus scope issues?

Question

Hi,
I have a multi-seat setup, so I need user-wide pulseaudio and whatnot. I'm trying to setup my boot through systemd --user.
Testing audio working apps are firefox, mpv, and mpd. The problem is:
- If I start pulseaudio and mpd manually everything is fine (no use of systemd)
- If I start pulseaudio through systemd no application has sound.
- If I start pulseaudio and mpd through systemd only mpd has sound.
raimundoyamtech~$ cat .config/systemd/user/pulseaudio.service
[Unit]
Description=PulseAudio Sound System
After=sound.target
[Service]
ExecStart=/usr/bin/pulseaudio
[Install]
WantedBy=multi-user.target
raimundoyamtech~$ cat .config/systemd/user/mpd.service
[Unit]
Description=Music Player Daemon
After=network.target sound.target
[Service]
ExecStart=/usr/bin/mpd %h/.config/mpd/mpd.conf --no-daemon
ExecStop=/usr/bin/mpd %h/.config/mpd/mpd.conf --kill
Restart=always
[Install]
WantedBy=multi-user.target
If I add BusName=org.pulseaudio.Server to the pulseaudio.service nothing changes.
Using pulseaudio's autospawn=yes leads to what seems to be same behaviour: mpd by systemd starts pulseaudio and is the only app with sound.
./config/pulse/client.conf only contains default-sink. Everything else is default.
Using alsa alone is not an option because of firefox.
Any thoughts?
EDIT:
raimundoyamtech~$ systemctl --version
systemd 208
+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ
raimundoyamtech~$ pulseaudio --version
pulseaudio 4.0
Last edited by Raimundo (2013-10-23 10:08:13)

Answer 1

ewaller wrote:
Please do not bump.   I understand the frustration; really, I do.  But, these are very active forums with some very good technical people lurking about.  I guarantee your post had been read.  I read it.  I did not have an answer, as I have never seen that behavior afore.   I am certain that was true for many other regulars.
In the future, you can bring focus to a thread by providing more information..  Tell us what you have tried, what you have read since the last post, etc.  At least it gives the impression that you are working the problem rather than merely waiting for a response.
I don't know almost anything about systemd, especially because it changes so rapidly and documention is so scarce and outdated that either I read the whole documentantion for my version in hopes of finding my problem (something for which I do not have time) or post a topic.
I posted everything I touched regarding systemd since the installation of my system, that's all the relevant information I know I can give, so at this point I had no more info to give.
Actually posting a topic is really my last resort, it usually means that I have already tried everything I knew and I'm hopeless already.
raimundoyamtech~$ loginctl list-sessions
SESSION UID USER SEAT
2 1002 carla seat0
1 1000 raimundo seat0
2 sessions listed.
raimundoyamtech~$ loginctl show-session 1
Id=1
Timestamp=Tue 2013-10-29 12:33:47 WET
TimestampMonotonic=6670234
VTNr=1
TTY=tty1
Remote=no
Service=login
Scope=session-1.scope
Leader=1456
Audit=1
Type=tty
Class=user
Active=no <----- Is this what you are talking about?
State=online
IdleHint=yes
IdleSinceHint=1383050072367636
IdleSinceHintMonotonic=0
Name=raimundo
raimundoyamtech~$ loginctl show-session 2
Id=2
Timestamp=Tue 2013-10-29 12:33:47 WET
TimestampMonotonic=6667439
VTNr=2
TTY=tty2
Remote=no
Service=login
Scope=session-2.scope
Leader=1453
Audit=2
Type=tty
Class=user
Active=no <----- Is this what you are talking about?
State=online
IdleHint=yes
IdleSinceHint=1383050025387636
IdleSinceHintMonotonic=0
Name=carla
raimundoyamtech~$ loginctl show-session 3
Failed to issue method call: No such file or directory
What is an active session? Oo Never heard of it
I could start things. Pulseaudio started, so did mpd. I also have a /usr/lib/systemd/systemd --user process started for each user. I assumed this would be it since this
raimundoyamtech~$ systemctl --user
Failed to issue method call: Process /bin/false exited with status 1
always happens and I've read that systemctl --user is no longer required.
[EDIT]
Fixed it. Don't remember where I read that it wasn't required, just that it was in the same place I found someone else complaining about getting this error.
For anyone else encountering this: sed -i s/system-auth/system-login/g /etc/pam.d/systemd-user
and systemctl --user will work. Insults fly out to the one who wrote it wasn't required!
Still am not able to get an active session though
[/EDIT]
Why would there be a need for anything else? I'm gonna check on that. Thanks!
See, the bump worked ^^ but ok I'll try to refrain from doing that next time. Sorry.
Last edited by Raimundo (2013-10-29 16:27:55)