log file: 00:00:00.000 [INFO] [sway/main.c:338] Sway version 1.9 00:00:00.000 [INFO] [sway/main.c:339] wlroots version 0.17.4 00:00:00.005 [INFO] [sway/main.c:120] OpenBSD Dagobah.lan 7.6 GENERIC.MP#338 amd64 ... 00:00:00.195 [DEBUG] [wlr] [backend/libinput/events.c:70] Adding wskbd0 [0:0] 00:00:00.195 [DEBUG] [sway/input/input-manager.c:235] adding device: '0:0:wskbd0' 00:00:00.195 [DEBUG] [sway/input/seat.c:975] adding device 0:0:wskbd0 to seat seat0 00:00:00.204 [DEBUG] [sway/input/keyboard.c:908] Created keyboard group 0x20f648aee00 00:00:00.204 [DEBUG] [sway/input/keyboard.c:932] Adding keyboard 0:0:wskbd0 to group 0x20f648aee00 00:00:00.206 [DEBUG] [wlr] [backend/libinput/backend.c:127] libinput successfully initialized
log file doesn't have a keyboard error this time. But, the group id is different each time it launches. I'm not sure what number it should be. When I run `startsway.sh` my keyboard only writes to the tty now. It does not send input to the sway session. But, it technically works on the tty. The mouse works fine. On Tue, Oct 1, 2024 at 1:04 AM Matthieu Herrb <[email protected]> wrote: > On Mon, Sep 30, 2024 at 11:06:43PM -0600, Kalen Romansky wrote: > > >Synopsis: pkg libinput-openbsd, used in sway, returns keyboard type > > XT instead of USB > > >Category: sway, wayland, libinput-openbsd > > >Environment: > > System : OpenBSD 7.5 > > Details : OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 > MDT > > 2024 > > [email protected]: > > /usr/src/sys/arch/amd64/compile/GENERIC.MP > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > From a fresh boot, I run startsway.sh to launch the sway window > > manager under with wayland. > > It emits the following debug log from sway. > > Hi, > > Sway/wayland support is very much a work in progress. There have been > some work in the keyboad area since 7.5 was released. > > Please try a snapshot (or wait one week or so for the 7.6 release) and > report back if the issue is still present. > > -- > Matthieu Herrb >
