Comment 2 for bug 1801796

I actually think that this might have been fixed. I suspect the main reason that bolt was started in the first place was fwupd (the firmware update daemon) starting it to force power the thunderbolt controller. It does so even if there is no controller to force power in the first place.
A small fix (https://github.com/fwupd/fwupd/commit/7e5c7b269a3b9182db58a201c24835177107ad41) to the fwupd daemon should prevent it from poking bolt if there is no hope of boltd succeeding in force powering the daemon. Thus on a system without any thunderbolt controller boltd should not be started anymore.

NB: The linked bug is to auto idle-quit the daemon if it is started but no controller found, while the fix should prevent the daemon to even be started.