The only possibly-related information I can see there is:
Jun 12 06:17:30 hero boltd[7027]: power: setting force_power to ON
Jun 12 06:17:30 hero boltd[7027]: power: state changed: supported/on
Jun 12 06:17:30 hero boltd[7027]: power: guard '3' for 'fwupd' active
which may be relevant because DisplayPort and Thunderbolt are the same bus, at least for Intel GPUs. So a few more ideas to try:
2. Disable Night Light. There have been some bug reports, and suggestions from upstream, that gnome-settings-daemon managing the colour profile separately to the power state is causing some confused states.
The only possibly-related information I can see there is:
Jun 12 06:17:30 hero boltd[7027]: power: setting force_power to ON
Jun 12 06:17:30 hero boltd[7027]: power: state changed: supported/on
Jun 12 06:17:30 hero boltd[7027]: power: guard '3' for 'fwupd' active
which may be relevant because DisplayPort and Thunderbolt are the same bus, at least for Intel GPUs. So a few more ideas to try:
1. Disable fwupd, with something like:
sudo systemctl stop fwupd.service
sudo systemctl disable fwupd.service
2. Disable Night Light. There have been some bug reports, and suggestions from upstream, that gnome-settings- daemon managing the colour profile separately to the power state is causing some confused states.
3. If all else fails, report the issue upstream: https:/ /gitlab. gnome.org/ GNOME/mutter/ issues