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
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
c6ristian has quit [Quit: irc quit]
Consolatis_ has joined #wayland
Consolatis is now known as Guest1459
Consolatis_ is now known as Consolatis
Moprius has joined #wayland
Guest1459 has quit [Ping timeout: 480 seconds]
Moprius has quit [Quit: bye]
nyah has quit [Ping timeout: 480 seconds]
nerdopolis has quit []
nerdopolis has joined #wayland
cool110_ has joined #wayland
cool110 has quit [Ping timeout: 480 seconds]
cvmn has joined #wayland
cvmn has quit [Ping timeout: 480 seconds]
cool110_ has quit [Remote host closed the connection]
cool110 has joined #wayland
jmdaemon has joined #wayland
jgrulich has joined #wayland
rpigott has quit [Read error: Connection reset by peer]
<MrCooper>
pac85[m]: there's no fundamental difference for vsync of fullscreen windows between rootful Xwayland and Xorg
jmdaemon has quit [Quit: WeeChat 3.6]
aki237 has joined #wayland
aki237 has quit []
aki237 has joined #wayland
aki237 has quit [Remote host closed the connection]
aki237 has joined #wayland
aki237 has quit []
d42 has quit [Read error: Connection reset by peer]
mvlad has joined #wayland
nyah has joined #wayland
milesrout_ is now known as milesrout
fmuellner has joined #wayland
fahien has joined #wayland
devilhorns has joined #wayland
pac85 has joined #wayland
<pac85>
MrCooper: x stores a crtc id for each window based on which output their center lies in. When vsync is handled drmModeWaitVblank is called passing that crtc, a client is vsynced to the output it lies in. When no compositor is used and images are blitted to the front buffer vsync is therefore handled correcly (same goes for tear free where each monitor has it's own buffer and contents are copied to them individually). When a comp
<pac85>
When a compositor is used apps will still be synced correctly but the compositor will not. Rootless Xwayland has no way of syncing apps to an individual output since it only creates one window.
<MrCooper>
pac85: with Xorg, only windows which fully cover the root window can be unredirected, which is equivalent to rootful Xwayland
<pac85>
MrCooper: mmm, well still you can disable the compositor and vsync will work as it should
<MrCooper>
apart from the tearing, sure
<pac85>
MrCooper: what do you mean?
<MrCooper>
there can be tearing in that case
<pac85>
I get no tearing when using vsync under xorg, perhaps a slow enough machine would
<pac85>
Due to the fact that thinhs are front buffer rendered
<MrCooper>
we've been over this before :) it's not so much about (GPU) performance as it is about the mode timings
<pac85>
Yeah I remember that
<pac85>
But it still works in many cases, rootful xwayland just won't ever handle it
<MrCooper>
"won't ever" are bold words :)
<pac85>
Mm yeah it could be changed to handle it
<pac85>
You could have one wayland window for each screen
<MrCooper>
we've only just started exploring how rootful Xwayland could be made more useful
<MrCooper>
yep, exactly
<pq>
rootful Xwayland could probably use some life quality improvements, like allowing to specify the initial size and resize - IIRC it doesn't have these yet, right?
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
<MrCooper>
looks like you're right for the former; not sure if -decorate (which uses libdecor) covers the latter
<pq>
oh it uses libdecor nowadays, that's nice news to me :-)
<MrCooper>
the next Xwayland major release will have optional libdecor support
fahien has quit [Ping timeout: 480 seconds]
fmuellner has quit []
fmuellner has joined #wayland
cool110 has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
cool110 has joined #wayland
bittin has quit [Remote host closed the connection]
bittin has joined #wayland
pac85 has quit [Ping timeout: 480 seconds]
agners has joined #wayland
devilhorns has quit [Remote host closed the connection]
devilhorns has joined #wayland
fahien has joined #wayland
<vyivel>
should xdg-shellmake creating xdg toplevel parent-child loops an error?
<vyivel>
right now, creating a simple loop with two toplevels freezes weston
<vyivel>
and a bit more complicated setup freezes sway
<vyivel>
mutter is smart about this though
<emersion>
it really sounds like this should be an error
devilhorns has quit [Remote host closed the connection]
Lucretia has quit [Remote host closed the connection]
rv1sr has joined #wayland
Lucretia has joined #wayland
leandrohrb11 is now known as leandrohrb
<leandrohrb>
emersion: yes! I do have interest in working with dma-buf feedback for vulkan wl wsi again. I'll probably have time to revive that MR soon. I'll take a closer look, rebase and then I'll ping you.
bittin has quit [Read error: No route to host]
<emersion>
leandrohrb: thanks!
jgrulich has quit [Ping timeout: 480 seconds]
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #wayland
rgallaispou1 has quit [Read error: Connection reset by peer]
fahien has quit [Ping timeout: 480 seconds]
soreau has quit [Read error: Connection reset by peer]
carbonfiber has quit [Quit: Connection closed for inactivity]
Bhawan has joined #wayland
mk2 has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
<DemiMarie>
Can we make sure there is a nesting depth limit, and that clients know what that limit is?
<daniels>
if it's about resource consumption, they could just create an infinite number of toplevels without bothering to specify relationships between them
bittin has joined #wayland
<DemiMarie>
It’s about stack overflows in compositors
<daniels>
shrug, just pick an extremely arbitrary limit and kill the client whenever it's exceeded
<daniels>
beyond that limit the UI would be so unusable that killing the app could not possibly represent a loss
<DemiMarie>
With a `wl_display.implementation` error?