ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
Brainium has quit [Quit: Konversation terminated!]
Narrat has quit []
Moprius has quit [Quit: bye]
Moprius has joined #wayland
Moprius has quit []
Brainium has joined #wayland
ramblurr_ has joined #wayland
ramblurr has quit [Ping timeout: 480 seconds]
ramblurr_ is now known as ramblurr
rv1sr has quit []
rgallaispou has quit [Ping timeout: 480 seconds]
karenw has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
kts has joined #wayland
sima has joined #wayland
karolherbst4 has quit []
karolherbst has joined #wayland
garnacho has quit [Ping timeout: 480 seconds]
sima has quit [Ping timeout: 480 seconds]
mxz_ has joined #wayland
mxz has quit [Ping timeout: 480 seconds]
mxz__ has quit [Ping timeout: 480 seconds]
mxz_ is now known as mxz
kts has quit [Ping timeout: 480 seconds]
kts has joined #wayland
bodiccea has joined #wayland
bodiccea_ has quit [Ping timeout: 480 seconds]
pavlushka has joined #wayland
<pavlushka>
issues with copy pasting, how do I do it?, copy pasting between gui windows
pavlushka has quit [Remote host closed the connection]
garnacho has joined #wayland
WhyNotHugo has quit [Remote host closed the connection]
rv1sr has joined #wayland
WhyNotHugo has joined #wayland
kts has joined #wayland
narodnik has joined #wayland
narodnik has quit [Quit: WeeChat 4.5.0]
kts has quit [Ping timeout: 480 seconds]
mriesch_ has joined #wayland
mriesch has quit [Ping timeout: 480 seconds]
narodnik has joined #wayland
mriesch_ has quit []
mriesch has joined #wayland
glennk has joined #wayland
__monty__ has joined #wayland
<__monty__>
Does libinput debug-events bypass the configuration just as debug-gui does? I'm trying to troubleshoot why middle click won't close Firefox tabs for me. Middle drag works for OpenBox but middle click doesn't. Yet debug-events does show middle click events.
<vyivel>
__monty__: device configuration is per-context, yes
<vyivel>
my guess is a compositor-specific setting or a bug, try with some other compositor to confirm
<__monty__>
Documentation for debug-gui says to pass flags like `--enable-tap` to debug your user configuration but my debug-events does not accept such flags. Or is that not what you mean when you say context?
<vyivel>
i mean that device configuration is applied within a specific program
<vyivel>
like, a compositor is a libinput user, it supplies device configuration from its settings or whatever
<vyivel>
"libinput debug-events" is another libinput user, it doesn't supply device configuration and therefore gets different results from same devices
<__monty__>
Wait, are we talking Wayland compositor? Given the channel I understand the assumption but I'm using Libinput with X, so wouldn't X be my compositor?
<vyivel>
…ah
<vyivel>
hm, idk then
<vyivel>
check with xev if the button is correct
<__monty__>
In xev I only get NotifyGrab and NotifyUngrab events, no button2 click.
<vyivel>
i suppose this means that openbox overrides the middle press action
<vyivel>
because it should be just Button{Press,Release} with button 2
<__monty__>
It does have bindings for middle press that do work, but its default binding for middle click doesn't.
<vyivel>
i'm afraid i'm not familiar with how openbox mouse bindings work
<vyivel>
that being said, doesn't seem to be a libinput-related issue
<vyivel>
try asking in a some openbox space
<__monty__>
OK, thanks for helping to narrow it down.
<whot>
__monty__: in X the xf86-input-libinput driver has the libinput context
<whot>
the rest still applies, think of libinput as a fancy grep on the device node, starting another grep (like libinput debug-events) is not going to affect the already running one
<whot>
from libinput's POV there's no configuration other than what's set at runtime and that's handled by whatever has the context - in the xorg driver case it translates from xorg.conf into the libinput API calls
<whot>
debug-events only translates getopt to api calls
<karenw>
Oh yeah, MS has a wayland server. I keep forgetting that in WSL because the wayland socket is in some random directory no app can find.
Narrat has joined #wayland
<bluetail>
you make it sound like a dare
karenw has quit [Quit: Segmentation Fault (Core Dumped)]
karenw has joined #wayland
rasterman has joined #wayland
narodnik has quit [Ping timeout: 480 seconds]
karenw has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
tent405 has joined #wayland
narodnik has joined #wayland
narodnik2 has joined #wayland
narodnik has quit [Read error: No route to host]
lsd|2|2 has quit [Ping timeout: 480 seconds]
narodnik2 has quit []
narodnik has joined #wayland
narodnik has quit []
narodnik has joined #wayland
narodnik has quit [Read error: No route to host]
narodnik has joined #wayland
narodnik has quit []
karenw has joined #wayland
___nick___ has quit [Remote host closed the connection]
narodnik has joined #wayland
Brainium has joined #wayland
melnary has quit [Read error: Connection reset by peer]
melnary has joined #wayland
kenny has quit [Quit: WeeChat 4.4.4]
rgallaispou has joined #wayland
nerdopolis has joined #wayland
lsd|2|2 has joined #wayland
lsd|2|2 has quit []
iomari891 has joined #wayland
coldfeet has quit [Quit: Lost terminal]
rgallaispou has quit [Ping timeout: 480 seconds]
shymega[i] has joined #wayland
rasterman has joined #wayland
yrlf has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
<whot>
__monty__: if you're on X then typically the desktop environment changes the settings of the xf86-input-* driver, so the actual settings are in e.g. gsettings for gnome
<whot>
but the short answer is: if you get NotifyGrab that means something has a grab on the button so it effectively gets intercepted