00:34solomoncyj: hello
00:34solomoncyj: does wayland have a protoocool for applications to request for a global keybind on the fly?
00:37DMJC: is there a test application for DRM lease? I want to grab a lease device and draw a test pattern on it
00:37Arnavion: solomoncyj: No, but there's an xdg-desktop-portal interface for that, or individual compositors might provide their own way
00:39solomoncyj: also have the bug about flatpak x apps, eg podman desktop, not being able to share clipboards with the wayland system been fixed yet?
00:43bl4ckb0ne: DMJC: i have a fork of kmscube with drm lease somewhere, but if you want to draw you need vk
00:43bl4ckb0ne: its pretty straightforward tho
00:44solomoncyj: is thre a way to "reject" a keybind and stop an application form listen it without telling the app?
01:19DMJC: blk4ckb0ne: perfect, I don't need to change the picture atm. Just trying to test a PSVR2 on Linux
01:19DMJC: I've got the headset activating the external cameras over USB, I want to see if I can get it to show a picture and get into VR mode.
01:46bl4ckb0ne: have you tried monado?
02:00DMJC: no, I haven't seen any PSVR2 support for them?
02:02bl4ckb0ne: iirc it should work, otherwise it would not be far from the older one
02:13DMJC: how do you use the drm lease with the vkcube application?
02:14DMJC: I've got the kmscube application with DRM built
02:14DMJC: it's trying to init the wrong display
02:15bl4ckb0ne: i think i saw a drm vkcube somewhere
02:15bl4ckb0ne: got a connector leased?
02:16DMJC: xrandr lists lease-DP-1
02:16DMJC: but I'm on wayland, I suspect my compositor (wayfire) might not support it
02:16DMJC: ./kmscube -l
02:16DMJC: zwp_lease_manager_v1 global not available
02:21DMJC: ah here we go, kde has it
07:54DMJC: hmm... so the PSVR2 appears as a 1080p device under Wayland/AMDGPU but on Intel with a USB-C -> DP adapter it appears as 4080x2000 pixels
07:55DMJC: I also can't activate the DRM lease, I've tried and the cube application segfaults or says no permission
07:55kennylevinsen: if you can't activate the drm lease, how do you know it shows up as a 1080p device?
07:56DMJC: wayland-info
07:56DMJC: connector id 107
07:56DMJC: using DRM mode 1920x1080@0.000000Hz
07:56DMJC: that's when I run the KMS Cube application
07:57kennylevinsen: that doesn't mean it's the only mode, the lease application is free to modeset
07:57DMJC: interesting, that's the only mode that xrandr and the cube application are detecting.
07:58linkmauve: DMJC, maybe try drm_info instead?
08:04DMJC: thanks, there's a lot of information there about texture formats etc.
08:05kennylevinsen: it should also give you the available modes
08:07DMJC: yeah it's failing to get the 4k mode
08:07DMJC: only showing 1920x1080 at 23/24/50/60hz
08:08DMJC: interesting, since on Windows it has the full range of 4k modes
08:08DMJC: if I switch to the USB-C HDMI adapter I get the full list of modes.
08:09DMJC: including 4000x2040@119.88
08:09kennylevinsen: sounds like your gpu driver might be filtering the mode based on perceived link limitations then
08:11DMJC: I might have just found the cause
08:12DMJC: hmm ok, it's not the HDMI being plugged in, looks like some sort of limitation on Linux
08:31pq: ramblurr, many wl_proxy_marshal_* functions are obsolete, but we cannot delete them because it would break library ABI. Problems with the older ones include e.g. subtle thread races leading to protocol errors.
08:34pq: bl4ckb0ne, colinmarc, you could try the wayland-protocols experimental/ process already, see if it feels good - just cannot land anything upstream yet, but no harm in having MRs.
08:56DMJC: I fell back to X11, I can access the headset including VR Mode just sending it 4k 120hz/4k 90hz data works.
08:56DMJC: Looks like the headset auto-loads into VR Mode
09:22linkmauve: DMJC, can you run drm_info again now, and see if the new mode appeared?
10:02bluetail: misbehaving VR headsets can be detrimental for health... I'd be wary
10:31wlb: wayland-protocols Merge request !292 closed (Specify wl_surface.offset for toplevel-drag)
11:38DMJC: linkmauve, I tested in X11 on AMD and it still doesn't appear
12:19ramblurr: pq: which ones are deprecated? or rather, which ones should I be using in new lang binding code?
12:33pq: ramblurr, I don't remember off-hand, but the newer would be better. There are also two alternative APIs, one used by wayland-scanner and the other for language bindings that are less fond of C.
12:35pq: ramblurr, I think the "array" variants are more popular with language bindings, and the non-array ones are used by wayland-scanner.
12:38pq: ramblurr, wl_proxy_marshal_array_flags() is probably the best thing.
12:40pq: ramblurr, wl_proxy_add_dispatcher() may be best for language bindings for setting up event handling.
12:46pq: ramblurr, wl_proxy_set_tag() may also be of interest, for identifying which component owns the proxy, to know whether to interpret its user_data.
13:47wlb: wayland-protocols Merge request !327 closed (text-input: Clarify anchor in set_surrounding_text)
14:23wlb: wayland-protocols Issue #217 closed \o/ (Possible typo in ext-image-copy-capture-v1.xml https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/217)
14:23wlb: wayland-protocols/main: itycodes * ext-image-copy-capture-v1: Fix typo in ext_image_copy_capture_frame_v1::destroy https://gitlab.freedesktop.org/wayland/wayland-protocols/commit/ea7e5ef693e9 staging/ext-image-copy-capture/ext-image-copy-capture-v1.xml
14:23wlb: wayland-protocols Merge request !343 merged \o/ (ext-image-copy-capture-v1: Fix typo in ext_image_copy_capture_frame_v1::destroy https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/343)
16:57wlb: weston Merge request !1621 opened by () Fix dma-buf feedback issue https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1621
17:57wlb: weston Merge request !1622 opened by () Draft: libweston: add etnaviv 2D GPU renderer https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1622