Comment 9 for bug 2054391

I had two systems, none had more than two thermal zones.
It was enough to outline the test a bit better, but not to show the good / bad case output.

But it gave me the chance to test and install the build I had which is all fine

$ sudo apt install ./thermald_2.4.9-1ubuntu0.5_amd64.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'thermald' instead of './thermald_2.4.9-1ubuntu0.5_amd64.deb'
The following packages will be upgraded:
  thermald
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/221 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 /home/ubuntu/thermald_2.4.9-1ubuntu0.5_amd64.deb thermald amd64 2.4.9-1ubuntu0.5 [221 kB]
(Reading database ... 106221 files and directories currently installed.)
Preparing to unpack .../thermald_2.4.9-1ubuntu0.5_amd64.deb ...
Unpacking thermald (2.4.9-1ubuntu0.5) over (2.4.9-1ubuntu0.4) ...
Setting up thermald (2.4.9-1ubuntu0.5) ...
Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
Processing triggers for man-db (2.10.2-1) ...
Scanning processes...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.