ID 598531 - The pass of a lookfile in the LookFileManager can not be interacted with or viewed and reports an error

Follow

Problem summary
The pass of a lookfile in the LookFileManager can not be interacted with or viewed and reports an error
 
Customer reported version
Katana 7.0v6
 
Customer reported platform
RHEL 9
 
Steps to reproduce
 
1) In Katana, create a lookfile via LookFileBake.

2) Create a LookFileManager node, right-click the Look Files section and select Advanced > Add Lookfile Using Browser...

3) Import your created look file, double click the default pass inside the pass section and observe the error.
 
Expected behaviour
Be able to select and view the pass of the loaded lookfile.
 
Actual behaviour
The pass is uninteractable and reports the following error:

[ERROR python.Uncaught Exception]: Traceback (most recent call last):File "Widgets/SortableListWidget.py", line 132, in mousePressEventFile "Widgets/SortableListWidget.py", line 508, in hitTestTypeError: arguments did not match any overloaded call:QRect(): too many argumentsQRect(int, int, int, int): argument 2 has unexpected type 'float'QRect(QPoint, QPoint): argument 1 has unexpected type 'int'QRect(QPoint, QSize): argument 1 has unexpected type 'int'QRect(QRect): argument 1 has unexpected type 'int'
 
Workaround
Unknown.
 
Reproduced by support
 
This bug has been reproduced in:
Katana 7.0v6 - Rocky 9 / Windows 11
Katana 7.0v4 - Rocky 9 / Windows 11
 
Unable to reproduce bug in:
Katana 6.5v6 - Rocky 9 / CentOS7 / Windows 11 (DeprecationWarning)
Katana 6.5v5 - Rocky 9 / CentOS7 / Windows 11 (DeprecationWarning)
Katana 6.0v5 - Rocky 9 / CentOS7 / Windows 11 (DeprecationWarning)
 
Below is the DeprecationWarning produced when following the reproduction steps mentioned above:
[WARN python.py.warnings]: Widgets/SortableListWidget.py:508: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python.
 
Earliest version tested
Katana 6.5v6 - This issue doesn't appear in this version and has regressed
 

    We're sorry to hear that

    Please tell us why