Semi-automatic troubleshooting - could Cadence solve all problems?

[unfa]

I was wondering for a long time if we could make Cadence automatically detect and fix problems with Linux audio for users? Before it took action, it should of course ask users for permission. This feature could be disabled entirely to avoid annoying dialog popups.

For example:

Problem: You can't run JACK, because PulseAudio is blocking the audio interface (everyone has this for starters) **Manual solution: ** search on forums, if you have no idea Automatic solution: apt install pulseaudio-modules-jack

Problem: Your USB audio interface disappears, and hangs JACK after system suspend/restore (I have this issue) Manual solution: Disconnect/reconnect the device and restart JACK Automatic solution: Write down the interface's USB path, if it disappears for no apparent reason try unbinding/binding it and restarting JACK (source: https://enc.com.au/2014/02/14/resetting-usb-devices/) - not tested!

Problem: You have 2 pulse-audio servers running, one though JACK, and one not Manual solution: I don't even know... Automatic solution: Modify some configuration?

etc...

Cadence already has something of that in place with the quick system checks, I guess this could be extended to help - especially new users - to just get it working. I guess a lot of new Linux audio users are turned off by the complexity and amount of things that can go wrong. I think collectively we could come up with a nice set of checks and propose automatic solutions for users.

I'm doing Linux audio for about 8 years now, and I still have things surprise me and not work, even though I was sure I had it figured out.

What do you think about this?

Or maybe this should be created as a separate tool that can be incorporated into QJackCtl etc.?