Updates policy exception request for thermald #3673

Closed
opened 2026-08-05 16:49:41 +00:00 by ngompa · 10 comments
Owner

I would like to request a one-time exception for thermald across all Fedora branches.

This is required to fix power management control on Intel-based machines that rely on thermald for this functionality, as many newer laptops released in the last couple of years have poorly working or completely non-functional support at the moment.

Ordinarily, this would be a regular, compatible update, but the need for the exception comes from the removal of the unmaintained Qt 5 application for monitoring thermald that was shipped as a subpackage. It was deleted upstream, and I do not believe anyone used it, so I think nobody will notice.

Additionally, I'm not yet the main admin for this package, but I expect that will change once #3672 is completed. I would like to use my provenpackager powers in the meantime to get this through as we have urgent requests through Fedora Ready that necessitate this update.

I believe the scope is very small and it should be very safe to allow this exception.

I would like to request a one-time exception for `thermald` across all Fedora branches. This is required to fix power management control on Intel-based machines that rely on `thermald` for this functionality, as many newer laptops released in the last couple of years have poorly working or completely non-functional support at the moment. Ordinarily, this would be a regular, compatible update, but the need for the exception comes from the removal of the unmaintained Qt 5 application for monitoring `thermald` that was shipped as a subpackage. It was deleted upstream, and I do not believe anyone used it, so I think nobody will notice. Additionally, I'm not _yet_ the main admin for this package, but I expect that will change once #3672 is completed. I would like to use my provenpackager powers in the meantime to get this through as we have urgent requests through Fedora Ready that necessitate this update. I believe the scope is very small and it should be very safe to allow this exception.
Owner

+1

+1
Author
Owner

+1

+1
Owner

+1

+1
Owner

+1

+1
Owner

+1, but do you have a link to the issues? would be good to know what they are....

+1, but do you have a link to the issues? would be good to know what they are....
Author
Owner

Unfortunately no, these were privately disclosed under NDA by a Fedora Ready vendor.

Unfortunately no, these were privately disclosed under NDA by a Fedora Ready vendor.
Owner

+1

+1
Owner

+1

+1
Author
Owner

This is APPROVED (+7, 0, -0)

This is APPROVED (+7, 0, -0)
Owner

This still needs to be announced with the next meeting schedule, reopening to keep track.

This still needs to be announced with the next meeting schedule, reopening to keep track.
gotmax23 2026-08-10 18:53:58 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
7 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fesco/tickets#3673
No description provided.