You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If I watch a YouTube video in Firefox on Labwc or Hyprland, Workrave will act as if I'm not idle, even if I'm not touching the mouse or keyboard.
Workrave behaves as desired on KDE, though.
Expected behavior
Workrave should recognize idle time as, well, idle time.
** Linux (please complete the following information in case you encountered the bug on Linux):**
Distribution: Arch Linux
Distribution Version: Rolling
Desktop Environment: Varying from KDE to Labwc or Hyprland
Workrave Version: 1.11.0_beta.14.31.g0aa1d00-1
Additional context
I have a strong suspicion that this has something to do with the Wayland idle inhibit protocol, as well as different apps having different ideas on what "idle" means (i.e., where the user in front of the keyboard is idle or if the computer itself is.)
[I had a rant here that sort of amounted to "idle inhibit considered harmful", but I got rid of it because, well, it was a rant.]
The text was updated successfully, but these errors were encountered:
One thing that seems to have helped is installing xdg-desktop-portal-gtk on Arch, which implements the org.freedesktop.impl.portal.Inhibit interface. I think what this does is allow Firefox to send dbus messages that inhibit idle without having the Wayland compositor treat that as non-idleness, but I'm not sure.
In the GNOME/Mutter activity monitor, I switch to polling when an "Inhibit" is received from the GNOME session manager. Something similar may be possible in Wayland. I will check if I can reproduce this.
Describe the bug
If I watch a YouTube video in Firefox on Labwc or Hyprland, Workrave will act as if I'm not idle, even if I'm not touching the mouse or keyboard.
Workrave behaves as desired on KDE, though.
Expected behavior
Workrave should recognize idle time as, well, idle time.
** Linux (please complete the following information in case you encountered the bug on Linux):**
Additional context
I have a strong suspicion that this has something to do with the Wayland idle inhibit protocol, as well as different apps having different ideas on what "idle" means (i.e., where the user in front of the keyboard is idle or if the computer itself is.)
[I had a rant here that sort of amounted to "idle inhibit considered harmful", but I got rid of it because, well, it was a rant.]
The text was updated successfully, but these errors were encountered: