general {
  after_sleep_cmd=hyprctl dispatch dpms on
  before_sleep_cmd=loginctl lock-session
  lock_cmd=hyprlock
}

listener {
  on-timeout=loginctl lock-session
  timeout=300
}

listener {
  on-resume=hyprctl dispatch dpms on
  on-timeout=hyprctl dispatch dpms off
  timeout=330
}

listener {
  on-timeout=systemctl suspend
  timeout=600
}

Guys I feel like there’s something wrong or odd in this config, cuz, I don’t know whats responsible for this but, it looks like things aren’t working well together, I said it looks like cuz I never caugth an actual error. So what happens is that after I leave my laptop idle, the hypridle starts doing its thing and most of the times it works, my laptop is suspended, hyprlock works etc, but sometimes, after I press any button on my keyboard to wake my laptop, I can see that my laptop is up, but all I can see is black screen, and then I have to hard shutdown the laptop, so somethings is not adding up here.

  • @[email protected]
    link
    fedilink
    English
    03 days ago

    That’s the like super convoluted way to do it, dmesg buffer is extremely short, and he will see everything relevant in the log. It’s 90% video driver issue anyeay.

    • @just_another_person
      link
      English
      13 days ago

      Dmesg is as long as the ring keeps it. Mine, for instance, is set to roll from boot to shutdown. Reading it from journal after the fact is convoluted when you’re dealing with state.