00:30 bluetail: ty, I won't upgrade then
00:30 bluetail: I am on 6.11.5-arch-1-1 at the moment
00:31 bluetail: cause stuff is still working :)
00:34 dviola: looks like only QEMU virgl is affected
00:34 dviola: np
01:44 ke8cqc: I'm a long time Gentoo LInux user who has only used xorg. I would like to try Wayland. Through googling, I have found out that xorg and wayland can run concurrently on the same machine, so I've installed wayland and hyprland. Is there a way to disable xorg and use wayland without nuking my xorg config?
01:49 whot1: ke8cqc: if you're running wayland the X server you're running will be Xwayland which is a translation layer between the wayland protocol and the X protocol. You're not actually running /usr/bin/Xorg anymore. Xwayland doesn't read your config so you can leave it in place
01:52 ke8cqc: I guess I'm confused here. What's running on my machine is xorg using bspwm right now. I have installed wayland, xwayland, and hyprland. What I don't understand is how to set up my laptop to use wayland and hyprland.
01:54 whot1: ke8cqc: you tell whatever starts xorg on your machine to start your compositor instead
01:54 whot1: in gdm that's a button to change between GNOME on Xorg and GNOME on Wayland, other display managers will have their own configuration
01:55 ke8cqc: I'm currently using ligjhtdm. I notice that hyprland shows up in the menu of available window managers, but when I choose it, all I get is a blinking cursor in the upper left corner of my screen after loging in.
01:56 ke8cqc: *lightdm.
01:57 whot1: ke8cqc: check if there's anyhing in the journal to tell you what's going wrong
01:58 ke8cqc: I'm using OpenRC - not SystemD.
03:27 wlb: wayland Merge request !440 opened by () cursor: scale cursors to the requested size on env var "XCURSOR_RESIZED=true" https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/440
09:00 wlb: wayland.freedesktop.org Merge request !92 opened by () releases: Add wayalnd-protocols 1.38 https://gitlab.freedesktop.org/wayland/wayland.freedesktop.org/-/merge_requests/92
09:03 wlb: wayland.freedesktop.org/main: Jonas Ådahl * releases: Add wayland-protocols 1.38 https://gitlab.freedesktop.org/wayland/wayland.freedesktop.org/commit/4752e7290d3e releases.html
09:03 wlb: wayland.freedesktop.org Merge request !92 merged \o/ (releases: Add wayland-protocols 1.38 https://gitlab.freedesktop.org/wayland/wayland.freedesktop.org/-/merge_requests/92)
09:10 jadahl: vyivel: emersion: should be fixed now. thought I had already done it, sorry about that
09:10 vyivel: thanks!
09:10 jadahl: np
09:11 emersion: ty!
09:45 pq: mclasen, the question is more about the level of support. There is new protocol after v4 still. I also haven't looked carefully enough whether all implementations together cover all the features.
09:46 jadahl: pq: I think one missing thing is an implementation that has both icc support and hdr support that mixes the two (monitor in HDR mode + ICC profile client)
09:46 pq: right
09:46 jadahl: I think Joan is working that atm
09:47 pq: oh, for which compositor?
09:47 jadahl: mutter
09:47 pq: cool
09:47 jadahl: here is a wip: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4102
09:48 pq: OTOH, I cannot think how that might change the protocol design, but of course it's better to see than guess.
09:48 jadahl: right, we have an idea for how it will work with nothing new needed in the protocol
09:49 jadahl: roughly it's creating an icc profile for the intermediate buffer color state in standard range, and then do standard to high dynamic range after doing an icc->icc conversion
09:50 pq: That's a very good idea.
09:50 pq: I was slightly worried by the MR description which seems to say otherwise.
09:50 jadahl: right, it isn't doing that yet
09:52 pq: I've been thinking of interfacing with the ICC PCS in the "parametric" handling side, but crafting an ICC profile and letting a CMM handle it feels better.
09:54 pq: well... crafting that ICC profile is equivalent, and probably on par with difficulty.
09:54 pq: I think an important aspect would be to ensure tat
09:56 pq: *that when an ICC profile and a parametric image description are fully equal, they also result in equivalent color transformations for all kinds of image descriptions as the other side.
09:56 pq: *on the other side
10:00 pq: jadahl, is there a reason to start with explicit shaper-matrix ICC profile parsing when crafting the intermediate ICC profile would make that moot? Do you want a special case that works without a 3D LUT?
10:01 jadahl: I guess the downside of doing parametric via ICC is you only get luts from lcms2?
10:01 pq: ICC files can contains 3D LUTs which you cannot represent with parametric.
10:02 jadahl: I mean interfacing parametric via ICC profiles, but maybe I misunderstood you
10:03 pq: Crafting an ICC profile for the intermediate space works for everything. Transforming an ICC profile into parametric representation is limited to certain types of profiles only.
10:04 jadahl: ah, yes, I don't think we'd start with special casing ICC profiles when thats what the client hands us, but I'm not sure
10:05 pq: the commit messages certainly sound like they special-case shaper-matrix profiles
10:06 pq: An ICC profile can have different AToB/BToA/DToB/DToA tags for colorimetric, saturation, and perceptual rendering intents, so you also need to know the rendering intent when using a profile.
10:08 pq: jadahl, I can see the special-casing code already there.
10:10 jadahl: pq: the MR is from a state before the intended ICC->ICC(SDR)->intermediate(HDR) approach was described to Joan
10:11 pq: right
10:13 pq: jadahl, when you have to use a 3D LUT, https://www.littlecms.com/ASICprelinerization_CGIV08.pdf might be useful. Leandro has worked on implementing that in Weston.
10:15 jadahl: pq: forwarded the link. too bad he isn't in this channel (at least I can't see him from IRC)
10:16 pq: thanks
12:36 zzxyb[m]: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/main/staging/ext-image-capture-source/ext-image-capture-source-v1.xml?ref_type=heads#L27 Why is opaque image emphasized here? emersion
12:45 vyivel: zzxyb[m]: "opaque" refers to "objects" there, not "image"
12:46 zzxyb[m]: I think I know what the author means.thanks
12:47 zzxyb[m]: Does anyone here make protocols for application shortcuts and system shortcuts?
12:49 vyivel: there's https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/216
12:49 zzxyb[m]: nice！
13:20 wlb: weston/main: Leandro Ribeiro * color-lcms: accept ICC profiles of device class ColorSpace https://gitlab.freedesktop.org/wayland/weston/commit/a3fd8f3c97fb libweston/color-lcms/color-profile.c
13:20 wlb: weston Merge request !1593 merged \o/ (color-lcms: accept ICC profiles of device class ColorSpace https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1593)
13:39 emersion: yeah, "opaque" as in "opaque object" rather than "opaque image"
15:00 wlb: weston Merge request !1637 opened by () gitlab-ci: Bump libdrm to 2.4.118 to add NV{15,20,30} fmts https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1637
15:20 wlb: weston/main: Marius Vlad * gitlab-ci: Bump libdrm to 2.4.118 to add NV{15,20,30} fmts https://gitlab.freedesktop.org/wayland/weston/commit/fe35be501391 .gitlab-ci.yml .gitlab-ci/build-deps.sh shared/weston-drm-fourcc.h
15:20 wlb: weston Merge request !1637 merged \o/ (gitlab-ci: Bump libdrm to 2.4.118 to add NV{15,20,30} fmts https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1637)