ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
Brainium has quit [Quit: Konversation terminated!]
phonetics has joined #wayland
phonetics has quit [Remote host closed the connection]
phonetics has joined #wayland
phonetics has quit [Remote host closed the connection]
garnacho has quit [Ping timeout: 480 seconds]
phonetics has joined #wayland
phonetics has quit [Remote host closed the connection]
mxz__ has joined #wayland
mxz___ has joined #wayland
mxz has quit [Ping timeout: 480 seconds]
mxz___ is now known as mxz
mxz_ has quit [Ping timeout: 480 seconds]
hergertme has quit [Remote host closed the connection]
iomari891 has joined #wayland
<YaLTeR[m]>
how normal is it for two monitors from the same manufacturer to have the exact same model, make, and serial? I thought you could rely on model+make+serial being more or less unique to store things like window positions across monitors
<soreau>
easier to use the crtc/connector name
<YaLTeR[m]>
then it won't work across connector name changes. Like if you have two GPUs, their connector names can come up in parallel and race, and you have different ones every boot. Or displayport docks bump connector name with every monitor
<bbhtt>
did wayland-protocol 1.38 bump the wayland scanner version required?
<bbhtt>
getting an error trying to build `linux-dmabuf/linux-dmabuf-v1.xml:113: element event: validity error : No declaration for attribute deprecated-since of element event`
kts has joined #wayland
lockywolf has quit []
lockywolf has joined #wayland
<bbhtt>
ok, seems it affects the tests only
iomari891 has quit [Quit: WeeChat 4.3.1]
iomari891 has joined #wayland
yaslam has joined #wayland
Emantor has joined #wayland
<kennylevinsen>
YalTeR[m]: note, I have occasionally seen that as a mishap when the monitors do actually have unique serials but EDID handling messed up and gave the same result for both monitors. Double check the EDID to make sure it’s actually foo.
abhimanyu has quit [Read error: Connection reset by peer]
<zamundaaa[m]>
YaLTeR: two monitors having the exact same EDID is a thing, you can't fully rely on it
<zamundaaa[m]>
KWin has a system where it'll use the edid serial + manufacturer + model + manufacturing date when it's unique, a hash of the entire edid when it's not, mst path or connector name when that's not unique either
<zamundaaa[m]>
And yes, connector names are not something anyone should ever use for persistent data, but we don't always have a better option
<kennylevinsen>
I’d be a little bit surprised if the serial is the same but the rest of the EDID differs to give a different hash
<kennylevinsen>
Ah I have seen zero-serial eDP panels so I guess that’s one way for that to happen
<kennylevinsen>
zamundaaa[m]: how does that work if, say, you start with one monitor, then plug in one that conflicts?
kts has quit [Quit: Leaving]
<zamundaaa[m]>
kennylevinsen: yep, zero serial is what that's for