Bug 449176

SUMMARY
When a background service failed there is no hint for the user in general. If the user goes into systemsettings and try to run the failed service a generic message pops up "Failed to start service". 
There is no hint what went wrong exactly or how to get more infos.


STEPS TO REPRODUCE
1. Have a failed service
2. Observe after a restart of the system that is not started automatically in the system settings (and there is no hint for the user other than there)
3. Start the previously failed service

OBSERVED RESULT

Generic error message

EXPECTED RESULT

First of all after a restart a system message that my service failed. These system service might or might not be important. And users usually don't monitor the systemsettings background services page to see that not service failed. 

If a service failed then I would like to have a non generic error message. Or at least some hint on how to find more interesting infos why the system service actually failed. 

ADDITIONAL INFOS 

In my case this happended with kcm-wacomtablet . When I went to the wacom kcm it told me the "wacom service was not running" and I should enable it in the kcm background service. In this tab I observed that wacom service was in deed not running even though it should start automatically after a boot. 
I then tried to manually run it by pressing the "run button". Then the error message "Failed to start service" popped up. I had no idea why it failed and also no idea where to get more information. I didn't even know what the "Wacom tablet control daemon" is. Maybe a systemd service? No idea. No further information. 

After some system updates and in particular a kernel update and a reboot it magically worked. So I can't reproduce the error right now anymore and attach a screenshot. 

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2