06:30 shtrom: hi all
06:31 shtrom: I'm trying to get to the bottom of a weird issue on a Debian bookworm box, where GDM3 doesn't want to start after a power-cut induced reboot
06:31 shtrom: I'm down to looking at wayland and trying to make sense of what's happening
06:31 shtrom: but save for starting Xwayland and watching it fail miserably, I'm not really sure how to debug further
06:32 shtrom: strace is not really helpful save for a permission issue on /dev/dri/renderD128 which I think is a red herring
06:32 shtrom: and running as user and/or root never seem to work, but without an indication why
06:33 shtrom: worth noting is that I'm connected to the box via SSH (it's literally not in the same country as where I am)
06:33 shtrom: any hint or pointer about where to look for further debugging would be most welcome
06:34 sh-RE_: better in a tmux (:
06:35 shtrom: more context on my issue here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059245
14:26 peelz: is there anything that says how ext_idle_notify_v1 is supposed to interact with idle_inhibit_unstable_v1?
14:26 peelz: sway doesn't send idle notifications if inhibited: https://github.com/swaywm/sway/blob/22d0dd8bde62592ff34d354e059cdc6e09879cb4/sway/input/seat.c#L102
14:26 peelz: and unfortunately that prevents standalone screen lockers (e.g swaylock) to turn off the monitors after a period of inactivity :(
14:29 emersion: that's the whole point
14:29 emersion: idle-inhibit exists for preventing screen lockers from kicking in while you're watching a movie
14:30 peelz: right, except it would be nice to ignore inhibition if swaylock is already active
14:31 peelz: so dpms can work on the lockscreen
14:39 peelz: if I have an inhibitor active and I manually trigger the lockscreen, swayidle won't be able to turn off the outputs after a timeout
14:40 emersion: that's arguably a sway issue, it should ignore inhibitors which are not visible on-screen
14:43 peelz: ah I see, create_inhibitor() takes a surface
15:00 peelz: emersion, if sway were to ignore inhibitors that aren't on screen, how would one go about creating an inhibitor that isn't associated with a window (e.g a CLI tool)? sorry for the uneducated question, I'm still quite new to wayland internals
15:01 emersion: CLI tools don't use wayland
15:01 peelz: well there's wl-clipboard (wl-copy/wl-paste)
15:01 peelz: it uses an invisible surface to do clipboard stuff afaik
15:01 emersion: sway has commands to tweak the idle inhibition, so one could use that from a script
15:02 emersion: no, it uses a wayland protocol for clipboard managers
15:03 peelz: huh? so wl-clipboard doesn't use wayland but it uses the wayland clipboard protocol?
15:03 emersion: we use "a wayland protocol" as an abbreviation of "a wayland protocol extension", it's still just wayland
15:04 peelz: right, but you said "CLI tools don't use wayland"
15:04 peelz: by that definition, doesn't wl-clipboard (which uses the wayland clipboard protocol extension) use wayland?
15:09 peelz: sorry, I think I got confused. I see you were talking about how wl-clipboard uses the wayland clipboard protocol (which doesn't use any surfaces)
15:09 peelz: I'll take a look at sway's inhibit_idle command. That might just be what I need. Thanks :D
15:32 kennylevinsen: peelz: wl-clipboard is a hack and an outlier. It creates a window briefly to get permission to use the clipboard it it can't get access to the clipboard management protocols
15:33 kennylevinsen: in the context of sway, CLI tools usually use sway's IPC or call swaymsg
15:40 peelz: kennylevinsen, ah gotcha. I thought I was misremembering about the window thing. Why does it need to create a window? Is it a protocol requirement? I'm trying to find an answer on wayland.app
15:41 kennylevinsen: You are not allowed access to the clipboard unless you have focus
15:41 kennylevinsen: and you can't have focus without a window
15:41 peelz: oh
15:41 peelz: I see from the wl-clipboard meson.build that they use gtk_primary_selection and wlr_data_control: https://github.com/bugaevc/wl-clipboard/blob/master/src/protocol/meson.build
15:42 kennylevinsen: gtk_primary_selection is deprecated and replaced by the primary selection protocol
15:42 peelz: what's the protocol for the clipboard (not primary selection)?
15:43 kennylevinsen: wlr data control is a privileged clipboard management protocol that not all compositors support, meant for writing (privileged) clipboard managers
15:43 kennylevinsen: peelz: wl_data_offer/source/device/device_manager in the core protocol
15:43 peelz: right, that's what I was getting at. It's not implemented by gnome-shell for example
15:43 peelz: oh alright
15:47 peelz: thanks for answering my questions, I appreciate it
18:03 wlb: wayland Merge request !284 closed (wayland-client: Add wl_display_get_default_queue)
18:03 wlb: wayland/main: Julian Orth * protocol: wl_subsurface will never be focused https://gitlab.freedesktop.org/wayland/wayland/commit/6626d4d98c19 protocol/wayland.xml
18:04 wlb: wayland Merge request !236 merged \o/ (protocol: wl_subsurface will never be focused https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/236)
18:27 wlb: wayland-protocols/main: MaxVerevkin * linux-dmabuf: sync changes from unstable to stable https://gitlab.freedesktop.org/wayland/wayland-protocols/commit/9d83649b4947 stable/linux-dmabuf/linux-dmabuf-v1.xml
18:27 wlb: wayland-protocols Merge request !266 merged \o/ (linux-dmabuf: sync changes from unstable to stable https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/266)
18:35 wlb: wayland-protocols Merge request !259 closed (Draft: (Re)move Xwayland related protocols)
18:44 wlb: wayland-protocols/main: Jonas Ådahl * xdg-shell: Clarify what a toplevel by default includes https://gitlab.freedesktop.org/wayland/wayland-protocols/commit/46f201bd7b32 stable/xdg-shell/xdg-shell.xml
18:44 wlb: wayland-protocols Merge request !222 merged \o/ (xdg-shell: Clarify what a toplevel by default includes https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/222)
18:51 wlb: wayland-protocols Merge request !219 closed (README.md: Explain that "unstable" label is not semantical)
18:57 wlb: wayland-protocols Merge request !270 opened by Simon Ser (emersion) ci: upgrade ci-templates and Debian https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/270
20:13 wlb: wayland Issue #426 closed \o/ (Adding restrictions to global binding and resource creation. https://gitlab.freedesktop.org/wayland/wayland/-/issues/426)