This bug still exist in openSUSE Leap 42.2 with amdgpu-pro driver. Should i clone this bug-report to openSUSE Leap 42.2?