Re: Testing graphical applications inside mock fails

2017-09-13 Thread Adam Jackson
On Tue, 2017-09-12 at 16:34 +, Samuel Rakitničan wrote: > > 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 > > Exte

Re: Testing graphical applications inside mock fails

2017-09-12 Thread Samuel Rakitničan
> 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 devi

Re: Testing graphical applications inside mock fails

2017-09-12 Thread Samuel Rakitničan
Thank you for your detailed answer! > Short answer: > > # mknod /dev/dri/card0 c 226 0 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

Re: Testing graphical applications inside mock fails

2017-09-12 Thread Adam Jackson
On Tue, 2017-09-12 at 12:35 +, Samuel Rakitničan wrote: > Hi, > > I am trying to test graphical application inside mock chroot > environment as documented on Fedora wiki [1], but I am unable to do > that successfully. In addition to that instructions I've installed > mesa-dri-drivers and mesa-

Testing graphical applications inside mock fails

2017-09-12 Thread Samuel Rakitničan
Hi, I am trying to test graphical application inside mock chroot environment as documented on Fedora wiki [1], but I am unable to do that successfully. In addition to that instructions I've installed mesa-dri-drivers and mesa-libGL inside the chroot as there were messages about missing files. B