ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
feaneron has joined #wayland
Hypfer has quit [Ping timeout: 480 seconds]
fmuellner has quit [Remote host closed the connection]
Hypfer has joined #wayland
user21 has quit [Remote host closed the connection]
feaneron has quit [Ping timeout: 480 seconds]
naveenk2 has joined #wayland
garnacho has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
Brainium has joined #wayland
Moprius has quit [Remote host closed the connection]
iomari891 has quit [Read error: Connection reset by peer]
<bluetail>
Can somebody redirect me to the right place? I noticed that all my Keyboard and Mouse events are replicated at my DualShock 4 Controller as soon as it is connected. https://0x0.st/8JBb.txt
<bluetail>
I noticed that the arch wiki has some udev rules for it, but this does not "make it go away" since I am looking at it as root with sudo keyd -m
kasper93 has joined #wayland
iomari891 has joined #wayland
iomari891 has quit [Read error: Connection reset by peer]
iomari891 has joined #wayland
naveenk2 has quit [Quit: Leaving.]
<kennylevinsen>
bluetail: if the input device file is emitting events on its own, with no services running that might mess with evdev ioctl or uinput or whatever (no idea what keyd is), then it's a bug in the kernel driver
iomari892 has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
iomari892 has quit [Read error: Connection reset by peer]
iomari891 has joined #wayland
iomari891 has quit [Read error: Connection reset by peer]
iomari891 has joined #wayland
Tom^ has joined #wayland
AJ_Z0 has quit [Ping timeout: 480 seconds]
AJ_Z0 has joined #wayland
fomys has quit [Remote host closed the connection]
fomys has joined #wayland
glennk has quit [Remote host closed the connection]
glennk has joined #wayland
tzimmermann has quit [Quit: Leaving]
AJC_Z0 has joined #wayland
AJ_Z0 has quit [Read error: Connection reset by peer]
AJC_Z0 is now known as AJ_Z0
AJC_Z0 has joined #wayland
fomys has quit [Remote host closed the connection]
fomys has joined #wayland
FreeFull has joined #wayland
AJ_Z0 has quit [Ping timeout: 480 seconds]
AJC_Z0 is now known as AJ_Z0
AJ_Z0 has quit [Quit: I have to return some videotapes]
AJ_Z0 has joined #wayland
bindu_ has joined #wayland
iomari891 has quit [Read error: Connection reset by peer]
iomari891 has joined #wayland
bindu has quit [Ping timeout: 480 seconds]
iomari891 has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
cyrinux9490 has quit []
cyrinux9490 has joined #wayland
coldfeet has joined #wayland
sima has quit [Ping timeout: 480 seconds]
akimoto has joined #wayland
iomari892 has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
Drakulix has quit [Remote host closed the connection]
<bluetail>
kennylevinsen I asked in another place and they said that ds4 controllers get all events from mouse and keyboard automatically pushed through "for comfort". But if I don't want that, I can't even write a udev rule to prevent it. I would need to 'own' the device and then only allow for certain keys. That's absurd. I feel that it's potentially
<bluetail>
problematic.
<bluetail>
I am thinking that this does not comply with the Wayland model - if this is true...