ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
hardening has quit [Ping timeout: 480 seconds]
tzimmermann_ has joined #wayland
cvmn has quit [Ping timeout: 480 seconds]
tzimmermann has quit [Ping timeout: 480 seconds]
d3x0r has joined #wayland
Seirdy has quit []
Company has quit [Read error: No route to host]
wolfshappen has joined #wayland
wolfshappen_ has joined #wayland
wolfshappen__ has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
wolfshappen has quit [Ping timeout: 480 seconds]
wolfshappen_ has quit [Ping timeout: 480 seconds]
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
wolfshappen__ has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
wolfshappen has joined #wayland
masoudd has joined #wayland
ahartmetz has quit [Quit: Konversation terminated!]
toggleton[m] has quit [Server closed connection]
toggleton[m] has joined #wayland
ujineli[m] has quit [Server closed connection]
ujineli[m] has joined #wayland
rgallaispou1 has joined #wayland
rektide has joined #wayland
rgallaispou has quit [Ping timeout: 480 seconds]
rgallaispou1 has quit [Read error: Connection reset by peer]
rgallaispou has joined #wayland
Seirdy has joined #wayland
ofourdan has quit [Server closed connection]
ofourdan has joined #wayland
soreau has quit [Read error: Connection reset by peer]
soreau has joined #wayland
niecoinny[m] has quit [Server closed connection]
niecoinny[m] has joined #wayland
duxsco has quit [Remote host closed the connection]
arichardson[m] has quit [Server closed connection]
zebrag has quit [Quit: Konversation terminated!]
arichardson[m] has joined #wayland
dcz_ has joined #wayland
zebrag has joined #wayland
zebrag has quit [Quit: Konversation terminated!]
zebrag has joined #wayland
Guest1401 is now known as DrNick
i509VCB has quit [Server closed connection]
i509VCB has joined #wayland
zebrag has quit [Quit: Konversation terminated!]
dblsaiko has quit [Server closed connection]
dblsaiko has joined #wayland
colordro1 has quit [Ping timeout: 480 seconds]
___nick___ has joined #wayland
eroux has joined #wayland
eroux has quit [Remote host closed the connection]
___nick___ has quit []
___nick___ has joined #wayland
l4s8g has joined #wayland
hardening has joined #wayland
jmdaemon has quit [Quit: WeeChat 3.4]
soreau has quit [Read error: Connection reset by peer]
soreau has joined #wayland
jmdaemon has joined #wayland
doras has quit [Server closed connection]
doras has joined #wayland
robertmader[m] has quit [Server closed connection]
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
moodman has joined #wayland
<moodman>
anyone happen to know how to send F keys through zwp_virtual_keyboard_v1?
bim9262 has quit [Ping timeout: 480 seconds]
bim9262 has joined #wayland
bim9262_ has joined #wayland
bim9262 has quit [Ping timeout: 480 seconds]
___nick___ has quit []
___nick___ has joined #wayland
___nick___ has quit []
___nick___ has joined #wayland
soreau has quit [Read error: Connection reset by peer]
l4s8g has quit []
soreau has joined #wayland
Company has joined #wayland
Company has quit [Read error: Connection reset by peer]
luc4 has joined #wayland
apol[m] has quit [Server closed connection]
apol[m] has joined #wayland
bdaase[m] has quit [Server closed connection]
bdaase[m] has joined #wayland
<any1>
Call zwp_virtual_keyboard_v1_key(..., 0, KEY_Fn, is_pressed) where n = 1 .. 10? Those constants are defined in linux/input-event-codes.h.
vchernin[m] has quit [Server closed connection]
vchernin[m] has joined #wayland
moodman has quit [Remote host closed the connection]
ttancos[m] has quit [Server closed connection]
ttancos[m] has joined #wayland
AndrewAylett[m] has quit [Server closed connection]
AndrewAylett[m] has joined #wayland
botiapa[m] has quit [Server closed connection]
botiapa[m] has joined #wayland
cousinofthor[m] has quit [Server closed connection]
cousinofthor[m] has joined #wayland
digitalfavshetheyname[m] has quit [Server closed connection]
digitalfavshetheyname[m] has joined #wayland
GrahamPerrin[m] has quit [Server closed connection]
GrahamPerrin[m] has joined #wayland
japchae[m] has quit [Server closed connection]
japchae[m] has joined #wayland
pac85[m] has quit [Server closed connection]
pac85[m] has joined #wayland
rubo_[m] has quit [Server closed connection]
rubo_[m] has joined #wayland
shadowninja55[m] has quit [Server closed connection]
shadowninja55[m] has joined #wayland
manuel1985 has joined #wayland
flacks has quit [Quit: Quitter]
flacks has joined #wayland
rasterman has joined #wayland
ahartmetz has joined #wayland
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #wayland
MajorBiscuit has joined #wayland
Major_Biscuit has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
luc4 has quit []
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #wayland
duxsco has joined #wayland
pavan has joined #wayland
jmdaemon has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
masoudd has quit [Ping timeout: 480 seconds]
masoudd has joined #wayland
duxco has joined #wayland
duxsco has quit [Ping timeout: 480 seconds]
duxco is now known as duxsco
luc4 has joined #wayland
duxsco has quit [Remote host closed the connection]
Major_Biscuit has quit []
macc24 has joined #wayland
jgrulich_ has joined #wayland
l4s8g has joined #wayland
l4s8g has quit [Remote host closed the connection]
l4s8g has joined #wayland
l4s8g_ has joined #wayland
shankaru has joined #wayland
l4s8g has quit [Ping timeout: 480 seconds]
zebrag has joined #wayland
ecloud has quit [Ping timeout: 480 seconds]
ecloud has joined #wayland
jmdaemon has joined #wayland
masoudd has quit [Ping timeout: 480 seconds]
zostj has quit []
___nick___ has quit [Ping timeout: 480 seconds]
jgrulich_ has quit [Remote host closed the connection]
wrl has quit [Server closed connection]
wrl has joined #wayland
milesrout has joined #wayland
l4s8g_ has quit []
FreeFull has joined #wayland
<FreeFull>
There's a bug involving touchpads that's been bothering me for years now, but I'm wondering how to best report it
dottedmag has quit [Server closed connection]
dottedmag has joined #wayland
<FreeFull>
Ever since I've switched from synaptics drivers to libinput many years ago, I've noticed that any program that grabs the mouse (emulators like qemu, for example), has the sensitivity be way too high when using my touchpad, but not when using a regular external mouse
<FreeFull>
I've since switched to wayland (currently using sway) and it still happens
<FreeFull>
I've also seen other people complaining about the same thing in various places on the web, but it never seems to have been reported on the libinput issue tracker
tlwoerner has quit [Ping timeout: 480 seconds]
<FreeFull>
The things I'm wondering is: Is this genuinely a libinput bug, or actually a bug in X11 and in wayland compositors? And, if it is libinput's fault, what exactly should I provide in the bug report anyway?
tlwoerner has joined #wayland
rasterman has quit [Remote host closed the connection]
glennk has quit [Server closed connection]
glennk has joined #wayland
Lyude has quit [Quit: WeeChat 3.4]
Lyude has joined #wayland
dcz_ has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
danvet has quit [Ping timeout: 480 seconds]
<FreeFull>
whot: If you're currently awake, has anyone complained directly about this issue before?
immibis has quit [Server closed connection]
immibis has joined #wayland
phryk has quit [Server closed connection]
phryk has joined #wayland
<kennylevinsen>
Is the acceleration too high for sway itself? I imagine it would be no different for the grab
<FreeFull>
Inside sway, the cursor movement is exactly as I'd like it, by default. This issue only affects grabs (that I think do some sort of relative movement) like qemu's
<FreeFull>
Changing the acceleration for the non-grabbed cursor doesn't affect the grabs at all
<FreeFull>
I am pretty certain this is not a sway bug in particular
<whot>
FreeFull: sounds like a libinput bug with the unaccelerated coordinates maybe? We fixed this a few versions ago, or at least something related to that. There's a bug with the flat acceleration too: https://gitlab.freedesktop.org/libinput/libinput/-/issues/707#note_1175215 but that's unrelated - could be that the bug you're triggering is related or has a similar cause
<whot>
FreeFull: best to file an issue anyway so we can narrow it down, first I hear about it
<FreeFull>
I am using flat acceleration but I haven't noticed any bugginess with that
<FreeFull>
Also I'm using a display scale of 1
<FreeFull>
And libinput version is 1.20.0
<whot>
FreeFull: you've noticed this with multiple compositors or just sway?
<FreeFull>
Well, the first time I've noticed it, it was actually under X11 many years ago, when I switched from synaptics to libinput there. I can quickly test inside weston right now
<FreeFull>
I can confirm it's exactly the same under Weston
<FreeFull>
So you think the TP_MAGIC_SLOWDOWN_FLAT factor might not be getting applied when programs grab the "raw" mouse data via capture?
<whot>
it's only under qemu, right?
andyrtr has quit [Server closed connection]
<whot>
could be that this is related to the relative motion interface. quick peek shows that at least weston just uses the libinput dx/dy and dx/dy_unaccelerated
andyrtr has joined #wayland
jmdaemon has quit [Ping timeout: 480 seconds]
<FreeFull>
qemu and 86box for certain, I believe I had the same issue in other similar programs too
<FreeFull>
And that's definitely possible
<whot>
and the latter ones are "raw" coordinates - i.e. they're not just "no acceleration applied" because that concept is a bit difficult inside libinput
<whot>
and they're in the resolution of the device, where applicable, so you'll get different results depending on the touchpad
<whot>
a slow motion on my touchpad here gives me this in libinput debug-events:
<whot>
which means that if you think the unaccelerated data can be handled the same way as the dx/dy (narrator: it can't) then you'd get 3 times the speed
luc4 has quit []
<whot>
right now, that's my best guess as to where that speedup comes from
<whot>
as to how to fix it - more tricky, not sure yet and the coffee hasn't kicked in
<FreeFull>
I'll try to check which kind of coordinates 86box uses
<FreeFull>
Seems it's using relative mouse events
<whot>
FreeFull: can you file a libinput issue for this please, with a libinput debug-events output attached so it's easy to see what the scale is (and libinput record as usual)
fmuellner has joined #wayland
<whot>
FreeFull: then we can narrow it down there what is happening and how to fix it, because right now it seems like there's too much blu tack involved
<FreeFull>
What should I do with the touchpad while running libinput record? Have 86box capture it and move it around a bit?
<whot>
libinput record captures the kernel events directly, doesn't matter what you run on top of it
hardening has quit [Ping timeout: 480 seconds]
<FreeFull>
So just wiggle my finger a bit and then stop the capture?
<whot>
yeah, just a normal movement, not fast, not creepingly slow
<whot>
or actually, maybe a movement that starts super-slow and then goes up to fast, that should show the range of the scale
<FreeFull>
Alright
<FreeFull>
Problem with debug-events, I've got a physically broken touchscreen that constantly spams events
<FreeFull>
I've currently got it disabled in my compositor, but probably should figure out a more global way of disabling it
jmdaemon has joined #wayland
jmdaemon has quit []
<whot>
FreeFull: debug-events takes a /dev/input/eventX argument if need be