You are not logged in.
So after a recent upgrade (hypridle wasn't upgraded) hypridle has multiple issues:
1. First being that when I myself lock the session (I use hyprlock) after 30 seconds hypridle (tries to start another lock session) and then some how the current lock session also gets interrupted and then I am able to access my system without unlock it first, but the lock session as a service are also still running and whenever i try to lock it again a new lock service starts but the screen lock doesn't appear. (This problem doesn't happen if hypridle starts the lock-session ) (Also after killing all sessions of hyprlock, the next lock session works properly.
2. Also the hypridle doesn't obey the idle-inhibitor button on waybar and runs even when the inhibitor is still on.
(ps I did downgrade waybar, wayland-protocols to see if they were the problem, but they were not the ines causing the problems).
Last edited by mwooper (2024-05-12 16:16:51)
Offline
So yeah, it is caused by hyprland v 0.40.0-1; reverting to version 0.39.1-5 fixes the issue.
So I'll report it to the respective github repo issues tab
Last edited by mwooper (2024-05-12 16:14:52)
Offline
Hello,
I'm facing the same issue. Did you end up reporting the bug?
I tried looking for it in the bug tracking system of Hyprland, Hypridle, and Waybar, but to no avail.
Offline
Nah, I'll report the error after a week from now, as currently I have my exams going on.
But if you create an issue in the GitHub page, please link it here.
:-)
Offline
Actually, somebody else reported a similar issue against waybar after my post.
Here is the link: https://github.com/Alexays/Waybar/issues/3268
The reporter mentions that the same problem happens with swayidle too, which suggests that the bug is in either waybar or hyprland itself.
Since you tried downgrading waybar, maybe it is the latter...
Good luck for your exams.
Offline
Hyprland 0.41.0 solves the problem for me.
Offline
Yup; it is
Offline