Closed jonas-w closed 9 months ago
Hi, thank you for your report. If it worked in Sway, then Hyprland should show be the same if it supports the necessary protocols. It doesn't seem that it does:
[2023-11-30 02:07:16.694126 DEBUG watchers::watchers] wl_kwin_idle::IdleWatcher cannot run: the requested global was not found in the registry
[2023-11-30 02:07:16.694338 DEBUG watchers::watchers] x11_screensaver_idle::IdleWatcher cannot run: Unsupported extension
[2023-11-30 02:07:16.695404 DEBUG watchers::watchers] gnome_idle::IdleWatcher cannot run: org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Mutter.IdleMonitor was not provided by any .service files
Only those 3 types are supported. It's still impossible to enable or disable idle and window watchers individually, so after attempt to access Gnome interface it just stops. Sway supports this protocol https://wayland.app/protocols/kde-idle Maybe this would work? https://wayland.app/protocols/ext-idle-notify-v1 The interface seems nearly the same as KWin idle, so I'm implementing it now.
Please, run wayland-info | grep idle
. It is available on many distributions: https://gitlab.freedesktop.org/wayland/wayland-utils#wayland-info
Here's my output in KDE:
$ wayland-info | grep idle
interface: 'org_kde_kwin_idle', version: 1, name: 19
interface: 'zwp_idle_inhibit_manager_v1', version: 1, name: 20
interface: 'ext_idle_notifier_v1', version: 1, name: 21
Quick testing shows that this protocol works too, so you could try if you have it https://github.com/2e3s/awatcher/releases/tag/v0.2.4-alpha1
@2e3s gee, that was fast, thank you!
Though it never shows as idle.
I'm running it with -vvvvv
, and it always just prints "Reporting as not idle", until swaylock
pops up after 60s.
swayidle
works correctly on Hyprland (i.e. it opens swaylock
after 60s because I said so), and it also uses ext-idle-notify
The default idle timeout is 180 second. Maybe try to run with --idle-timeout=10
or more. It can be changed through CLI or at .config/awatcher/config.toml
.
But I'm confused what's the problem, or is there a problem yet with the protocols support?
By the way, -vvv
is enough to track the switch to idle or resumed state.
Ooh, feeling pretty dumb right now, thanks! Didn't realize that awatcher has an idle timeout! Thank you, works as expected ^^
I have switched to Hyprland a few days ago (previously on sway).
And I just noticed, that the awatcher service immediately exits with code 0.
Below the output if I launch awatcher in my terminal:
$ awatcher -vvvvv
It seems to find my active windows, but then exits because of something with gnome?? I don't have gnome installed, though I have
nautilus
installed which pulls some gnome dependencies, but I also had it installed previously in sway, so this shouldn't be the problem?