On Sun, 17 May 2015 12:55:18 +0200 Reindl Harald <h.rei...@thelounge.net> wrote:
> > > Am 17.05.2015 um 12:46 schrieb Mikhail Morfikov: > > Is that possible? I'm asking because I often listen to the music > > and I don't really need my monitor to be on most of the time, so I > > just lock the screen. But when I lock the screen, the active > > session becomes inactive and amarok stops playing. And yes, the > > screen should be locked, and not just turned off > > that's a pulseaudio problem and if you run pulsed as system-wide > audio is indepdendent of sessions and you may want to look at MPD > which can even start playing music after power on the machine without > login > I see, I've read this article: http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/SystemWide/ and I've changed the pulseaudio config file a little bit: allow-module-loading = no allow-exit = no system-instance = yes enable-shm = no exit-idle-time = -20 then I started pulseaudio in the system mode and I was able to play sound all the time. But there's another question -- is there any difference between pulseaudio in system mode and pulseaudio in user mode + adding specific users to the "audio" group? I mean in the link I had given in the previous post, you can read something like this: "By the way, you don't want users permanently added to groups like audio or video. Such user would be able to ssh into the machine while you are using it and spy on you using webcam, microphone etc. Access to such critical peripherals should only be granted for active user." Does this concern pulseaudio in the system mode with users added to the pulse-access group?
pgpFtCRkmM3xb.pgp
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel