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
ozwald1[m]1 has joined #wayland
jonahpierce has joined #wayland
jpierce has quit [Ping timeout: 480 seconds]
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
nielsdg has joined #wayland
anomalous_creator[m] has joined #wayland
jonahpierce has quit []
cb5r[m] has joined #wayland
repetitivestrain has joined #wayland
<repetitivestrain>
hello folks
<repetitivestrain>
what should the compositor do if a wl_subsurface's parent is destroyed?
<repetitivestrain>
to the surface i mean
<repetitivestrain>
i assume the surface will just be unmapped, right? and the wl_subsurface object becomes basically inert
<repetitivestrain>
but it can be destroyed and get_subsurface called for the surface again with a different surface?
<repetitivestrain>
thanks
cool110 has quit [Remote host closed the connection]
inkbottle[m] has joined #wayland
cool110 has joined #wayland
niecoinny[m] has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
vsyrjala has quit [Ping timeout: 480 seconds]
vsyrjala has joined #wayland
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
Nico has joined #wayland
ttancos[m] has joined #wayland
edrex[m] has joined #wayland
ongy[m] has joined #wayland
YaLTeR[m] has joined #wayland
Company has quit [Quit: Leaving]
DemiMarie has joined #wayland
dcz has joined #wayland
DemiMarie is now known as Guest61
dcz_ has quit [Ping timeout: 480 seconds]
Sumera[m] has joined #wayland
halfline[m] has joined #wayland
zamundaaa[m] has joined #wayland
MajorBiscuit has joined #wayland
jgrulich has joined #wayland
Major_Biscuit has joined #wayland
jgrulich has quit [Remote host closed the connection]
jgrulich has joined #wayland
MajorBiscuit has quit [Ping timeout: 480 seconds]
jryans has joined #wayland
go4godvin has joined #wayland
tinybronca[m] has joined #wayland
go4godvin is now known as Guest66
psydroid[m] has joined #wayland
MatrixTravelerbot[m]12 has joined #wayland
ppascher has quit [Quit: Gateway shutdown]
Serus has quit [Read error: Connection reset by peer]
Serus has joined #wayland
JosExpsito[m] has joined #wayland
enick_119 has joined #wayland
danvet has joined #wayland
hardening has joined #wayland
windowsxp[m] has joined #wayland
FbioPacheco[m] has joined #wayland
ahmadraniri[m] has joined #wayland
heeen[m][m] has joined #wayland
cousinofthor[m] has joined #wayland
davidre has joined #wayland
hex[m]1 has joined #wayland
rasterman has joined #wayland
Kelseyjgilbert[m] has joined #wayland
shadowninja55[m] has joined #wayland
botiapa[m] has joined #wayland
jgrulich has quit [Remote host closed the connection]
japchae[m] has joined #wayland
jgrulich has joined #wayland
zebrag has quit [Quit: Konversation terminated!]
mbalmer has joined #wayland
mvlad has joined #wayland
jgrulich has quit [Remote host closed the connection]
jgrulich has joined #wayland
jgrulich has quit [Remote host closed the connection]
jgrulich has joined #wayland
jgrulich has quit [Quit: Konversation terminated!]
jgrulich has joined #wayland
phryk has quit []
Guest61 is now known as DemiMarie
phryk has joined #wayland
Guest66 is now known as go4godvin
cool110_ has joined #wayland
cool110 has quit [Ping timeout: 480 seconds]
jmd has quit [Ping timeout: 480 seconds]
<repetitivestrain>
hello, i'm writing a wayland compositor here, and i'm wondering why weston-subsurfaces seems to complain about no buffers being available in synchronous mode
<DemiMarie>
Is it okay for a compositor to clip a subsurface to the bounds of its parent surface? I know that this violates the spec, but in some cases (ex. tiling) it would be very hard to do otherwise
<repetitivestrain>
my understanding is that state for subsurfaces is only committed when the parent is also commited
<repetitivestrain>
so for compositors that don't copy surface contents
<repetitivestrain>
the buffer previously attached to the subsurface should only be released when the parent is also commited, correct?
<repetitivestrain>
but when i implement it that way, weston-subsurfaces just crashes with
<repetitivestrain>
weston-subsurfaces -t1 -r1
<repetitivestrain>
Chosen EGL config details:
<repetitivestrain>
RGBA bits: 8 8 8 8
<repetitivestrain>
swap interval range: 0 - 1
<repetitivestrain>
shm_surface_prepare: all buffers are held by the server.
<repetitivestrain>
<repetitivestrain>
does anyone know what might be going on, or am i misunderstanding how subsurfaces are supposed to release buffers?
<emersion>
DemiMarie: yeah, there's no guarantee that a subsurface will ne fully visible on screen
<emersion>
be*
<emersion>
it could be clipped by the physical screen edge for instance
<emersion>
a reasonable thing to do is use xdg window geometry
<repetitivestrain>
anyone? i hate to repeat myself but i think i might not be able to speak here for whatever reason
<repetitivestrain>
could be an irc client bug
<DemiMarie>
I can see you.
<repetitivestrain>
phew, so it's not that
nerdopolis has joined #wayland
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
alatiera5 has joined #wayland
alatiera is now known as Guest89
alatiera5 is now known as alatiera
<kennylevinsen>
repetitivestrain: the spec says that the subsurface is unmapped when the parent is destroyed.
Guest89 has quit [Ping timeout: 480 seconds]
<kennylevinsen>
A buffer can be released by the compositor when it no longer has any use for it, regardless of reason. The commit semantics just dictate when requested changes take effect.
<repetitivestrain>
kennylevinsin: thanks
<repetitivestrain>
okay, i should clarify a little about my question
<repetitivestrain>
basically, my compositor doesn't copy anything, but it can read from the "current" (committed) buffer at any time
<repetitivestrain>
which means that buffer cannot be released until another buffer is attached to the synchronous subsurface, and the subsurface's parent is also committed
<repetitivestrain>
is this valid behavior? because weston-subsurfaces seems to choke after a few frames when i do that
arichardson[m] has joined #wayland
idkrn[m] has joined #wayland
<kennylevinsen>
whether the parent needs to be committed depends on the sync state of the subsurface
<kennylevinsen>
And things like “parent surface was destroyed” doesn’t wait on commit
<kennylevinsen>
You can use wlhax to monitor the buffers in real-time btw
Mershl[m] has joined #wayland
<repetitivestrain>
...whether the parent needs to be committed depends on the sync... yes, the subsurface in question is in synchronous mode
<emersion>
maybe you can try reproducing with weston or wlroots' pixman renderer
<repetitivestrain>
...And things like “parent surface was destroyed” doesn’t wait on... i understand that -- the question i'm asking now (as opposed to what i asked this morning) is whether or not it's okay to release the previous buffers on parent commit
<repetitivestrain>
thanks for the wlhax tip btw
<emersion>
both should keep the current buffer locked if it's wl_shm
<repetitivestrain>
i meant the buffer that's being detached due to the commit