02:50wlb: wayland Issue #359 closed \o/ (Stylus tracking suddenly out of calibration https://gitlab.freedesktop.org/wayland/wayland/-/issues/359)
10:22pq: swick[m], I have much more comments for the mastering display info request, but we should agree on the terminology first before I can write proper comments.
11:27wlb: wayland-protocols/main: Jonas Ådahl * xdg-output: Remove and tweak contradicting examples https://gitlab.freedesktop.org/wayland/wayland-protocols/commit/94482ceaf9be unstable/xdg-output/xdg-output-unstable-v1.xml
11:27wlb: wayland-protocols Merge request !195 merged \o/ (xdg-output: Remove and tweak contradicting examples https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/195)
11:29DodoGTA: Why does setting the primary screen in xrandr do nothing with XWayland?
11:30pq: DodoGTA, xrandr on Xwayland is strictly read-only. It cannot be used to reconfigure the Wayland compositor.
11:32pq: OTOH, I think Xwayland does support faking video mode changes via RandR, to let apps think they changed it. In reality, video mode does not change.
11:33emersion: hm i think it's supposed to work DodoGTA
11:33emersion: some sway users have a script to set the X11 primary output via xrandr
11:33emersion: (this doesn't affect the Wayland compositor in any way)
11:35pq: DodoGTA, what exactly did you expect to see?
14:03DodoGTA: pq: So how can I force an Xorg app to run on a specific screen without changing the primary screen in KDE?
14:03DodoGTA: Specifically a fullscreen one
14:05pq: can't you just... move it there?
14:06pq: or does it force itself to a wrong output?
14:09pq: I have no idea how KDE works there, user interfaces are up to each DE. The Wayland compositor always has the last say in the matter, so you need to somehow tell it what you want.
14:10DodoGTA: pq: KDE can weirdly change the XRandR primary screen, but XRandR can't
14:11DodoGTA: The particular app does start on that primary screen by default with no way to change it
14:15zzag: DodoGTA: for kwin specifically, you could use a window rule; if you have control over source code of the app, you could just make sure that the app sets the corresponding hints so kwin places the window on some specific output
14:22pq: DodoGTA, maybe kwin just immediately undoes what you do with xrandr? In the end, kwin decides what the primary output is anyway.
14:24pq: xrandr is never the authoritative configuration tool, not even on Xorg. You need to have the DE specifically adapt to what you might change with xrandr - it's just that on Xorg, the DE cannot stop you from messing with xrandr.
14:25vsyrjala: kwin supposedly has https://wayland.app/protocols/kde-primary-output-v1
14:25pq: well, "never" is an overstatement. On non-DE environments xrandr might be only thing driving the monitor configuration.
14:26zzag: That's a deprecated protocol, but you shouldn't use neither kde-primary-output-v1 no kde-output-order-v1
14:26zzag: nor*
14:26zzag: Those are for plasma
14:26zzag: You shouldn't use xrandr command to change the primary output either
14:27pq: we can always rightfully blame the app, and that doesn't help the end user...
14:28zzag: pq: if you want a window to be shown on a particular output, change the relevant window geometry hints. changing the primary output may help you to achieve your goal, but one could argue that there are better options
14:30pq: DodoGTA, ^
14:51DodoGTA: zzag: I've tried to change the position window rule in KDE but that does nothing in fullscreen mode
14:59wlb: wayland Issue #360 opened by wentbackward (wentbackward) HP Pointing Stick Issue https://gitlab.freedesktop.org/wayland/wayland/-/issues/360
15:03wlb: weston Merge request !1178 opened by Michael Olbrich (mol) compositor/text-backend: use xzalloc everywhere https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1178
15:03wlb: wayland Issue #360 closed \o/ (HP Pointing Stick Issue https://gitlab.freedesktop.org/wayland/wayland/-/issues/360)
15:05DodoGTA: So how should native Wayland toolkits/apps pick on which screen to run in fullscreen mode?
15:07wlb: weston Issue #727 opened by Kim Crow (kimcrow) 4 Gift Exchange Ideas for Big Families https://gitlab.freedesktop.org/wayland/weston/-/issues/727
15:08emersion: ah nice
15:09DodoGTA: When you spam it (osu! reference)
15:10wlb: weston Merge request !1179 opened by Michael Olbrich (mol) ivi-layout: simplify API https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1179
15:11pq: DodoGTA, I don't think native Wayland apps do. The compositor does.
15:11zzag: DodoGTA: huh, it might be a bug. Please file a bug report. Note that there's also a screen rule
15:12zzag: pq: xdg_toplevel.set_fullscreen takes an output hint
15:12DodoGTA: zzag: I also tried that with values set at 0 and 1 (no difference)
15:12pq: yeah, it takes a hint. That's all.
15:13pq: If an app uses that hint, the app really needs to have a way to change that somehow too.
15:14pq: It doesn't mean apps should usually set that hint.
15:33pq: swick[m], btw. I'm currently improving the wp_image_description events to be more like the respective factory requests.
15:33pq: till tomorrow \o.
15:33swick[m]: o/
17:09kennylevinsen: DodoGTA: the value is a wl_output object ID, not an output number
17:22DodoGTA: kennylevinsen: Are those object IDs random?
18:29kennylevinsen: DodoGTA: all object IDs are dynamic, obtained when the object is created or bound
18:43zzag: DodoGTA: https://invent.kde.org/plasma/kwin/-/merge_requests/3711 might fix the issue, otherwise let's continue the discussion in https://webchat.kde.org/#/room/#kwin:kde.org
19:02emersion: reminder: libwayland alpha tomorrow
20:42emersion: would anyone have a few minutes to ack/review this? https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/291
20:43wlb: wayland/main: Sebastian Wick * protocol: do not change pending x and y when attaching a buffer https://gitlab.freedesktop.org/wayland/wayland/commit/2aec8f59e9c0 protocol/wayland.xml
20:43wlb: wayland Merge request !295 merged \o/ (protocol: do not change pending x and y when attaching a buffer https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/295)
20:46wlb: wayland Issue #322 closed \o/ (Inconsistent implementation of wl_data_offer.source_actions https://gitlab.freedesktop.org/wayland/wayland/-/issues/322)
20:46wlb: wayland/main: Vlad Zahorodnii * protocol: reorder wl_data_offer.source_actions and wl_data_device.enter https://gitlab.freedesktop.org/wayland/wayland/commit/3815803633a6 protocol/wayland.xml
20:46wlb: wayland Merge request !270 merged \o/ (protocol: reorder wl_data_offer.source_actions and wl_data_device.enter https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/270)
20:46bl4ckb0ne: why are some aliases missing?
20:51emersion: old code taken from Xorg
20:52wlb: wayland Merge request !63 closed (build: Fix strndup detection on MinGW)
20:54wlb: wayland/main: Mikhail Gusarov * protocol: Clarify meaning of input region for cursors, DnD icons https://gitlab.freedesktop.org/wayland/wayland/commit/6cdeae1becef protocol/wayland.xml
20:54wlb: wayland Merge request !281 merged \o/ (protocol: Clarify meaning of input region for cursors, DnD icons https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/281)
20:58bl4ckb0ne: i mean from the specs, the patch doesnt add all of them
20:59bl4ckb0ne: is it only the DnD stuff?
21:00emersion: only the cursors in the built-in theme
21:00emersion: the list above the new entries contains the old names
21:01emersion: thanks!
21:02wlb: wayland/main: Simon Ser * shm: fix segfault when accessing destroyed pool resource https://gitlab.freedesktop.org/wayland/wayland/commit/ab526f8d7c80 src/wayland-shm.c
21:02wlb: wayland Merge request !268 merged \o/ (shm: fix segfault when accessing destroyed pool resource https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/268)