© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
seems that qtmir is overriding the cursor with a "NamedCursor" as a workaround to override some cursor behavior (seems to be the way that Qt cursor names ride through the mir code). This ends up setting a 0x0 cursor, which ends up trying to create a 0x0 buffer stream, which is undefined and does not succeed (causing qtmir's starting autodetection code to fail, causing u8 to exit after that timeout expires).
Current workaround is to reset 0x0 to 1x1, which will succeed in not hanging, but leaves us with a dangling/unused 'invisible' cursor resource. Still digging around to see what we should actually be doing to support this bit of qt cursor handling.