This issue is resolved now and too minor to trigger a reworking of the log system. My suggestions would be:

1. Do change the log message from a warning to an error regardless. Not being able to access the sound card is an error and an unexpected situation which will lead to other problems (as seen in the original complaint).

2. Your --started-by solution seems to be desirable on its own. I would suggest opening up a new bug report so that knowledgeable people can discuss the best solution to the current logging situation and then proceed to implement it.

Hopefully the combination of the two might result in better logging to this particular problem but I think #2 is out of the scope for this particular issue and should be discussed on its own merits.

On 29 June 2018 at 06:50, <bugzilla-daemon@freedesktop.org> wrote:

Comment # 8 on bug 107037 from Tanu Kaskinen

I tested how the warning shows up in journalctl, and unfortunately it has no
highlighting. Making the warning an error wouldn't help, because the problem is
that when pulseaudio is started by systemd, the logs go to stderr. The journal
picks up the messages from stderr, but the journal has no idea about the
importance of the messages. PulseAudio supports logging to the journal
directly, but unfortunately that doesn't get enabled when PulseAudio is started
by systemd.

We could pass --log-target=journal on the command line that is specified in the
.service file, but that would make it impossible to override the log target
from daemon.conf, so some other solution is needed. I think it would be good to
add a --started-by=foo command line option. If it's set to "systemd", we could
then adjust the default log target based on that. The option would also provide
useful information in "ps" output.

You are receiving this mail because:

You reported the bug.