Arch Linux

SD

Member

Registered: 2025-01-04

Posts: 28

Hypridle.service does not start

Using Hyprland on Arch and, up until a week ago, hypridle was running without problem, using exec-once on my hyprland.conf
Suddenly, it stopped working. This is my hypridle.conf

 general {
    lock_cmd = pidof hyprlock || hyprlock       # avoid starting multiple hyprlock instances.
    before_sleep_cmd = loginctl lock-session    # lock before suspend.
    after_sleep_cmd = hyprctl dispatch dpms on  # to avoid having to press a key twice to turn on the display.
}

listener {
    timeout = 600                                # 10min.
    on-timeout = brightnessctl -s set 10         # set monitor backlight to minimum, avoid 0 on OLED monitor.
    on-resume = brightnessctl -r                 # monitor backlight restore.
}

# turn off keyboard backlight, comment out this section if you dont have a keyboard backlight.
listener { 
    timeout = 600                                          # 10min.
    on-timeout = brightnessctl -sd rgb:kbd_backlight set 0 # turn off keyboard backlight.
    on-resume = brightnessctl -rd rgb:kbd_backlight        # turn on keyboard backlight.
}

listener {
    timeout = 900                                # 15min
    on-timeout = loginctl lock-session            # lock screen when timeout has passed
}

listener {
    timeout = 1800                                # 30min
    on-timeout = hyprctl dispatch dpms off        # screen off when timeout has passed
    on-resume = hyprctl dispatch dpms on          # screen on when activity is detected after timeout has fired.
}

listener {
    timeout = 3600                                # 1h
    on-timeout = systemctl suspend                # suspend pc
}

and the warning I get when I check hypridle.log or run hypridle on terminal is about using DBus so I run

 systemctl --stop xdg-portal-hyprland 

because it seems to be conflicting and start hypridle.service. Now it shows as being active but still does not seem to work, not even with hyprctl reload. Sometimes it does but it is, at best, unreliable and not sure if it is even working right now. I do not think it is some process causing hypridle to not activate but it is possible. I tested with a short period of time and still does not work.

SD

Member

Registered: 2025-01-04

Posts: 28

Re: Hypridle.service does not start

when I run

 systemctl --user status 

I get one particular set of processes pertaining to Dbus

 /user.slice/user-1000.slice/user@1000.service
           ├─app.slice
           │ ├─app-dbus\x2d:1.15\x2dorg.a11y.atspi.Registry.slice
           │ │ └─dbus-:1.15-org.a11y.atspi.Registry@0.service
           │ │   └─1243 /usr/lib/at-spi2-registryd --use-gnome-session

and I am not even sure what those are or if it is what causes the issue. Even if I get hypridle.service working by disabling xdg-portal-hyprland, it still gives the
error

 
[ERR] Couldn't connect to session dbus
hypridle[31833]: err: [org.freedesktop.DBus.Error.FileExists] Failed to request bus name (File exists)
hypridle[31833]: [LOG] Inhibited sleep with fd 10 

and does not do anything
also having issues with hyprpaper so I wonder if it also affects that. Seems to either be something I installed as a dependency that made it start to conflict unexpectedly or some weird bug because they were both working fine just over a week ago and I did not really do anything other than regular system update

cjvoid

Member

Registered: 2025-06-03

Posts: 1

Re: Hypridle.service does not start

I have the same problem with hypridle. It just won't start suddenly, I don't know why, same error:

    [ERR] Couldn't connect to session dbus
    hypridle[31833]: err: [org.freedesktop.DBus.Error.FileExists] Failed to request bus name (File exists)
    hypridle[31833]: [LOG] Inhibited sleep with fd 10 

Did you manage to solve the problem? What might be the cause?

SD

Member

Registered: 2025-01-04

Posts: 28

Re: Hypridle.service does not start

It ended up being a move convoluted issue, with snapper, not mounting properly and having some conflict. Basically ended up spending 2 days going back and forth with mount points, could not even access my system. I suspect that DBus was not loading properly due to conflict, lack of space or both. Rolling back solved the issue and now works out of the box. I don't think I even needed to do

 systemctl enable hypridle.service 

so it just started working again on its own