VladiBG Apr 7, 2021 #26 It's always good when you get response from a dev who know how the things work. Yes launching e16 with IMLIB2_SHM_OPT 1 doesn't create the fd setenv IMLIB2_SHM_OPT 1 e16 ShmCheck: x_does_shm=2 x_does_shm_fd=0 Click to expand... libxshmfence is requred by: root@x1:/home/versus # pkg info -r libxshmfence-1.3 libxshmfence-1.3: xorg-server-1.20.9_1,1 mesa-dri-20.2.3_1 mesa-libs-20.2.3 Click to expand...
It's always good when you get response from a dev who know how the things work. Yes launching e16 with IMLIB2_SHM_OPT 1 doesn't create the fd setenv IMLIB2_SHM_OPT 1 e16 ShmCheck: x_does_shm=2 x_does_shm_fd=0 Click to expand... libxshmfence is requred by: root@x1:/home/versus # pkg info -r libxshmfence-1.3 libxshmfence-1.3: xorg-server-1.20.9_1,1 mesa-dri-20.2.3_1 mesa-libs-20.2.3 Click to expand...
OP Kaminar Apr 19, 2021 Thread Starter #27 Before I'll mark this thread as solved, I have few questions about using the file descriptors in x11/libxshmfence. Why are file descriptors used for the memory sharing? In the case of E16, this leads to big inefficiency. Is there any way to disable the use of file descriptors in x11/libxshmfence similar to graphics/imlib2?
Before I'll mark this thread as solved, I have few questions about using the file descriptors in x11/libxshmfence. Why are file descriptors used for the memory sharing? In the case of E16, this leads to big inefficiency. Is there any way to disable the use of file descriptors in x11/libxshmfence similar to graphics/imlib2?
who know how the things work.