> Thank you for your detailed answer! > > > The error messages about drm device are gone if I manually create the character file > inside the chroot. However the original issue remains the same. Tried a GTK application > easystroke however and that seems to work fine even without a drm device, so maybe it has > to do something with Qt. The Qt application camotics gives a bunch of these messages. > > X Error: BadAccess (attempt to access private resource denied) 10 > Extension: 130 (MIT-SHM) > Minor opcode: 1 (X_ShmAttach) > Resource id: 0x131 > X Error: BadShmSeg (invalid shared segment parameter) 128 > Extension: 130 (MIT-SHM) > Minor opcode: 5 (X_ShmCreatePixmap) > Resource id: 0x280005f > X Error: BadDrawable (invalid Pixmap or Window parameter) 9 > Major opcode: 62 (X_CopyArea) > Resource id: 0x2800060 > X Error: BadDrawable (invalid Pixmap or Window parameter) 9 > Major opcode: 62 (X_CopyArea) > Resource id: 0x2800060 > X Error: BadDrawable (invalid Pixmap or Window parameter) 9 > Major opcode: 62 (X_CopyArea) > Resource id: 0x2800060 > ... QT_X11_NO_MITSHM=1 helps with these, though. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
