08:03rawoul: 03333
09:22MrCooper: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/248#note_2281433 discusses some of the same issues as I raised in https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/175, but even though I pointed to the latter in the former, nobody has even acknowledged its existence yet. Not sure what to make of that
09:23MrCooper: my issue has a proposal for a solution
09:30pq: MrCooper, I've read your 175, but I feel incapable of diving that deep while color-management is on my plate. It's easier to just casually troll elsewhere, sorry. :-)
09:32pq: I can only repeat my ideals for now, and that's not useful.
09:42wlb: wayland Merge request !367 opened by Simon Ser (emersion) Introduce enum wl_arg_type https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/367 [IPC library]
09:43MrCooper: pq: my proposed solution attempts to preserve your ideal as much as realistically possible
09:44pq: cool
09:44MrCooper: and it lets the client know what's what
09:52wildwestrom[m]: Hello everyone. I'm pleased to finally be a part of this room. I've been a Sway user for about 3 years now and I'd like to start contributing to the Wayland project as a whole.
09:55pq: Hi wildwestrom[m], welcome.
09:57wildwestrom[m]: Hi @pq. It seems you're one of the people who were last working on wayland/#194.
09:58emersion: you mean this? https://gitlab.freedesktop.org/wayland/wayland/-/issues/194
09:59wildwestrom[m]: Indeed emersion
10:00wildwestrom[m]: I've been on a wild goose chase trying to figure out why programs are crashing, and I appear to be close to rock bottom. Been collecting all the issues that mention wl_surface@n: error 2: Buffer size (NxN) is not divisible by scale (n). If I understand right, it seems like crashing is intended behavior(?) I'm not sure though.
10:01emersion: yeah, but it'
10:01emersion: s likely unrelated to this particular issue
10:02emersion: compositors don't send this error for cursor surfaces in practice today
10:03emersion: the bug is likely to be in the app you're using
10:03wildwestrom[m]: Really? Ok, well that's a bit of a relief. Jumping right into changing the ABI seems daunting.
10:03wildwestrom[m]: Ok, I figured it was, and boy is it prevalent.... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/HmisgmHcdEcNGMVPIUkqtaSu>)
10:26davidre: I would say these are not workaround bug actual bug fixes
10:27wildwestrom[m]: David Redondo: For real? Well that's good to know.
10:29emersion: at least the first 2 are
10:29kchibisov: neovide had real bug fix.
10:29emersion: the patch in that wayland-proxy-virtwl issue is a hack
10:30kchibisov: They just forgot to resize the egl surface at some point iirc.
10:37wildwestrom[m]: Now I just have to figure out what Wezterm is doing wrong. https://github.com/wez/wezterm/issues/2445... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/vWSocxaAahgigJKoGGUHBRDY>)
10:38wildwestrom[m]: Ah, and that function itself is called when the compositor handles a commit. Therefore this must be handled before a commit.
10:46wildwestrom[m]: I think I have enough info to try to discuss it with the folks at Wezterm https://github.com/wez/wezterm/issues/2445.
10:46wildwestrom[m]: Thank's everyone!
10:56wlb: wayland/main: Sebastian Wick * server: add wl_client_get_user_data/wl_client_set_user_data https://gitlab.freedesktop.org/wayland/wayland/commit/9c4213ed3eb3 src/wayland-server-core.h src/wayland-server.c tests/client-test.c
10:56wlb: wayland Merge request !364 merged \o/ (server: add wl_client_get_user_data/wl_client_set_user_data https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/364)
11:07kchibisov: wildwestrom[m]: wezterm is in general really broken around initial sizing and such.
11:08wildwestrom[m]: Hey by the way emersion, do you happen to live in South Korea too, or is there another reason for the 시몽 on your profile?
11:09emersion: i used to live in South Korea
11:09kchibisov: during internship, I guess or parents related?
11:10emersion: yeah, parent's job
11:14wildwestrom[m]: I see, well I hope to meet you someday. I love all your projects.
11:18emersion: are you the owner of westrom.xyz?
11:18emersion: glad to hear that
11:28wildwestrom[m]: <emersion> "are you the owner of westrom.xyz..." <- Yes I am. Haven't touched it in years.
11:28emersion: cool, if you're okay with that, i'll try to ping you next time i visit
11:29wildwestrom[m]: Totally! Definitely send me a message if you're here.
11:29emersion: :)
11:58wlb: weston/main: Pekka Paalanen * 10 commits https://gitlab.freedesktop.org/wayland/weston/compare/bac9060d54293a1877f0586ccf0591408c261b2a...0ade70fb6c95ff3f9356d8c25d3a8e55319841ac
11:58wlb: weston Merge request !1356 merged \o/ (Add support for the color-management protocol https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1356)
12:09wlb: weston Merge request !435 closed (Drm gamma support)
20:02wlb: wayland Issue #442 opened by GhostCoder22 (GhostCoder22) Re-docking sub-windows isn't possible in Wayland, and switching from X11 to Wayland causes black screen due to SDDM https://gitlab.freedesktop.org/wayland/wayland/-/issues/442
20:03jal: hi, on xorg I used xbanish to hide the mouse cursor when a key is pressed; is there a wayland equivalent?
20:03wlb: wayland Issue #442 closed \o/ (Re-docking sub-windows isn't possible in Wayland, and switching from X11 to Wayland causes black screen due to SDDM https://gitlab.freedesktop.org/wayland/wayland/-/issues/442)
20:06soreau: jal: this is something that would be implemented by your compositor
20:07soreau: I haven't heard that there's any standard protocol for it, so you might check in your compositor support channels
20:08jal: thanks
20:08soreau: for example on wayfire, there's a hide cursor plugin that automatically hides the cursor after certain time of no movement
22:46Dhalucario: Hello, I have a question. I used to use Windows and Mac for a good while. After switching to Linux I noticed that the linux desktop seems to lack global context menu entry.
22:47Dhalucario: *entries
22:48Dhalucario: Is there some kind of standard that already does this? A friend told me I would have to create a standard for that but I have no clue where to start.
23:02zamundaaa[m]: Dhalucario: can you describe what exactly you're after? I don't get what you mean with "global context menu entries"
23:05Dhalucario: Sometimes when you make a text selection some applications allow you to right click it to open the context menu and do something with that text selection. Lets say I select a text in Firefox and when I right click the text I wanna send it to my gpg program to decrypt the text.
23:06Dhalucario: There is like an entry in the context menu to do so.
23:21zamundaaa[m]: Ah. Yeah I don't think such a thing exists yet
23:21zamundaaa[m]: That sounds like a job for xdg portals though
23:27Dhalucario: Hm I am going to read a bit into that then.
23:37Dhalucario: If I understand this xdg-desktop depends on dbus. Idk if that makes sense since the program should not have to be running to do the users interaction. Windows seems to do this via registry entries: https://stackoverflow.com/questions/20449316/how-add-context-menu-item-to-windows-explorer-for-folders
23:38Dhalucario: MacOS seems to allow programs to register Quick Actions which the user can add to their context menu.
23:46Dhalucario: I think I will explore this some more and rejoin once I have a bit more of a concrete idea what the API should look like. For now I will go to bed though. Good night.