The current situation is the following: Audio Professionals, common users and people who aim to connect there desktop computer/notebook/plasma tablet to the TV, plug in their USB and/or HDMI audio device and nothing happens. No notification, no sound, nothing. So, these people may think, their device is broken and/or there open source OS dont support this device. There is a imho very easy solution: Just let the phonon KCM start, once an additional digital audio/video device get detected on the fly. They get connected for one reason: To use them, an undesired launch seems thus to be very unlikely ? This KCM is anyway , besides of the complicated and even more hidden way for audio devices in kmix, the useable solution. The point is, that we direct the people directly to the correct place to setup their output. A menu point in the phonon KCM, which let me enable/disable that function might be also nice, for such uncommon cases where this is inhibiting :) Reproducible: Always Steps to Reproduce: 1. Plug in any digital audio/video device 2. Listen and watch carefully :D Actual Results: No sound, no video, no response at all. Expected Results: Launch of kcmshell4 kcm_phonon / kcmshell5 kcm_phonon
A potentially additional solution: https://bugs.kde.org/show_bug.cgi?id=355169
As I was saying in the other bug report. This should really be a behavioral feature in Pulseaudio. What we could do is show a notification that allows opening the KCM, that's non-persistent and very 1990's though so really, doing it automatically would be better.
Do what you think is suitable, so long as the current situation change.
(In reply to Matthias from comment #3) > Do what you think is suitable, so long as the current situation change. The old Pulse audio control game. :))) I remember having to install pavucontrol in a lot of distros to get stuff to work. As of late, 2016, I haven't run across this.