Date: Sun, 22 Sep 2019 18:08:11 +0000 From: greg@unrelenting.technology To: "Vasily Postnicov" <shamaz.mazum@gmail.com> Cc: freebsd-x11@freebsd.org Subject: Re: Xorg with evdev input devices Message-ID: <81039c4b5ae0c2d4bd97dcc07852e279@unrelenting.technology> In-Reply-To: <CADnZ6BnGBZpVf9_zzoz4mV96m2DJwwDSuNHhQGn_Xnwdq=zpfQ@mail.gmail.com> References: <CADnZ6BnGBZpVf9_zzoz4mV96m2DJwwDSuNHhQGn_Xnwdq=zpfQ@mail.gmail.com> <CADnZ6B=foNChKaH6j%2Bx4pv4Z6g2ycCL7yiuLvDZSAOBHOa4ugw@mail.gmail.com> <bceb7ed1804dd98d9c186c42b08473c1@unrelenting.technology> <CADnZ6Bnzdk_kr608wg8t8Ugth%2BS8zMDy18w7KhoLWbLoBXCjJg@mail.gmail.com> <300f65b7469c608ad4cd32a9ad6c41d6@unrelenting.technology> <CADnZ6BmbYDM7Y-WQbfqQ4Y-gRv9awWS30ZtQk2Kz9tOUYXxHHw@mail.gmail.com> <320f3ff12f7aeb4eed823ea6e5eee70a@unrelenting.technology>
next in thread | previous in thread | raw e-mail | index | archive | help
September 22, 2019 8:59 PM, "Vasily Postnicov" <shamaz.mazum@gmail.com> w= rote:=0A=0A> Huh, that is quite interesting info. I had some problems wit= h OpenCL as in that bug, now they are=0A> gone. My drm-kmod version is dr= m-fbsd12.0-kmod-4.16.g20190814 (the most recent), so the problem=0A> ment= ioned is fixed. clinfo and vulkaninfo are working.=0A> =0A> But with sway= , I now see this=0A> =0A>> amdgpu_query_info(ACCEL_WORKING) failed (-13)= =0A> =0A> That is EACCES again. Looks like the bug ressurected for waylan= d at least. This message appears as=0A> I try to launch emacs (with hotke= y). I use GDK_BACKEND=3Dwayland=0A=0AYeah, Emacs GUI still requires X11 = =E2=80=94 despite being wrapped in GTK, it does a lot of raw X11 stuff.= =0A=0AThere was some porting work http://emacs.1067599.n8.nabble.com/port= ing-to-Wayland-td326678.html but looks like it's not done/merged yet.=0A= =0A> Xwayland is 1.19.1_11,1=0A> =0A> Any ideas how to fix this?=0A=0AApp= arently updating to xwayland 1.20 helps, according to the last comment in= that thread.=0A=0Ahttps://github.com/FreeBSDDesktop/freebsd-ports/tree/f= eature/xserver-1.20 =E2=86=90 the ports branch with the xorg 1.20 update= =0A=0AI haven't tested that, I've disabled xwayland completely.=0AIf that= doesn't help, that thread has my workaround patch that disables permissi= on checks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?81039c4b5ae0c2d4bd97dcc07852e279>