10:05kyomawolf: Hey Guys, do you know How I can savely detect, if the device is a Touchpad? I havent found anything, except for checking for names/capabilities. Is there a common way?
10:06emersion: can you explain your use-case? why do you need to know?
10:08kyomawolf: I have some settings I want to apply only for mice but not for touchpad and vice versa (like pointer speed)
10:09emersion: are you writing a compositor?
10:09emersion: are you using libinput, or are you writing a Wayland client?
10:09kyomawolf: compositor? I want to work directly with libinput
10:10emersion: what kind of program are you writing?
10:10kyomawolf: A small C program that is able to apply set settings from a config, maybe something with a ui later
10:11jadahl: kyomawolf: you can do `libinput_device_config_tap_get_finger_count (device) > 0`
10:11kyomawolf: okay, so just checking for capabilites is a thing
10:11jadahl: thats what mutter uses to tag a device as "touchpad"
10:12kyomawolf: thanks guys
10:12emersion: is it running as root?
10:12kyomawolf: probably, otherwise I dont get device evnets
10:12emersion: you won't be able to use libinput in a regular program, mind
13:39wlb: weston Merge request !1392 opened by Daniel Stone (daniels) Fix input-panel surface/view mapping https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1392 [Input]
15:24wlb: wayland Merge request !356 opened by Guido Günther (agx) protocol: Suggest wl_surface.offset https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/356
15:31wlb: wayland Merge request !356 closed (protocol: Suggest wl_surface.offset)
15:38wlb: wayland/main: Simon Ser * protocol: refer to wl_surface.offset in wl_data_device.start_drag https://gitlab.freedesktop.org/wayland/wayland/commit/e4eb42d07305 protocol/wayland.xml
15:38wlb: wayland Merge request !344 merged \o/ (protocol: refer to wl_surface.offset in wl_data_device.start_drag https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/344)
15:40wlb: weston Merge request !1386 closed (desktop-shell/input-panel: Re-work the input surface mapping)
15:46wlb: wayland/main: Simon Ser * gitlab: make issue template the default https://gitlab.freedesktop.org/wayland/wayland/commit/3007718b0c84 .gitlab/issue_templates/default.md
15:46wlb: wayland Merge request !353 merged \o/ (gitlab: make issue template the default https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/353)
15:49wlb: wayland/main: Simon Ser * util: simplify wl_fixed_from_double() https://gitlab.freedesktop.org/wayland/wayland/commit/2a91f01d6c61 src/wayland-util.h
15:49wlb: wayland Merge request !351 merged \o/ (util: simplify wl_fixed_from_double() https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/351)
15:52wlb: wayland/main: Kirill Chibisov * protocol: clarify defaults with wl_compositor@v6 https://gitlab.freedesktop.org/wayland/wayland/commit/8a19dc19a1ee protocol/wayland.xml
15:52wlb: wayland Merge request !352 merged \o/ (protocol: clarify defaults with wl_compositor@v6 https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/352)
15:57wlb: wayland/main: Kirill Primak * protocol: improve wl_subsurface.{set_position,place_above} description https://gitlab.freedesktop.org/wayland/wayland/commit/82d8b21827c4 protocol/wayland.xml
15:57wlb: wayland Merge request !347 merged \o/ (protocol: improve wl_subsurface.{set_position,place_above} description https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/347)
16:04wlb: wayland Merge request !336 closed (client: fix segfault when removing uninitialized display->proxy.queue_link)
17:01wlb: weston/main: Daniel Stone * desktop-shell: Map input panel exactly once https://gitlab.freedesktop.org/wayland/weston/commit/bd8a6da2f0dc desktop-shell/input-panel.c
17:01wlb: weston/main: Daniel Stone * weston-keyboard: Create input_panel_surface earlier https://gitlab.freedesktop.org/wayland/weston/commit/9ced4a4f3a39 clients/keyboard.c
17:02wlb: weston Merge request !1392 merged \o/ (Fix input-panel surface/view mapping https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1392)
17:23wlb: weston Issue #842 closed \o/ (Weston (Kiosk Mode) Launches Black Screen in X11 https://gitlab.freedesktop.org/wayland/weston/-/issues/842)
20:32wlb: weston Merge request !1393 opened by Marius Vlad (mvlad) build: bump to version 12.0.95 for the RC3 release https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1393
20:38wlb: weston/main: Marius Vlad * build: bump to version 12.0.95 for the RC3 release https://gitlab.freedesktop.org/wayland/weston/commit/544618d3c60d meson.build
20:38wlb: weston Merge request !1393 merged \o/ (build: bump to version 12.0.95 for the RC3 release https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1393)
20:41wlb: weston New tag: 12.0.95 https://gitlab.freedesktop.org/wayland/weston/tags/12.0.95
20:56ara1307: hello, could someone point me to the place in wayland code where `registry_bind` function is being called
21:13wlb: wayland.freedesktop.org Merge request !71 opened by Marius Vlad (mvlad) releases: add weston 12.0.94 release https://gitlab.freedesktop.org/wayland/wayland.freedesktop.org/-/merge_requests/71
21:14wlb: wayland.freedesktop.org/main: Marius Vlad * releases: add weston 12.0.94 release https://gitlab.freedesktop.org/wayland/wayland.freedesktop.org/commit/8424d94bb070 releases/weston-12.0.95.tar.xz releases/weston-12.0.95.tar.xz.sig releases.html
21:14wlb: wayland.freedesktop.org Merge request !71 merged \o/ (releases: add weston 12.0.94 release https://gitlab.freedesktop.org/wayland/wayland.freedesktop.org/-/merge_requests/71)
21:17soreau: ara1307: it's for clients to call https://github.com/emersion/hello-wayland/blob/master/main.c#L89
21:27ara1307: soreau, this is weird... I'm using a wlroots based client and the only place where wl_registry_bind is called is from registry_global function, but registry_global is not being called from anywhere... Nevertheless manager_bind is being called somehow (I know for sure it happens from registry_bind)
21:29ara1307: In other words, wl_global_create(...,manager_bind) is called from both wlr_screencopy and wlr_export_dmabuf, and only one (wlr_screencopy's one) manager_bind is being called back
21:30ara1307: wlr_export_dmabuf's manager_bind is never called back
22:09ara1307: nevermind, found wl_registry_bind calls inside xdg-desktop-portal-wlr. Why doesn't it call the one for wlr_export_dmabuf?
22:16emersion: wlroots is used to build compositors not clients
22:17ara1307: right, sorry... so is xdg-desktop-portal-wlr going to support wlr_export_dmabuf interface? Right now it supports zwp_linux_dmabuf_v1_interface... Is it similar?
22:19emersion: not sure it's worth it
22:21emersion: wlroots would need to grow the swapchain as needed, and the client would need to use a fixed modifier
22:24ara1307: sorry, not familiar with the project enough to understand what swapchain is... Just trying to understand the basics first. Can we say that xdg-desktop-portal-wlr uses zwlr_screencopy_manager_v1_interface for screenshots and zwp_linux_dmabuf_v1_interface for screencast?
22:26emersion: no, screencopy for both
22:29ara1307: I'm trying to build a basic pipewiresrc gstreamer pipeline where headless wlroots based compositor is tied with pipewire through the xdg-desktop-portal-wlr and I see no frames are coming into pipewiresrc... I see the issue in wlroots - it basically doesn't produce any frames. Well, it produces just few and then stops with no errors. Trying to find the loop which calls "capture_output" in wlr_screencopy_v1.c as I believe it'
22:31emersion: wlroots won't produce frames if nothing changed on screen
22:31emersion: maybe try running an animated client in the headless compositor, such as weston-simple-egl
22:33ara1307: thanks, good to know... What if I connect by VNC and start moving cursor there - should this trigger frames generation?
22:49ara1307: yes, it worked. Spent a day hunting for a ghost!