ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
radu24284303951534727071489559 has quit [Read error: Connection reset by peer]
coldfeet has quit [Remote host closed the connection]
selckin1 has quit []
selckin has joined #wayland
<wlb>
weston Issue #906 opened by n3rdopolis (n3rdopolis) If Weston is using simpledrm, and simpledrm is replaced when Weston is inactive, Weston shows a black screen switching back to it https://gitlab.freedesktop.org/wayland/weston/-/issues/906
IwillKMS has quit [Read error: Connection reset by peer]
checkfoc_us has quit []
checkfoc_us has joined #wayland
RandomUser has joined #wayland
UsingMyPhoneAsAlt has joined #wayland
<RandomUser>
динаху
<UsingMyPhoneAsAlt>
сам йди
<IDKmyName>
чо
mclasen has quit [Ping timeout: 480 seconds]
neniagh has quit []
neniagh has joined #wayland
leon-anavi has quit [Quit: Leaving]
Narrat has joined #wayland
kenny has quit [Quit: WeeChat 4.2.2]
kenny has joined #wayland
IDKmyName has quit [Read error: Connection reset by peer]
IDKmyName has joined #wayland
mclasen has joined #wayland
IDKmyName has left #wayland [#wayland]
UsingMyPhoneAsAlt is now known as VadumAutist
iomari891 has quit [Ping timeout: 480 seconds]
VadumAutist is now known as AutisticHerbut
rasterman has quit [Quit: Gettin' stinky!]
ILoveAnal has joined #wayland
DonAlex has joined #wayland
kts has joined #wayland
<DonAlex>
Is there any update on being able to map touchscreen inputs to a specific display? It seems it detects touch events fine but applies them only to the primary display which is undesirable.
kts has quit []
ILoveAnal has left #wayland [#wayland]
<daniels>
DonAlex: which compositor are you using?
<DonAlex>
Gnome
kts has joined #wayland
<daniels>
DonAlex: you should be able to configure that in GNOME settings - if not please check on their Discourse or file an issue in their GitLab
coldfeet has joined #wayland
kts has quit [Ping timeout: 480 seconds]
kts has joined #wayland
RandomUser has quit [Quit: leaving]
kasper93 has joined #wayland
tombl_ has joined #wayland
tombl has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
tombl_ is now known as tombl
<DonAlex>
@daniels, No settings in Gnome for it. And I did not see any way to do it with gsettings
<mclasen>
DonAlex: you should talk to garnacho (who isn't here right now)
<DonAlex>
Hmmm
<DonAlex>
What timezone are they ?
<daniels>
EU
<DonAlex>
hmm ok
Brainium has joined #wayland
IDKmyName has joined #wayland
RandomUser has joined #wayland
<RandomUser>
exit
RandomUser has left #wayland [#wayland]
feaneron has quit [Remote host closed the connection]
IDKmyName has left #wayland [#wayland]
mart has quit [Quit: Konversation terminated!]
garnacho has joined #wayland
neniagh has quit []
neniagh has joined #wayland
garnacho has quit [Ping timeout: 480 seconds]
rv1sr has quit []
sgdr has joined #wayland
DonAlex has quit [Quit: Leaving]
neniagh has quit [Read error: Connection reset by peer]
neniagh has joined #wayland
lsd|2 has joined #wayland
mclasen has quit [Ping timeout: 480 seconds]
AJ_Z0 has quit [Read error: Connection reset by peer]
AJ_Z0 has joined #wayland
AJ_Z0 has quit [Read error: Connection reset by peer]
AJ_Z0 has joined #wayland
coldfeet has quit [Quit: Lost terminal]
KDDLB has joined #wayland
f_ has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
sima has quit [Ping timeout: 480 seconds]
garnacho has joined #wayland
<ids1024_>
It seems `Xwayland` relies on always getting `wl_keyboard::leave` events, even when it destroys the focused surface. (The `WAYLAND_DEBUG` log for `Xwayland` in that case on `sway` shows a `leave` with a `nil` surface). Otherwise, it doesn't send key up events for keys that were pressed when the surface was destroyed, and the next focus XWayland surface sees them as held down. This
<ids1024_>
particular behavior can be fixed by adding 3 lines to Xwayland, but is it correct to expect this from the server? It seems the protocol should be more specific on this.
lsd|2 has quit [Ping timeout: 480 seconds]
mvlad has quit [Remote host closed the connection]
lsd|2 has joined #wayland
<ids1024_>
It seems odd that a client should rely on getting a `leave` event after it has destroyed the surface, when the `surface` argument of `leave` is not nullable.
<whot>
ids1024_: sounds like an xwayland bug tbh, possibly from x assumptions where you get the leave event because the server destroys the windwow for you