I have verified that the updated package fixes this bug.
I reproduced this issue in a fresh Ubuntu 22.10 container by following the test plan from the original bug description with kinetic-proposed enabled (but with no proposed packages installed). The call to rocminfo crashed as expected. I then installed libhsa-runtime64-1/kinetic-proposed and verified that the rocminfo output was correct.
The details of this testing (including details about the hardware used) can be found in the attached log.
I have verified that the updated package fixes this bug.
I reproduced this issue in a fresh Ubuntu 22.10 container by following the test plan from the original bug description with kinetic-proposed enabled (but with no proposed packages installed). The call to rocminfo crashed as expected. I then installed libhsa- runtime64- 1/kinetic- proposed and verified that the rocminfo output was correct.
The details of this testing (including details about the hardware used) can be found in the attached log.