Hi, On 20-06-18 18:33, Gerald B. Cox wrote:
This isn't related to a service, but is throwing out an spurious error message. There is a patch but it hasn't made it's way yet into the Fedora kernel: rt_cmos registration error: rhbz#1568276 Basically an error is being thrown because your system doesn't have battery backup. To their credit, it was quickly identified and patched. We now just have to wait for the patch to be applied. However these: The mcelog.service message is associated with rhbz#1166978 The dbxtool.service message is associated with rhbz#1508808 The rngd.service message is associated with rhbz#1490632 At least for me are the result of services being enabled by default, that should never have been enabled for my environment. mcelog: I am using an AMD processor. This service only applies to Intel. dbxtool: I am not using SecureBoot. This service only applies to machines using SecureBoot. rngd: I am not using a machine that has a hardware RNG generator Again, if we are apparently so concerned about a streamlined user experience, why are we starting processes that aren't needed - and in fact are not appropriate for a particular environment, and then throwing out error messages which are spurious and confusing? In my case, this caused me to spend hours individually tracking down all these error messages to find out that there is nothing wrong with my environment. Instead the issue is these services are inappropriately started for EVERYBODY - and in one case have been languishing for years. Last time I checked, Fedora wasn't an Intel only, SecureBoot only, mandatory hardware RNG generator environment. If we truly are concerned about end user experience - this isn't the way to go about it.
Note that any service failing will change things over from the silent boot we want to have to showing details, starting with the: Starting foo... [FAILED] message, so I fully agree with you. I've put looking into the 3 service bugs you refer to above at the end of my silent boot todo list. I first want to get al the other bits involved working, but once that is done making sure false-positive failures like this don't break the experience definitely is something which we should work on. Regards, Hans _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/3LVW5ZBXPNF3DD2SNE5CCNND2ARJFMYI/
