ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
bluetail has quit []
bluetail has joined #wayland
feaneron has joined #wayland
Brainium has joined #wayland
fmuellner_ has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
shider has quit [Ping timeout: 480 seconds]
shider has joined #wayland
shider has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
yshui has quit [Read error: Connection reset by peer]
yshui has joined #wayland
yshui has quit [Ping timeout: 480 seconds]
Company has quit [Ping timeout: 480 seconds]
yshui has joined #wayland
Company has joined #wayland
eletrotupi has joined #wayland
feaneron has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
Psi-Jack has quit [Quit: Do you type on your PS1 or play on your PS1?]
fmuellner_ has quit [Ping timeout: 480 seconds]
shider has joined #wayland
Company has quit [Remote host closed the connection]
Psi-Jack has joined #wayland
mxz_ has joined #wayland
kts has joined #wayland
mxz has quit [Ping timeout: 480 seconds]
mxz__ has quit [Ping timeout: 480 seconds]
mxz_ is now known as mxz
kts has quit [Quit: Leaving]
nerdopolis has quit [Ping timeout: 480 seconds]
TheCaptain82970403198578471379 has quit [Ping timeout: 480 seconds]
Psi-Jack has quit [Quit: Do you type on your PS1 or play on your PS1?]
Psi-Jack has joined #wayland
glennk has joined #wayland
mclasen has joined #wayland
eruditehermit has quit [Ping timeout: 480 seconds]
sima has joined #wayland
mxz_ has joined #wayland
mclasen has quit [Ping timeout: 480 seconds]
rv1sr has joined #wayland
rv1sr has quit []
rv1sr has joined #wayland
rv1sr has quit []
eruditehermit has joined #wayland
shider has quit [Quit: WeeChat 4.4.2]
<colinmarc>
<JoshuaAshton> "Colin Marc: that's why the..." <- if you read the rest of the thread, I was trying to suggest introducing some soft backwards compatibility so that it's easier to iterate. for example adding an optional arg doesn't have to require a version bump, which would make it easier to propose and merge
abhimanyu has joined #wayland
_w has joined #wayland
tzimmermann has joined #wayland
rv1sr has joined #wayland
_w has quit []
sally has joined #wayland
coldfeet has joined #wayland
leon-anavi has joined #wayland
mclasen has joined #wayland
kts has joined #wayland
mclasen_ has joined #wayland
mclasen has quit [Read error: Connection reset by peer]
mclasen_ has quit [Remote host closed the connection]
mclasen_ has joined #wayland
rasterman has joined #wayland
Tokoyami has joined #wayland
<ifreund>
colinmarc: most wayland protocols use the design pattern of using multiple events/requests to define pending state followed by a commit event/request to make it current
<ifreund>
this is functionally equivalent to optional arguments, call it "optional events/requests" instead if you like
<ifreund>
my point is that the problem here is a social one, not a technical one
<ifreund>
and I for one do not see bypassing the standards body as a healthy solution for the ecosystem
<MrCooper>
amen
mclasen_ has quit [Read error: Connection reset by peer]
___nick___ has joined #wayland
mclasen has joined #wayland
mclasen has quit [Remote host closed the connection]
mclasen has joined #wayland
mclasen has quit [Remote host closed the connection]
<vnd>
but may be the most important finding is that upgrading BSP to latest fixes the issue
<vnd>
everything got updated, weston in particular from 8 to 10
<vnd>
but still it would be super useful to know which component is the culprint, since backporting the fix, or just upgrading one component is so much better given all the deadlines
<vnd>
so any hings are greatly appreciated
kts has joined #wayland
<daniels>
vnd: if I had to guess, I'd say that it was either weston gaining the ability to do per-plane rotation via KMS, or Mesa, or GStreamer
tzimmermann has quit [Quit: Leaving]
cwittlut_ has joined #wayland
cwittlut has quit [Ping timeout: 480 seconds]
<ManMower>
wasn't there some well known green tint weston/gst interaction around that era due to missing modifiers, and the fix was just to have gstreamer bind a newer version of linux-dmabuf?
leon-anavi has quit [Remote host closed the connection]
<ManMower>
(that era being... introducing weston 10 into your bsp)
caseif has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
cyrinux has joined #wayland
caseif has joined #wayland
Moprius has joined #wayland
<bwidawsk>
is the output emitted by `wp_presentation_feedback::sync_output` up to the compositor if the surface is displayed on multiple outputs?
<YaLTeR[m]>
yes
<bwidawsk>
so it can change every event then?
<YaLTeR[m]>
yes but i don't think anyone would do that
<kennylevinsen>
If the compositor fires on first present, it could change on every event if two overlapping outputs run at different refresh rates
<kennylevinsen>
It would be nicest for the compositor to stick to using its “preferred” output
<zamundaaa[m]>
bwidawsk: what do you want to use the sync output for?
<bwidawsk>
I'm not actually working on Wayland, however, I find Wayland to generally be a sane way of doing things and so I'm trying to model things similarly
Moprius has quit [Quit: bye]
<Company>
bwidawsk: generally the assumption is that surfaces are associated with 1 output I think and compositors translate whatever is different to the 2nd output
<Company>
see also: (fractional) scale or HDR
<bwidawsk>
I realize most of the use cases with presentation timestamps are for 1 output btw, it's mostly a curiosity
<bwidawsk>
I do imagine if you want to tile displays though, it could be problematic
<bwidawsk>
maybe the assumption is they're all vsync locked
<Company>
was reading the removal thing, and wondering: Let's say Gnome develops an experimental thing, Mutter and GTK implement it, but nobody else thinks it's high priority
<Company>
so nobody else works on it
<Company>
does it get removed after 3 months even though there are happy users?
<Company>
though it might be useful to have some place for corner-case protocols that nobody else wants to implement
<Company>
bit of a question if those should live elsewhere though
<zmike>
we'll put those on a case by casis
<bl4ckb0ne>
looks like somebody didnt signed off their commit :P
<zmike>
smh who would do such a thing
<bl4ckb0ne>
newbies smh
shider has joined #wayland
<jadahl>
Company: when (trying to, many stalled) to upstream some gtk-shell stuff, I always put my toe in the water first to see if there is interest, and I imagine the same could be done in the future would we need to
<Company>
it's some weird edge-case where you don't know if the wider world should be aware of it, even if it just has 2 users right now
<d_ed[m]>
jadahl: talking of which, is anything holding up the system bell?
<d_ed[m]>
You can ack from gnome at least
<jadahl>
people answering my questions mostly
<jadahl>
i'll go and self-ack it though, good point
<d_ed[m]>
There doesn't seem to be anything open
<jadahl>
oh, I missed replies? :o
soreau has quit [Quit: Leaving]
<jadahl>
2 unresolved threads..
soreau has joined #wayland
<jadahl>
I guess it needs a formar review, too
<jadahl>
and a last ack
<jadahl>
I was going to nag drakulix[m] about that at some point
<d_ed[m]>
cool
<jadahl>
want to "rb" it? can't ask carlos atm
<bl4ckb0ne>
ill have a look to the system-bell tomorrow for the wlroots ack
sima has quit [Ping timeout: 480 seconds]
<bl4ckb0ne>
nobody sent us an impl right?
<vyivel>
iirc nope but i can write one
<bl4ckb0ne>
sounds fun
<jadahl>
maybe wayfire can make a visual bell shader effect
<Company>
ah, people are waiting for things to appear in wayland-protocols
<jadahl>
now its missing a third ack, and a rb
<jadahl>
but maybe bl4ckb0ne will make the acks complete
<drakulix[m]>
if nobody does that before tomorrow, I’ll look into it (and most likely ack)
<jadahl>
drakulix[m]: thanks!
<Company>
I wonder if GTK needs a way to handle protocols not existing in wayland-protocols
<Company>
then we could implement them while they're on branches
<Company>
and we'd survive releases after zmike deleted half the protocols from the experimental/ folder
coldfeet has joined #wayland
<Company>
though I guess this doesn't avoid breakage because updates to experimental protocols can be breaking
<jadahl>
could if ...found() and meson_option('enable_..') in meson
<Company>
I don't like implementations living on branches because then nobody will test them
<Company>
but implementations not living on branches can cause compile-time breakage
yaslam has quit [Ping timeout: 480 seconds]
<Company>
it's fine if we hide them behind env vars, so you need to pass GDK_DEBUG=experimental-wayland or so
yaslam has joined #wayland
<Company>
to avoid shipping with an implementation for an unfinished protocol and then breaking - that'd be bad
<Company>
but I'm thinking about having something in nightlies
<Company>
that people can test
<Company>
so you can implement it in Mutter + GTK and tell designers to run with whatever env vars to see if things beep right
hch1290718697 has joined #wayland
<Company>
obviously that's more relevant for larger protocols, say color-management or input-method-v42
hch1290718697 is now known as hch12907
<hch12907>
if !339 gets merged, wouldn't wayland-protocols require a bot to make sure the removal of expired protocols is actually carried out
<ManMower>
I don't think we need nanosecond precision.
<llyyr>
and even if we did, it'd be trivial to have something that does...
<ManMower>
I think it's a "cross that bridge when we get to it" situation
<ManMower>
it would be nice if expiring protocols happened so rarely that it wasn't worth the effort to automate it.
<hch12907>
I could have sworn some protocol MRs were tagged "In 30 Day Discussion Period" even though the MR was definitively older than 30 days... but apparently that was cleaned up
<hch12907>
anyway, I thought of that, hence my original message
qyliss has joined #wayland
qyliss has quit []
qyliss has joined #wayland
paulk has joined #wayland
rv1sr has quit []
<Company>
congrats on reaching Phoronix everyone, I'm sure this will turn that MR into a fruitful discussion
<psykose>
i can already see the first phoronix commenter has jumped in
<karolherbst>
:')
<Company>
that comment is why I checked Phoronix
<karolherbst>
somebody might want to leave a "this is a community wide discussion, so please refrain from randomly jumping in" or something like that. Especially if the comments contains some unncessary opinions not helping with anything
<jadahl>
karolherbst: I copied that suggestion verbatim and replied
<karolherbst>
:D
fmuellner_ has joined #wayland
MrCooper has quit [Read error: Connection reset by peer]
<karolherbst>
I might have phrased it more diplomatic if I'd knew somebody is gonna to copy it, but fair enough
MrCooper has joined #wayland
<Company>
You apparently also should have defined "community"
<karolherbst>
yeah....
<Company>
but as you're not "the only sane developer working on linux stuff" you might be excused
<Company>
(that was from Phoronix comments)
<vyivel>
not even "phoronix user spotted, opinion invalidated"
fmuellner has quit [Ping timeout: 480 seconds]
<Ermine>
birdie linking issue 233 - check
<FreeFull>
Phoronix comments are.. something
<Arnavion>
It's called Moronix for a reason
lsd|2 has joined #wayland
<daniels>
can we please try keep a higher signal:noise ratio here? thanks.
<FreeFull>
I'm wondering if I should try writing my own wayland compositor again