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
nerdopolis has quit [Ping timeout: 481 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
jmdaemon has quit [Remote host closed the connection]
jmdaemon has joined #wayland
devilhorns has joined #wayland
devilhorns has quit []
remanifest has joined #wayland
duxsco has quit [Quit: duxsco]
MrCooper_ has joined #wayland
MrCooper has quit [Read error: Connection reset by peer]
nerdopolis has quit [Ping timeout: 480 seconds]
remanifest has quit [Remote host closed the connection]
remanifest has joined #wayland
shashank_sharma has joined #wayland
shashanks has quit [Ping timeout: 480 seconds]
agd5f has quit [Remote host closed the connection]
agd5f has joined #wayland
Ariadne has quit [Read error: Connection reset by peer]
Ariadne has joined #wayland
UndeadLeech has quit [Quit: Critical System Error]
UndeadLeech has joined #wayland
reillybrogan has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
reillybrogan has joined #wayland
aswar002 has quit [Quit: No Ping reply in 180 seconds.]
shashanks has joined #wayland
aswar002 has joined #wayland
shashank_sharma has quit [Ping timeout: 480 seconds]
shashanks has quit [Ping timeout: 480 seconds]
remanifest has quit []
zebrag has quit [Quit: Konversation terminated!]
Company has quit [Read error: Connection reset by peer]
danvet has joined #wayland
shankaru has joined #wayland
naveenk2 has joined #wayland
dcz_ has joined #wayland
jgrulich has joined #wayland
flacks has quit [Ping timeout: 480 seconds]
flacks has joined #wayland
maxzor has joined #wayland
mvlad has joined #wayland
codecolla has joined #wayland
hardening has joined #wayland
naveenk2 has quit [Ping timeout: 480 seconds]
naveenk2 has joined #wayland
<kennylevinsen> any1: not peeping on buffer content, but seeing which buffers exist, their type, their size and what it's being used for
<kennylevinsen> Same for viewports
quantum5 has quit [Quit: ZNC - https://znc.in]
quantum5 has joined #wayland
<jadahl> kennylevinsen: no ascii art representation?
<emersion> yeah, next step is definitely a libcaca display
<jadahl> anything less would be dissapointing
<kennylevinsen> be careful what you wish for :P
<jadahl> with special unicode magic, it can be just as pixel perfect as fractional scaling
Arnavion has quit [Ping timeout: 480 seconds]
Arnavion has joined #wayland
<zzag> jadahl: pff, ascii art is so yesterday; today, it's all about blockchains.. we demand blockchain support! don't worry about security, it's all cryptography so it's safe
<jadahl> wp_bitcoin_wallet_v1?
ts has joined #wayland
<emersion> wp_nft_buffer_v1
<zzag> I would argue that it needs to be "xdg" rather than "wp" because no person would be able to live without it
<emersion> "wp" is stronger than "xdg"
<jadahl> ext_bitcoin_wallet_v1 and wp_nft_buffer_v1 seems like a plan
codecolla has quit []
<DemiMarieObenour[m]> On the topic of silly protocols, there could be wp_network_connect_v1, wp_dbus_v1, and wp_audio_v1
lxsameer2 has joined #wayland
<dottedmag> wp_tcp_v1
<dottedmag> To avoid a crazy maze of specialized protocols
jmdaemon has quit [Ping timeout: 480 seconds]
<vyivel> wp_x11
<vyivel> to simplify porting x11 programs to wayland, i suppose
rasterman has joined #wayland
<columbarius> wp_haiku_v1 implementing is_computer_on_fire
<DemiMarieObenour[m]> I actually did propose tunneling X11 in Wayland at one point. It was to avoid some sort of race condition in XWayland.
<ofourdan> iirc, it wasn't a race condition, it was about the fact that wayland compositors with Xwayland support are Xwayland clients, which itself is a Wayland client, so more about potential deadlocks
<ofourdan> ah
mceier has quit [Ping timeout: 480 seconds]
* kennylevinsen opens the chat again just to see nft buffers
<kennylevinsen> "why is the frame rate so bad" "because there's not enough people mining dogecoin!"
<kennylevinsen> Or Ethereum or whatever the cool kids use these days
txtsd has joined #wayland
duxsco has joined #wayland
___nick___ has joined #wayland
ts has quit []
fmuellner has joined #wayland
<DemiMarieObenour[m]> Amazingly, Thomas Leonard managed to implement XWayland without special compositor support.
<DemiMarieObenour[m]> I certainly thought it was impossible, but he managed to actually do it.
<pq> If it's rootless and did not patch Xwayland nor add new Wayland extensions, it sounds amazing indeed.
<pq> How does it work?
<pq> a full-screen fully transparent wl_surface as a parent in order to achieve client-side global positioning?
<pq> an X11 compositing manager relaying X11 window contents to Wayland instead of letting Xwayland deliver them?
<pq> DemiMarieObenour[m], that link does not say anything about Xwayland that I can see, just that it is TBD.
<wlb> wayland-protocols Merge request !145 opened by () WIP: wp-surface-scale-v1: new protocol https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/145
<DemiMarieObenour[m]> pq: That’s the next post: https://roscidus.com/blog/blog/2021/10/30/xwayland/
<pq> :-(
<pq> I wish you pointed me to that first.
<DemiMarieObenour[m]> Sorry about that, my mistake
<DemiMarieObenour[m]> Sorry for wasting your time pq
<emersion> it's possible to a degree
<emersion> kind of a shame this is written in ML tbh
<DemiMarieObenour[m]> Why is it a shame?
<emersion> i like boring stuff
<DemiMarieObenour[m]> OCaml isn’t exactly a new language; it’s been around since 1996.
<emersion> OCaml screams "oh look at this fancy code construct"
<emersion> but my bad, this is off-topic for this channel
txtsd has quit [Ping timeout: 480 seconds]
<pq> It is an impressive body of work.
<pq> It's based on guessing the X11 window types and states and mirroring those via xdg-shell, with quirks here and there to make the Wayland interchange legal.
<ofourdan> thomas leonard of Rox fame?
<pq> The post didn't really go into the details of window positioning, especially O-R positioning, which I would have assumed to be a pretty big problem.
<DemiMarieObenour[m]> pq: That would be my assumption too. I suspect it gets translated to a popup, but I am not certain.
<DemiMarieObenour[m]> ofourdan: I am not sure what Rox is, but I do know he is the creator of 0install, a contributor to MirageOS, and the discoverer of at least one vulnerability in Xen’s ARM port.
<ofourdan> yeah, same person
<pq> DemiMarieObenour[m], he mentioned using various heuristics in trying to detect what to do with each O-R window. I suppose it works surprisingly well for the apps he uses.
<kennylevinsen> I imagine it is not dissimilar to what wine needs to do
<pq> yup
<DemiMarieObenour[m]> kennylevinsen: Probably almost the same, except somewhat easier because most X11 applications use a toolkit.
<DemiMarieObenour[m]> Some of it probably turns into per-application hacks, but that is probably a minority.
<DemiMarieObenour[m]> And the payoff is worthwhile
<vyivel> heh, had the same "rootlees x11 wm" idea a while ago, although x11->wayland DnD would still require compositor to play along
<pq> the post mentions the same problem with DnD
d_ed has joined #wayland
<wlb> wayland Issue #287 opened by () Optional knob to shuffle wl_signal_add ordering https://gitlab.freedesktop.org/wayland/wayland/-/issues/287
<DemiMarieObenour[m]> <pq> "the post mentions the same..." <- In Qubes OS, the current plan for DnD is to not support it at all.
<kennylevinsen> Yeah that won't work for general compositors
<DemiMarieObenour[m]> It’s not that I don’t want to support it, but rather that I am not aware of a good way to support it properly, and only supporting it within a single VM just leads to confusion.
manuel1985 has joined #wayland
<qyliss> when I used Qubes OS for the first time, being able to drag and drop only within a single VM was actually the thing that made me understand the concept of Qubes OS, and the separation of VMs
<DemiMarieObenour[m]> That is interesting qyliss!
<qyliss> (I understand why it would be confusing for other people though)
<DemiMarieObenour[m]> The problem with the current situation isn’t just that one can’t drag and drop between qubes, but that it is very easy to drop onto the wrong window. If dropping onto a window owned by a different VM gave a useful error, that would be okay. Right now, however, it will either do nothing or (worse) drop onto whatever window in the same VM happened to be there at the time, even if that window was hidden by a window from a
<DemiMarieObenour[m]> different VM! This is not only surprising, but also a legitimate security problem. I have dropped text from a chat window into a terminal more than once.
<DemiMarieObenour[m]> I actually reported that as a security vulnerability in gnome-terminal before I understood what was going on.
<qyliss> oh wow, yes, that is surprising
<DemiMarieObenour[m]> Basically, DnD only works if everyone agrees on what the topmost window at a given position is, and that is not the case in Qubes OS.
<qyliss> in Wayland, only the compositor needs to know, right?
<qyliss> (I'm coming at this from the virtio-wl/virtio-gpu perspective, like Thomas)
<emersion> yes
nerdopolis has joined #wayland
<wlb> weston/main: Derek Foreman * compositor: Stop trapping SIGQUIT https://gitlab.freedesktop.org/wayland/weston/commit/2f71b3c3deae compositor/main.c
<wlb> weston/main: Derek Foreman * compositor: Use sigaction to trap SIGINT https://gitlab.freedesktop.org/wayland/weston/commit/f32bcfef42a0 compositor/main.c
<wlb> weston/main: Derek Foreman * compositor: Launch clients in their own session https://gitlab.freedesktop.org/wayland/weston/commit/bb1d19dc5e99 compositor/main.c
<wlb> weston Merge request !817 merged \o/ (compositor: Stop trapping SIGINT https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/817)
dblsaiko is now known as doublesaiko
dblsaiko has joined #wayland
doublesaiko has quit []
maxzor has quit [Ping timeout: 480 seconds]
maxzor has joined #wayland
Arnavion has quit [Remote host closed the connection]
Arnavion has joined #wayland
dblsaiko has quit [Remote host closed the connection]
dblsaiko has joined #wayland
Company has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
maxzor has quit [Ping timeout: 480 seconds]
erc_ has joined #wayland
erc has quit [Ping timeout: 480 seconds]
erc has joined #wayland
erc_ has quit [Ping timeout: 480 seconds]
jgrulich has quit [Ping timeout: 480 seconds]
shankaru has quit [Quit: Leaving.]
lagash has quit [Remote host closed the connection]
lagash has joined #wayland
manuel1985 has quit [Remote host closed the connection]
manuel1985 has joined #wayland
<swick> do we know who wrote that part of the vulkan spec?
shankaru has joined #wayland
<swick> > If the swapchain is created with a present mode of VK_PRESENT_MODE_MAILBOX_KHR or VK_PRESENT_MODE_IMMEDIATE_KHR, then the corresponding wl_surface.attach, wl_surface.damage, and wl_surface.commit request must be issued by the implementation during the call to vkQueuePresentKHR and must not be issued by the implementation outside of vkQueuePresentKHR
<daniels> swick: o/
<swick> perfect :)
<swick> why is this restricted to mailbox and immediate?
<daniels> I'd have to ping the 2015 edition of daniels and ask him
<daniels> it does certainly make no sense for that to be cut out from FIFO, because you're just handing yourself an absolute footgun
<daniels> we were definitely hoping at the time that presentation-time would take off, but ... lul
___nick___ has quit []
<swick> in practice the WSI gives the same guarantee for FIFO and apps rely on it
<daniels> IIRC the requirement was originally unqualified (i.e. for all present modes), but then later on there was a longer discussion about how FIFO was mandatory and not blocking was mandatory, so that was kind of cut out whilst we waited for the ecosystem to be fixed
<daniels> (it was mostly jajones pushing for the FIFO usecases)
maxzor has joined #wayland
___nick___ has joined #wayland
___nick___ has quit []
<swick> daniels: so, changing the spec to reflect reality would probably a good idea?
___nick___ has joined #wayland
<daniels> yeah, I would suggest so, and then apps who don't want to block on FIFO can be a usecase for present timing
mceier has joined #wayland
MrCooper_ is now known as MrCooper
<MrCooper> FWIW, this means the WSI can't work around Wayland compositors missing display refresh cycles due to busy buffers
<MrCooper> (at least not without vkQueuePresentKHR doing the moral equivalent of glFinish)
manuel1985 has quit [Ping timeout: 480 seconds]
<daniels> yep
manuel1985 has joined #wayland
naveenk2 has quit []
caseorum has joined #wayland
caseorum has quit [Remote host closed the connection]
caseorum has joined #wayland
<MrCooper> kind of sad that after a couple of years of beating drums about this issue, I only know of gamescope having addressed it
rv1sr has joined #wayland
<emersion> well, we really miss a mechanism to integrate "wait for fence" into poll
<emersion> firing up a thread just for this is really not great
<MrCooper> a dma-buf fd works fine
<MrCooper> the real challenge is the implications for tracking output state vs Wayland protocol state
<emersion> hm right poll works on dma-bufs but not fences
<emersion> wasn't mutter doing some work for this?
<emersion> we have wlroots patches for this as well
caseorum has quit [Quit: Quit]
caseorum has joined #wayland
<MrCooper> emersion: I started working on it for mutter, but I haven't fully solved the challenge yet, and I won't get a chance to pick it up again for another six months at least
<emersion> that's some long-term planning :P
caseorum has quit []
<MrCooper> I need to focus on something else until the RHEL 8.7 release is done
caseorum has joined #wayland
d_ed has quit [Ping timeout: 480 seconds]
<MrCooper> (others are free to pick this up in the meantime, of course)
rv1sr has quit []
<MrCooper> meanwhile, users just notice that games look less smooth with Wayland than Xorg :(
d_ed has joined #wayland
caseorum has quit [Read error: Connection reset by peer]
ecloud_quassel has quit [Ping timeout: 480 seconds]
caseorum has joined #wayland
caseorum has quit [Read error: Connection reset by peer]
caseorum has joined #wayland
ecloud_ has joined #wayland
zebrag has joined #wayland
duxco has joined #wayland
duxsco has quit [Ping timeout: 480 seconds]
duxco is now known as duxsco
tzimmermann has joined #wayland
duxsco has quit [Quit: duxsco]
duxsco has joined #wayland
Arnavion has quit [Ping timeout: 480 seconds]
Arnavion has joined #wayland
lxsameer3 has joined #wayland
lxsameer2 has quit [Ping timeout: 480 seconds]
jmdaemon has joined #wayland
caseorum has quit [Read error: Connection reset by peer]
fmuellner has quit [Ping timeout: 480 seconds]
shankaru has quit [Quit: Leaving.]
jmdaemon has quit [Quit: WeeChat 3.5]
caseorum has joined #wayland
ppascher has joined #wayland
caseorum has quit [Read error: Connection reset by peer]
___nick___ has quit [Ping timeout: 480 seconds]
manuel1985 has quit [Ping timeout: 480 seconds]
tzimmermann has quit [Quit: Leaving]
Major_Biscuit has joined #wayland
Serus has quit [Ping timeout: 480 seconds]
duxsco has quit [Quit: duxsco]
Major_Biscuit has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
maxzor has quit [Remote host closed the connection]
maxzor has joined #wayland
duxsco has joined #wayland
Serus has joined #wayland
jmabr has quit [Quit: Leaving]
nerdopolis has joined #wayland
Major_Biscuit has joined #wayland
d_ed has quit []
dcz_ has quit [Ping timeout: 480 seconds]
lxsameer3 has quit [Remote host closed the connection]
mvlad has quit [Remote host closed the connection]
Major_Biscuit has quit [Ping timeout: 480 seconds]
jr has joined #wayland
jr has quit []
codedchaos has joined #wayland
bim9262 has quit [Ping timeout: 480 seconds]
hardening has quit [Ping timeout: 480 seconds]
neonking has joined #wayland
bim9262 has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
maxzor has quit [Ping timeout: 480 seconds]
codedchaos has quit [Ping timeout: 480 seconds]
danvet has quit [Ping timeout: 480 seconds]
ppascher has quit [Ping timeout: 480 seconds]