ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
sgdr has quit [Ping timeout: 480 seconds]
paulk has quit [Ping timeout: 480 seconds]
paulk has joined #wayland
mclasen has quit [Quit: mclasen]
mclasen has joined #wayland
<Consolatis>
I'd strictly differentiate between the compositor and the desktop environment though. In some cases a desktop environment also provides the compositor but in other cases that is not true.
<Consolatis>
which btw is an issue for some specific cases like for example having an up-to-date keyboard layout indicator in a panel without having keyboard focus
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
gg has joined #wayland
klausvalka has quit [Remote host closed the connection]
Company has quit [Read error: Connection reset by peer]
mclasen has quit [Quit: mclasen]
mclasen has joined #wayland
AJ_Z0 has joined #wayland
mclasen has quit [Quit: mclasen]
mclasen has joined #wayland
AJ_Z0 has quit [Ping timeout: 480 seconds]
mclasen has quit [Ping timeout: 480 seconds]
AJ_Z0 has joined #wayland
enick_190 has quit [Write error: connection closed]
furyishere[m] has quit [Write error: connection closed]
apol[m] has quit [Write error: connection closed]
danburd[m] has quit [Write error: connection closed]
hex[m]1 has quit [Write error: connection closed]
basemale has quit [Write error: connection closed]
luks2[m] has quit [Remote host closed the connection]
FbioPacheco[m] has quit [Remote host closed the connection]
drakulix[m] has quit [Write error: connection closed]
japchae[m] has quit [Write error: connection closed]
nickdiego[m] has quit [Write error: connection closed]
zaibon[m] has quit [Write error: connection closed]
rubo_[m] has quit [Write error: connection closed]
hariselldon[m] has quit [Write error: connection closed]
KingoftheElves[m] has quit [Write error: connection closed]
mboudr35[m] has quit [Write error: connection closed]
kenrendell[m] has quit [Write error: connection closed]
ErikReider[m] has quit [Write error: connection closed]
cousinofthor[m] has quit [Write error: connection closed]
arichardson[m] has quit [Write error: connection closed]
anonymousanomoly[m] has quit [Write error: connection closed]
ammen99[m] has quit [Write error: connection closed]
akallabeth[m] has quit [Remote host closed the connection]
teaper[m] has quit [Remote host closed the connection]
q234rty[m][m] has quit [Write error: connection closed]
daissi has quit [Write error: connection closed]
Eighth_Doctor has quit [Write error: connection closed]
robertmader[m] has quit [Write error: connection closed]
vchernin[m] has quit [Write error: connection closed]
unix-supremacist[m] has quit [Write error: connection closed]
RobertAyrapetyan[m] has quit [Write error: connection closed]
teh1[m] has quit [Write error: connection closed]
bdaase[m] has quit [Write error: connection closed]
heeen[m] has quit [Write error: connection closed]
wildwestrom[m] has quit [Write error: connection closed]
Z[m]123 has quit [Write error: connection closed]
Diamonditshe[m] has quit [Write error: connection closed]
Nico has quit [Write error: connection closed]
cmeissl[m] has quit [Write error: connection closed]
nep_nep has quit [Write error: connection closed]
varlad[m] has quit [Remote host closed the connection]
davidre has quit [Remote host closed the connection]
JosExpsito[m]1 has quit [Remote host closed the connection]
elinor has quit [Remote host closed the connection]
rails[m] has quit [Remote host closed the connection]
mrkzboo[m] has quit [Remote host closed the connection]
j-james[m] has quit [Remote host closed the connection]
[old]freshgumbubbles[m] has quit [Remote host closed the connection]
shawn[m]1 has quit [Remote host closed the connection]
Kelseyjgilbert[m] has quit [Write error: connection closed]
zamundaaa[m] has quit [Write error: connection closed]
botiapa[m] has quit [Write error: connection closed]
Shimmy[m] has quit [Write error: connection closed]
windowsxp[m] has quit [Write error: connection closed]
tzx[m] has quit [Write error: connection closed]
Poly[m] has quit [Write error: connection closed]
modelockedcat has quit [Write error: connection closed]
d_ed[m] has quit [Write error: connection closed]
emilio[m] has quit [Write error: connection closed]
colinmarc has quit [Write error: connection closed]
neobrain[m] has quit [Write error: connection closed]
glennk has joined #wayland
coldfeet has joined #wayland
coldfeet has quit [Remote host closed the connection]
ity has quit [Remote host closed the connection]
ity has joined #wayland
crazybyte has quit [Read error: Connection reset by peer]
crazybyte has joined #wayland
klausvalka has joined #wayland
klausvalka has quit [Remote host closed the connection]
rasterman has joined #wayland
leon-anavi has joined #wayland
kts has joined #wayland
tzimmermann has joined #wayland
kts has quit [Ping timeout: 480 seconds]
klausvalka has joined #wayland
klausvalka has quit [Remote host closed the connection]
aaron465 has joined #wayland
sima has joined #wayland
naemi4 has quit []
naemi4 has joined #wayland
naemi4 has quit []
naemi4 has joined #wayland
mart has joined #wayland
garnacho has joined #wayland
kts has joined #wayland
kts has quit [Read error: Connection reset by peer]
<KarenTheDorf>
Is it normal for a compositor to need write access to wl_shm buffers? (I noticed kwin has a fast path if they have SEAL_SHRINK, so I thought, I know, I'll try adding SEAL_FUTURE_WRITE too, and that went boom)
<emersion>
wl_shm buffers may be written to for some use-cases, e.g. screen capture
<KarenTheDorf>
True, I guess I should specifically say that it's a buffer being used to back a wl_surface. So in a general case absolutely because I could use a buffer and ask the compositor to fill it with data.
<emersion>
right, the problem is that the compositor doesn't know up-front what the buffer will be used for
iomari891 has joined #wayland
<emersion>
so kind-of needs to assume it can be used for any usage
<KarenTheDorf>
Right, that makes sense. It won't know my use case at wl_shm_pool_create_buffer time. sure, I know it will be client->server only, but the server doesn't. Thanks.
kts has joined #wayland
lbia_ has joined #wayland
lbia has quit [Ping timeout: 480 seconds]
iomari891 has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
kts has quit [Ping timeout: 480 seconds]
iomari891 has quit [Ping timeout: 480 seconds]
lbia_ has quit [Ping timeout: 480 seconds]
DonAlex has joined #wayland
<DonAlex>
garnacho, I hear you are someone who knows how to allocate touch inputs to external monitors on Wayland?
<emersion>
it depends on your compositor
<emersion>
are you using GNOME, KDE, Sway, …?
<DonAlex>
Well Gnome 3. so ?
<DonAlex>
v46
<emersion>
i think you can do it in settings
<DonAlex>
I can't see anything there?
<garnacho>
DonAlex: hey
<garnacho>
yeah, touchscreen mapping to monitors is meant to be automagic, there's a GSetting underneath though
<garnacho>
it's drawing tablets which do offer the full mapping options
<DonAlex>
I mean only mouse and touchpad but that is for the laptop I know the touch inputs are detected because if I touch the external display it moved the mouse on my primary display
<garnacho>
DonAlex: the mouse moving doesn't sound like a wayland session, though...
<DonAlex>
So which gsetting should I look at? I am familar with using dconf
<DonAlex>
Well the display is 'extended' in gnome. .but the touch movement is translated to the primary display.
<garnacho>
DonAlex: you'd need something like `gsettings set org.gnome.desktop.peripherals:/org/gnome/desktop/peripherals/touchscreens/VID:PID output "['VENDOR', 'PRODUCT', 'MODEL']" `, but that blogpost does indeed explain more in detail.
<DonAlex>
Yeah.. I tried that.. but it came back saying it had no schema ?
<garnacho>
DonAlex: I typoed mine, but whot did not. The schema should be "org.gnome.desktop.peripherals.touchscreen", the first piece of info right after "gsettings set"
iomari891 has joined #wayland
<garnacho>
that relocatable schema is defined at /usr/share/glib-2.0/schemas/org.gnome.desktop.peripherals.gschema.xml
<garnacho>
yeah, `gsettings get org.gnome.desktop.peripherals.touchscreen:/org/gnome/desktop/peripherals/touchscreens/27c0:0859 output` should tell the truth
<garnacho>
if you're sure that's the VID/PID of the touchscreen input device, it should work as far as I can see...
<DonAlex>
Same key
<DonAlex>
`gsettings get org.gnome.desktop.peripherals.touchscreen:/org/gnome/desktop/peripherals/touchscreens/27c0:0859 output
<DonAlex>
['XKY', 'Display', 'demoset-1']
<DonAlex>
Yup pretty sure that is correct Bus 001 Device 007: ID 27c0:0859 Cadwell Laboratories, Inc. TouchScreen
<garnacho>
DonAlex: that sounds like bug territory, might also be interesting to find out why it didn't get automatically mapped to the right output.
<garnacho>
I don't have an external touchscreen, but will be testing multimonitor...
<DonAlex>
Well quite.. Could just be my bad luck.. But then again it is a USB powered monitor as well so maybe that confuses it ?
<kennylevinsen>
garnacho: What does GNOME use as heuristic to associate the digitizer with the display panel?
<DonAlex>
Well this one one is super cheap but nice.. light USB powered comes with it's own kickstand
<kennylevinsen>
yes, amazon drop-shippers just hammer on the keyboard to create their continously replaced throwaway brand-names
<DonAlex>
Fairy nuff.
<garnacho>
kennylevinsen: the most relevant for touchscreens is based on reported sizes in millimeters, from the absolute coords input device and edid. There's others through libwacom, for the devices supported there.
<DonAlex>
libwacom ? Hmmmm
<garnacho>
cheap brands have a tendency to blatantly lie in those, so perhaps the GSettings escape hatch is being well used here
<garnacho>
DonAlex: is the device connected via a single cable? I wonder if it's sensitive to the connection order
<DonAlex>
Well no. one HDMI and one USB. I can do USB video but my laptop does not support it. FWIW it does show two devices in libinput. https://pastebin.com/Zxd9iWVL
<garnacho>
"Capabilities: pointer " in the second? interesting...
<garnacho>
might be worth checking which of both devices gets triggered on touch input...
<DonAlex>
Hang on just ran libinput debug-gui Will upload it so you can see the behaviour/
azerov has joined #wayland
<DonAlex>
garnacho, Here you go. If it makes and sense. Not sure why the touchpad moves on the external display but oh well https://vimeo.com/946148458
leon-anavi has quit [Remote host closed the connection]
leon-anavi has joined #wayland
mvlad has joined #wayland
<DonAlex>
oh that is kinda cool. Libinput shows how many fingers are touching and in what order.
<DonAlex>
Anyway, lunchtime here atm. So back in about an hour
tombl has quit [Remote host closed the connection]
tombl has joined #wayland
<garnacho>
DonAlex: plain text output from "libinput debug-events" might be clearer :). I forget the libinput debug-gui feedback all the time, and can't easily check on silverblue...
<garnacho>
if the output lines start with "event15", that'd be the wrong device
<YaLTeR[m]>
Is it intended when a client acks a configure dropping the resizing state but then doesn't commit, if it doesn't have anything else it wants to commit?
<YaLTeR[m]>
Resulting in the toplevel kind of hanging with the resizing state for a while
<DonAlex>
garnacho, Ok well here is a pastbin of that dragging a finger and touch up and down. https://pastebin.com/1qr8tLaw
manuel1985 has joined #wayland
<YaLTeR[m]>
How do you tell if the client committed new size after a minute in response to the last configure that dropped the resizing state, or just because it decided to change size on its own?
<YaLTeR[m]>
(in the former case the client should move on screen if it was a top-left resize, in the latter case the client should not move)
<emersion>
acks are double-buffered
<emersion>
IOW, acks have no effect until the next commit
<garnacho>
DonAlex: thanks, that looks correct... perhaps it's time for a Mutter bug report
<DonAlex>
Hmm ok
<YaLTeR[m]>
emersion: yeah exactly, and I'm seeing Firefox and Chromium just not commit their toplevel after acking a configure that dropped the resizing state (but did not request a new size). Which means that if they commit a different size in a minute, I don't know if that's their response to the last resizing commit, or if that's an unrelated new size
<emersion>
are you describing a Firefox bug then?
<jadahl>
sounds like it
<YaLTeR[m]>
I'm asking if that's a firefox and chromium bug, or if it's expected behavior that I should figure out a way to deal with
<YaLTeR[m]>
This sounds like that I want from firefox/chromium here
<YaLTeR[m]>
s/that/what
<jadahl>
firefox uses gtk3, so maybe that gtk MR fixes the firefox issue, I dunno
<YaLTeR[m]>
Electron apps also do this. So uh
<jadahl>
an ozone-wayland bug then?
<YaLTeR[m]>
I'm just thinking that since electron does this, I need at least some working around in the compositor because it ain't getting fixed for a while in apps
<mclasen>
jadahl: should I merge that gtk3 mr ? let me know
<jadahl>
mclasen: you did a month ago
<mclasen>
ah, well. Just need to get a release out
<jadahl>
yea
kts has quit [Ping timeout: 480 seconds]
f_ has joined #wayland
<pq>
Sounds like firefox and chromium might be sending their acks from configure event handlers instead of from the drawing path. That might be nice to fix, too.
rasterman has quit [Quit: Gettin' stinky!]
<kennylevinsen>
relying on paint to commit is fine assuming the configure path can schedule a forced paint...
rv1sr has joined #wayland
<jadahl>
kennylevinsen: on gtk3 I just scheduled an empty paint just for the commit
DonAlex has quit [Quit: Leaving]
iomari891 has quit [Remote host closed the connection]
mart has quit [Quit: Konversation terminated!]
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
garnacho has quit [Read error: No route to host]
garnacho has joined #wayland
iomari891 has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
Brainium has quit []
Brainium has joined #wayland
lbia_ has joined #wayland
lbia has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
privacy has joined #wayland
iomari891 has quit [Remote host closed the connection]
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
Max1 has joined #wayland
<Max1>
YaLTeR: regarding Chromium not committing after ack'ing a configure, can you please file a bug at https://issues.chromium.org/ and ping me about it?
<YaLTeR[m]>
idk if related to this specifically, but I did notice upon creating a new window chromium is a bit glitched out until the next configure
<Max1>
There have been a few changes recently which might be related to this, it might make sense to grab the latest build from https://download-chromium.appspot.com/ and test with that
Brainium has quit [Quit: Konversation terminated!]
soreau has joined #wayland
iomari891 has joined #wayland
egg_cream has joined #wayland
kts has joined #wayland
mclasen has quit [Quit: mclasen]
mclasen has joined #wayland
KarenTheDorf has quit [Remote host closed the connection]
garnacho has quit [Read error: Connection reset by peer]
<codecolla>
In both cases /stable/xdg-shell/xdg-shell.xml might be missing ls: cannot access '/stable/xdg-shell/xdg-shell.xml': No such file or directory
kts has quit [Ping timeout: 480 seconds]
<bl4ckb0ne>
did you replace the `pkgXXX` with $(shell pkgXXX)` like tinywl does
<codecolla>
Ho, once again WAYLAND_PROTOCOLS=$(shell pkg-config --variable=pkgdatadir wayland-protocols) is void
<codecolla>
pkg-config --variable=pkgdatadir wayland-protocols gives nothing in shell
<vyivel>
do you have wayland-protocols installed
<bl4ckb0ne>
do you have the wayland-protocols installed