FYI:
.msg<Main>: 0xaaaa0002=FOCUS_RECEIVED (0x63000020, 0)
.msg<Main>: 0xaaaa0001=FOCUS_LOST (0x63000020, 0)
.msg<Main>: 0xaaaa0002=FOCUS_RECEIVED (0x63000007, 0)
.msg<Main>: 0xaaaa0001=FOCUS_LOST (0x63000007, 0)
.msg<Main>: 0xaaaa0002=FOCUS_RECEIVED (0x63000006, 0)
.msg<Main>: 0xaaaa0001=FOCUS_LOST (0x63000006, 0)
.msg<Main>: 0xaaaa0002=FOCUS_RECEIVED (0x63000005, 0)
.msg<Main>: 0xaaaa0001=FOCUS_LOST (0x63000005, 0)
.msg<Main>: 0xaaaa0002=FOCUS_RECEIVED (0x63000004, 0)
.msg<Main>: 0xaaaa0001=FOCUS_LOST (0x63000004, 0)
these are in fact messages from the "Main" application that gets dumped to the linux console, when hovering and focusing on UI elements in the sh3 menu, these are NOT errors.
As I have the flickering too with AMDGPU driver I tested my intel onboard driver (which worked fine with sh3 some month back), and I have no flickering / errors there.
Intel drivers for my HD4600 card now support exactly the same OPENGL levels as AMDGPU , so there should be a bug in AMDGPU driver (that incidentally is now used by AMDGPU Pro proprietary driver), I will try to revert to older mesa drivers and dissect and report this issue to the mesa developers if possible.
Hope that does not count as necroposting here (sorry), but this thread actually turns up first when searching for the problem...
cheers.
