1.3.3-3 promoted to focal release pocket today fixes this, marking fix
released.
** Changed in: fwupd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Package changed: bolt (Ubuntu) => fwupd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801796
Title:
boltd running on a system with no thunderbolt devices
To manage notifications about
That fix for fwupd to not use boltd on such systems is landed in fwupd
1.3.3 which is currently in focal-proposed.
** Changed in: bolt (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
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
That's known upstream and reported as
https://gitlab.freedesktop.org/bolt/bolt/issues/92
They agree it would be nice so that might happen at some point but it
requires to resolve some questions about interactions with the desktop
components, etc so not trivial.
** Changed in: bolt (Ubuntu)
Imp
