Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Sep 2019 16:31:54 +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:  <300f65b7469c608ad4cd32a9ad6c41d6@unrelenting.technology>
In-Reply-To: <CADnZ6Bnzdk_kr608wg8t8Ugth%2BS8zMDy18w7KhoLWbLoBXCjJg@mail.gmail.com>
References:  <CADnZ6Bnzdk_kr608wg8t8Ugth%2BS8zMDy18w7KhoLWbLoBXCjJg@mail.gmail.com> <CADnZ6B=foNChKaH6j%2Bx4pv4Z6g2ycCL7yiuLvDZSAOBHOa4ugw@mail.gmail.com> <bceb7ed1804dd98d9c186c42b08473c1@unrelenting.technology>

next in thread | previous in thread | raw e-mail | index | archive | help
September 22, 2019 7:12 PM, "Vasily Postnicov" <shamaz.mazum@gmail.com> w=
rote:=0A=0A> Thanks, it works. The purpose of my evdev kernel support tes=
ting is eventually switch to wayland.=0A> For this time I have all relate=
d ports recompiled with WAYLAND option and also have x11-wm/sway=0A> inst=
alled. Then I run following commands in terminal (I mean, without xorg se=
rver running):=0A> =0A>> setenv XDG_RUNTIME_DIR /tmp=0A> =0A>> sway -d=0A=
> =0A> Sway fails to start with the following log: https://pastebin.com/M=
3eExb0C=0A> =0A>> 2019-09-22 18:53:04 - [backend/libinput/backend.c:55] I=
nitializing libinput=0A>> 2019-09-22 18:53:04 - [backend/libinput/backend=
.c:84] libinput initialization failed, no input=0A> devices=0A>> 2019-09-=
22 18:53:04 - [backend/libinput/backend.c:85] Set WLR_LIBINPUT_NO_DEVICES=
=3D1 to suppress=0A> this check=0A>> 2019-09-22 18:53:04 - [backend/multi=
/backend.c:32] Failed to initialize backend.=0A>> 2019-09-22 18:53:04 - [=
sway/server.c:195] Failed to start backend=0A> =0A> I've tried to run "se=
tenv WLR_LIBINPUT_NO_DEVICES 1" as suggested and got sway started (but wi=
thout=0A> input devices, I suppose). What's wrong with my libinput? It se=
ems it works OK with Xorg=0A=0AYour sway process doesn't have permission =
to access /dev/input/*.=0A=0A[re: the little follow-up email: setuid does=
 not help, because input devices are attached after dropping root, becaus=
e input devices need to be hotpluggable anyway. setuid is bad, use consol=
ekit2 as described below]=0A=0AThe good (but a bit involved for now) fix:=
=0A=0A- run 'sysctl kern.evdev.input' to make sure you have a recent enou=
gh kernel -- my patch for this is not in 12.0-RELEASE, but should be in 1=
2.1-BETA I'm pretty sure=0A- build libudev-devd with https://github.com/m=
yfreeweb/freebsd-ports-dank/blob/lite/devel/libudev-devd/Makefile (i.e. u=
pdate to the latest git commit)=0A- build consolekit2 with https://review=
s.freebsd.org/D18754=0A- build wlroots with CONSOLEKIT option=0A- enable =
automatic CK2 session creation on login: add 'session         optional   =
     pam_ck_connector.so' to the '# session' section of /etc/pam.d/login=
=0A- log out, log in, just run sway=0A- (you can launch sway under ck-lau=
nch-session if the automatic session gets screwed up somehow, but it work=
s for me pretty well)=0A=0AThe bad (but quick) fix:=0A=0A- chmod/chown /d=
ev/input/* to be accessible to your account=0A- (there's some devfs confi=
g thing that can do this automatically)=0A- (this exposes input devices t=
o any program running as your account, which defeats the "no keyloggers a=
llowed" advantage of wayland)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?300f65b7469c608ad4cd32a9ad6c41d6>