ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
cvmn has quit [Remote host closed the connection]
cvmn has joined #wayland
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
Leopold__ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
Brainium has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
Leopold_ has quit [Remote host closed the connection]
Brainium has joined #wayland
Leopold_ has joined #wayland
Brainium has quit [Remote host closed the connection]
Brainium has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
ahartmetz has quit [Quit: Konversation terminated!]
eroc1990 has quit [Ping timeout: 480 seconds]
iomari892 has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
iomari891 has quit [Ping timeout: 480 seconds]
eroc1990 has joined #wayland
ciara has quit []
ciara has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
Company has quit [Quit: Leaving]
iomari892 has quit [Read error: Connection reset by peer]
iomari892 has joined #wayland
tzimmermann has joined #wayland
rv1sr has joined #wayland
iomari892 has quit [Ping timeout: 480 seconds]
dsrt^ has joined #wayland
rasterman has joined #wayland
pochu has joined #wayland
manuel_ has joined #wayland
iomari892 has joined #wayland
manuel__ has joined #wayland
manuel_ has quit [Ping timeout: 480 seconds]
crazybyte has quit [Quit: Ping timeout (120 seconds)]
<JEEB>
had that visualization of gamut demoed to me at the nhk r&d open days
<pq>
cool
<pq>
I went through colour refrence docs, and could not find it. No wonder, as the function names do not have "gamut" nor "rings" in them.
<JEEB>
fun :)
tawonga4 has quit [Quit: WeeChat 3.8]
<wlb>
weston Merge request !468 closed (ivi-shell: Set view mask solely based on source rectangle)
<qyliss>
just want to check my understanding: calling wl_display_roundtrip() here guarantees that the compositor will have received the wl_surface.commit event, generated the xdg_surface.configure event in reply, and the client listeners will have run, before wl_surface_attach() is called on the next line, right?
<qyliss>
so if wl_surface_attach() is getting called early and I get an error that the xdg_surface isn't configured yet, that means my compositor is buggy, because it's replying to the wl_display.sync before it's configured the surface?
<pq>
it's a toy example, where calling wl_display_roundtrip() in that specific context is fine.
<qyliss>
(I'm very occasionally seeing a crash because the compositor receives wl_surface.attach before xdg_surface.ack_configure)
<qyliss>
so my best guess is that this is a bug with the compositor, and it's doing things out of order, confusing the client
tawonga has joined #wayland
<pq>
xdg_surface spec says: "...perform an initial commit without any buffer attached. The compositor will reply with an xdg_surface.configure event."
<pq>
I guess that implies that a roundtrip should be enough.
<llyyr>
what compositor is this?
<pq>
I'd perhaps explicitly wait for the configure event though
<JEEB>
emersion: btw thanks for your drm DB, it lets me check before hand whether "HDR_OUTPUT_METADATA" is listed or not for a specific piece of hardware :)
<emersion>
:)
<JEEB>
I hope now with a 8550U intel I have a new enough intel to also check stuff on it, since it shows blob = <nil> there :)
<JEEB>
(Intel UHD 620)
<emersion>
that's expected, it'll only be set to non-nil if user-space has programmed it
<emersion>
the presence of the prop indicates whether the driver supports it
<emersion>
note, AMD patches have landed recently for HDR_OUTPUT_METADATA
jmdaemon has quit [Ping timeout: 480 seconds]
<pq>
you mean AMD patches for Colorspace?
<emersion>
oh, err, i mixed these up
<qyliss>
emersion: oh, so is the compositor's behaviour here actually acceptable?
i509vcb has quit [Quit: Connection closed for inactivity]
<qyliss>
is it plausible that sway could be triggering the callback before sending configure?
<jadahl>
qyliss: you cannot rely on a roundtrip to know you have received a configure event
<qyliss>
okay, so hello-wayland shouldn't do that?
<emersion>
sway sends configure immediately
jlco has joined #wayland
<jadahl>
qyliss: no, that'd be a bug
<jadahl>
qyliss: but my guess for the proxy thing is that it's something else. how does the proxy work btw? is there some libwayland-server.so server that proxies messages for a set of interfaces to the host?
<qyliss>
my understanding is that apart from XWayland, it just relays everything
<jadahl>
how does it relay things?
<qyliss>
either by directly opening a unix connection to another compositor (not very useful, I assume mostly for testing), or via virtio-gpu, where the proxy runs in the guest, and crosvm on the host connects to the host compositor
<jadahl>
qyliss: some light browsing it does seem to depend on libwayland in some way, and has a set of protocols it forwards. then a naive guess is that wl_display.sync() is implemented by libwayland-server.so, which means that it doesn't actually roundtrip all the way to the host compositor, which will break a bunch of assumptions
<qyliss>
I don't think it does
<qyliss>
I linked the code earlier where it appears to forward sync to the host
<vbt>
Hello. wayland noob here. I am adding some feature to a panel based on layer shell. i wanted to reduce the width of panel to 1px. i was told to use wp_viewporter. panel is in gtk.