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
hergertme_ has joined #wayland
mclasen_ has joined #wayland
co1umbarius has joined #wayland
hergertme has quit [Ping timeout: 480 seconds]
mclasen has quit [Ping timeout: 480 seconds]
columbarius has quit [Ping timeout: 480 seconds]
alarumbe has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
CME has quit []
CME has joined #wayland
cool110_ has quit [Remote host closed the connection]
cool110 has joined #wayland
emery has quit [Ping timeout: 480 seconds]
emery has joined #wayland
Company has quit [Quit: Leaving]
nerdopolis has quit [Ping timeout: 480 seconds]
shankaru has joined #wayland
shankaru has quit []
tzimmermann has joined #wayland
mclasen has joined #wayland
mclasen_ has quit [Ping timeout: 480 seconds]
hardening has joined #wayland
jgrulich has joined #wayland
rv1sr has joined #wayland
mclasen has quit [Ping timeout: 480 seconds]
danvet has joined #wayland
MajorBiscuit has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
mvlad has joined #wayland
<pq>
kchibisov, if Mesa is adding something behing the app's back, it needs to make it work behind the app's back too. IMO. So I'd say Mesa needs to add the damage itself.
bindu has quit [Remote host closed the connection]
bindu has joined #wayland
juergbi has quit []
MajorBiscuit has quit [Ping timeout: 480 seconds]
juergbi has joined #wayland
MajorBiscuit has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #wayland
Company has joined #wayland
fmuellner has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #wayland
fmuellner has quit [Remote host closed the connection]
flacks_ has quit [Quit: Quitter]
MajorBiscuit has quit [Ping timeout: 480 seconds]
flacks has joined #wayland
rv1sr has quit []
CuteMath has joined #wayland
alarumbe has joined #wayland
MajorBiscuit has joined #wayland
CuteMath has quit [Quit: Leaving]
CuteMath has joined #wayland
<CuteMath>
Hello. I've bound the wl_seat object and got the keyboard object from it. I don't see any keymap event been fired though. Is it guaranteed to be sent?
tlwoerner has joined #wayland
<pq>
CuteMath, I believe it is, at least if the seat has keyboard capability. Do you "wait" for it?
<pq>
Do you enter your main event loop, and it still never arrives?
<CuteMath>
I do enter the main loop and I get key events, but the keymap event does not get fired.
<pq>
That's very odd. What's the compositor you're running on?
<pq>
CuteMath, you might want to ask from the Sway community about this, and maybe try on a different compositor to see if it's a compositor bug.
<CuteMath>
I've already asked on the sway chat, no response for now. I'll try another compositor.
<CuteMath>
Tried wayfire 0.7.3.1 from AUR. No keymap as well. I'll try to reduce the code to the minimum before anything else. Dunno if I am doing something wrong.
<pq>
you could be forgetting to set up the keyboard listener, but OTOH you do get key events, and leaving a function pointer to NULL would crash.
<pq>
and plugging a wrong function should produce compiler warnings
<CuteMath>
keyboard listener is indeed set and I pass the correct function.
<pq>
hard to guess what else it could be
<any1>
maybe running with WAYLAND_DEBUG=1 would shed some light on the problem?
<pq>
In the client that has the caveat that it only prints events that has a handler set; more reliable would be to use that on the compositor to see if the compositor sends the event.
* any1
thinks it's very unlikely to be a compositor issue
<pq>
yes, unless there is some kind of "too old wl_keyboard version, no keymaps for you"
<pq>
I don't know if anyong does that, but I do recall issues with keymap fd sharing that requires extra work from the compositor to address.
<CuteMath>
Ok, something strange just happened. I went back to wayfire (Ctrl-Alt-F2) and I saw some keymap events been received
<pq>
Are you perhaps running your clients while VT-switched away from the compositor?
<CuteMath>
what do you mean by "VT-switched away"?
<pq>
you said Ctrl-Alt-F2, that's usually for VT-switching
<any1>
Or maybe the event loop is being blocked somewhere, and switching back and forth generates some events that free it up?
<any1>
Recommend running with strace to see
<CuteMath>
sway does not fire keymap events when switching from wayfire to sway
rv1sr has joined #wayland
CuteMath has quit [Remote host closed the connection]
tzimmermann has quit [Remote host closed the connection]
<ifreund>
CuteMath: it looks like you're making the get_keyboard request before the compositor sends wl_seat.capabilities
<CuteMath>
oh shoot
<CuteMath>
that fixes it, thanks guys
<ifreund>
wlroots should have been hitting you with a missing_capability protocol error tbh
<ifreund>
ah, I guess it's a race condition
caveman has joined #wayland
cabal704 has joined #wayland
<CuteMath>
ifreund, should I report it?
<CuteMath>
oh, I don't have a display listener. I should have set one.
<CuteMath>
doesn't seem to send me an error event when getting the keyboard before handling the capabilities event, dunno if it is correct
<pq>
CuteMath, you can't set a listener on wl_display, that's handled inside libwayland-client.
<pq>
libwayland-client has API to get the protocol error if any happens, but you cannot "forget" it, because a protocol error will always disconnect the client.
<CuteMath>
yeah thought so, I did that out of habits because I have written a client library some time ago. I see I see
rv1sr has quit [Remote host closed the connection]
tzimmermann has quit [Remote host closed the connection]