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 [Remote host closed the connection]
nerdopolis has joined #wayland
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
slattann has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
Dami_Lu has quit [Ping timeout: 480 seconds]
Dami_Lu has joined #wayland
slattann has quit [Quit: Leaving.]
hays has joined #wayland
<hays>
across two different distros on kde plasma wayland I am getting this yellow W in the taskbar
pw has quit [Read error: Connection reset by peer]
pw has joined #wayland
dcz_ has joined #wayland
pw has quit [Read error: Connection reset by peer]
pw has joined #wayland
hardening has joined #wayland
rv1sr has joined #wayland
jgrulich has joined #wayland
_bsr_ has quit [Ping timeout: 480 seconds]
<zzag>
hays: if a KDE app has that "W" icon in the task manager, please file a bug report at bugs.kde.org; in general, you can use https://webchat.kde.org/#/room/#kwin:kde.org to discuss with us plasma wayland things
MajorBiscuit has joined #wayland
Company has quit [Read error: Connection reset by peer]
Company has joined #wayland
mvlad has joined #wayland
adarshgm has quit [Ping timeout: 480 seconds]
adarshgm has joined #wayland
floof58 has quit [Ping timeout: 480 seconds]
floof58 has joined #wayland
adarshgm1 has joined #wayland
floof58 has quit []
floof58 has joined #wayland
<pq>
MrCooper, Phoronix forums so far have been surprisingly reasonable about this Weston release.
<pq>
emersion, thank you for the release!
<MrCooper>
pq: indeed, the HDR thing definitely sparked some excitement though :)
adarshgm has quit [Ping timeout: 480 seconds]
<pq>
it did but not overboard
<pq>
Theoretically you could coax Weston to set a HDR mode, use 10 bpc color, and have a fullscreen video player decode HDR pretending it's going straight to the monitor.
<pq>
everything else of course would be an eye-sore on that monitor
<pq>
and naturally that stops working, hopefully by the next Weston major release
<emersion>
np!
jmdaemon has quit [Ping timeout: 480 seconds]
staticfinalpengu has joined #wayland
staticfinalpengu has left #wayland [#wayland]
adarshgm1 has quit [Ping timeout: 480 seconds]
d42 has quit [Ping timeout: 480 seconds]
d42 has joined #wayland
adarshgm has joined #wayland
fahien has joined #wayland
rgallaispou1 has quit [Read error: Connection reset by peer]
<mvlad>
fyi, I've updated !936 to remove the pc file as well, though not really sure there's something else we might want in first.
<pq>
mvlad, my question is mostly about cherry-picking things for 11.0.1. If we land the intrusive stuff, cherry-picking becomes harder. Do you care about that?
<mvlad>
well, !990 touches libweston-desktop but it wouldn't be that hard to cherry-pick that back. I wouldn't stress that much w/ it (famous last words).
<pq>
ok. The intrusive stuff planned in that milestone are mainly moving code around, so it should still be manageable.
<pq>
daniels, should we start splitting compositor.c up now? Who'd do it?
<hays>
zzag: thanks. i think i figured it out.. its a parallels desktop tool so part of vm tools
<pq>
and how do we organize the headers, because we have both per class (weston_surface, weston_head, ...) but also public vs. internal/backend vs. core APIs.
<hays>
prlcp -- "The tool prlcp can be run to synchronize the clipboard between guest and host."
<pq>
though I guess we can split compositor.c first, and re-organize headers later
fahien has quit [Ping timeout: 480 seconds]
<pq>
mvlad, how do you want 11.0.1 material marked?
<mvlad>
pq, as is, is fine (11.0.1). Used the same for 10 (and bump that when needed).
<pq>
Did you create a milestone or a label?
<pq>
mvlad, we cannot get *any* rebase MR pass CI now, until !936 is in. Could you add the major bupm there?
<mvlad>
pq, right, on it.
<mvlad>
created a milestone now for 11.0.1
<pq>
thanks, and I should tag the *original* MR with that milestone?
<mvlad>
pq, created a new milestone for those MRs that still a need proper backport to a 11 point release. Renamed !995 to use that instead. it's 'backport to weston 11' if you have other to tag. Think it is more suitable.
<daniels>
pq: I haven't had the chance to look at what MRs to land and when - I've got a ton of stuff I need to finish before XDC so realistically probably won't look until then, just go ahead and do whatever seems sensible
<pq>
daniels, ok. I'm undecided if I should take the time to split compositor.c or just continue with my stuff.
<daniels>
pq: I think let's just take it opportunistically. I'll try to come back to surface/view mapping when I'm done with my current project work, and when I'm doing that I'll try to shake compositor.c and see if there's anything natural that would fall out of trying to split that up
<mvlad>
afaik, the xwayland test timeouts from time to time. It's been an issue for a while now. (and it happened as well after the fork changes landed)