Heres a log on a KDE startup and as far as I can see it is a cascade looking something like this.
DriverManager start python3 which then starts aplay which then again starts pulseaudio. Parallel to that kmixctl is also starting pulseaudio. Both lines of events happen 2 or 3 times. They sort of race eachother.
Heres a log on a KDE startup and as far as I can see it is a cascade looking something like this.
DriverManager start python3 which then starts aplay which then again starts pulseaudio. Parallel to that kmixctl is also starting pulseaudio. Both lines of events happen 2 or 3 times. They sort of race eachother.