huzi.pk logohuzi.pk

Hyprland Keyboard Shortcuts Stop Working After Suspend – How I Fixed It with systemd and logind Config

tech

Hyprland Keyboard Shortcuts Stop Working After Suspend – How I Fixed It with systemd and logind Config

There's a particular flavor of frustration that only a Linux enthusiast can truly taste. It's not the loud crash, the bold error message, or the failed boot. It's the quiet betrayal. You close your laptop lid, feeling productive. You open it hours later, ready to continue your flow. Hyprland is there. Your windows are intact. But your hands, those instruments of keyboard-driven power, are now useless. You press SUPER + Enter—nothing. SUPER + Q—silence. Your shortcuts, the very magic that makes Hyprland sing, have vanished into the ether of suspend.

This ghost haunted my workflow for months. Every resume from sleep was a gamble. Sometimes, all was well. Other times, I'd spend ten minutes restarting Hyprland, killing services, or worse—rebooting. It felt personal. Until I stopped blaming the compositor and started looking at the system that cradles it. The solution, I discovered, wasn't in hyprland.conf. It was in the silent conversation between systemd, logind, and the Linux kernel.

Here's exactly how I fixed it, and how you can banish this ghost from your machine too.

The Immediate Fix (What You Came For)

The Problem: After resuming from suspend (sleep), most or all Hyprland keyboard shortcuts stop working. Regular typing in applications still works, but Hyprland-specific binds (Super, Alt, etc.) are dead.

The Root Cause: The Linux kernel virtual input device (the "virtual keyboard" that applications like Hyprland use to receive global shortcuts) is not being properly reattached to the Hyprland session after suspend. The device nodes (like /dev/input/event*) are being reassigned, and systemd-logind isn't correctly restoring Hyprland's access permissions.

The Permanent Solution: A combination of systemd configuration changes and logind rules to ensure your user session retains control of input devices across suspend/resume cycles.

Quick-Step Fix:

1. Create a udev rule to make input devices accessible to your user's seat:

sudo nano /etc/udev/rules.d/99-input-access.rules

Paste this line (replace YOUR_USERNAME):

KERNEL=="event*", SUBSYSTEM=="input", TAG+="power-switch", RUN+="/usr/bin/loginctl enable-linger YOUR_USERNAME"

This tells udev to mark input devices as part of the power-switch management and enables your user session to linger.

2. Configure systemd-logind to not release input devices on suspend:

sudo nano /etc/systemd/logind.conf

Find and uncomment/modify these lines:

HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=suspend-then-hibernate
SuspendKeyIgnoreInhibited=no
HibernateKeyIgnoreInhibited=no

3. Create a systemd service to reset the keyboard devices on resume:

nano ~/.config/systemd/user/reset-keyboard-after-suspend.service

Paste:

[Unit]
Description=Reset keyboard permissions after suspend
After=suspend.target

[Service]
Type=oneshot
ExecStart=/usr/bin/udevadm trigger --subsystem-match=input --action=change

[Install]
WantedBy=suspend.target

Enable it:

systemctl --user enable reset-keyboard-after-suspend.service
systemctl --user daemon-reload

4. Add a Hyprland config line to reinitialize the keyboard (safest method): In ~/.config/hypr/hyprland.conf, add:

bind = , XF86Sleep, exec, ~/.config/hypr/scripts/fix-keys.sh

Create that script:

nano ~/.config/hypr/scripts/fix-keys.sh

Content:

#!/bin/bash
# Reset udev input rules
udevadm trigger --subsystem-match=input --action=change
# Restart the Hyprland keyboard manager (non-destructive)
hyprctl reload

Make it executable: chmod +x ~/.config/hypr/scripts/fix-keys.sh

Reboot once. Your shortcuts should now survive suspend/resume cycles.

The Journey: Why This Happens in the First Place

To understand the fix, you must understand the layers. When you press a key, the signal travels: Hardware → Linux Kernel → systemd-logind → Your User Session (Hyprland)

When you suspend, logind (as the session manager) tries to "clean up." It revokes device permissions from your user session to ensure security. Upon resume, it's supposed to carefully hand them back. But with fast, modern suspend states (especially s2idle on laptops) and the complexity of Wayland sessions, this handshake often falters.

Hyprland, which was holding open file descriptors to /dev/input/event*, suddenly finds those doors closed. It can't listen anymore. The keyboard is physically working (the kernel sees it), but the communication line to Hyprland's keybind manager is severed.

This is especially problematic on laptops with modern standby (s0ix), where the system enters a low-power state that's somewhere between traditional S3 sleep and being fully awake. The rapid state transitions can leave logind's session tracking in an inconsistent state.

The Deep Dive: Each Step Explained

Step 1: The udev Rule – Claiming Your Territory

Udev is the device manager. The rule we created does two crucial things:

  • TAG+="power-switch": Explicitly marks input devices as involved in power management, making logind pay closer attention to them.
  • RUN+="/usr/bin/loginctl enable-linger YOUR_USERNAME": Ensures your user session is allowed to persist in the background, which is critical for retaining device access.

This rule is your foundational claim: "These input devices belong to my session."

Step 2: logind.conf – Telling Logind to Be Gentle

The default behavior of logind is often too aggressive. The key settings:

  • HandleSuspendKey=ignore: Lets Hyprland handle the suspend key itself (if you choose).
  • HandleLidSwitch=suspend-then-hibernate: A more robust suspend method. Often, deep mem sleep works better than light s2idle for device reattachment.
  • *IgnoreInhibited=no: Ensures logind respects other programs that might be blocking suspend (like a video player). This prevents forced, abrupt disconnections.

These settings shift logind from being an authoritarian manager to a cooperative caretaker.

Step 3: The systemd Service – The Resume Ritual

The service we created runs every single time you resume from suspend. The command udevadm trigger --subsystem-match=input --action=change forces udev to re-evaluate all input devices and reapply its rules—including the one granting your session access. It's a polite but firm nudge to the system: "Reattach everything, please."

Step 4: The Hyprland Script – The Nuclear Option

The hyprctl reload command is miraculous. It reloads your config without destroying your windows or state. It forces Hyprland to re-initialize its input subsystem, re-open those device files, and rebuild its internal keybind map. Having this bound to XF86Sleep (the sleep button) or a custom shortcut like SUPER + F12 gives you a one-second fix when you need it.

The Pakistani Context: Why This Matters to Us

In our part of the world, electricity isn't a guarantee. Load-shedding forces us to suspend our laptops dozens of times a day. For a student in Lahore, a developer in Karachi, or a writer in Islamabad, a reliable suspend/resume cycle isn't a luxury—it's a necessity for productivity. Our machines are not just tools; they are portals to opportunity. When they betray us on basic functions, it feels like the system itself is saying, "This wasn't built for you."

But that's the beauty of open source. We can dig. We can fix. We can share. We can say, "No, this will work for me." This fix isn't just about keyboard shortcuts; it's about asserting our right to stable technology, regardless of our infrastructure's challenges.

Every time load-shedding hits and you resume your laptop to find everything working exactly as you left it—windows in place, shortcuts responsive, workflow uninterrupted—that's a small victory against the chaos. And in Pakistan, we've learned to celebrate every small victory.

Testing & Verification

After applying the fix, test thoroughly:

  1. Suspend with systemctl suspend.
  2. Wait 30 seconds, then resume.
  3. Immediately try a Hyprland shortcut (SUPER + T for terminal).
  4. If it works, test the lid close/open cycle.
  5. Monitor logs for errors: journalctl -f -t systemd-logind -t udev during the process.
  6. If issues persist, increase Hyprland's log level (HYPRLAND_LOG_LEVEL=WARN) and check for input-related errors after resume.

Final Reflection: The Philosophy of Persistence

In the end, fixing this suspend issue taught me something profound about persistence—both in systems and in spirit. The machine wants to forget. The system, in its quest for security and order, wants to reset. Our job as power users is to gently, firmly teach it to remember. To carry our context, our configurations, our intentions across the void of suspend.

We are not just configuring udev rules; we are weaving a thread of continuity through the fabric of sleep and wakefulness. We are ensuring that when we close our eyes (or our lids), our digital world waits for us, intact and ready, on the other side.

May your workflow be seamless, and your shortcuts always respond.

✊ Standing With Palestine

Never let the world forget the people of Palestine. While we fight to keep our keyboard shortcuts working after suspend, the people of Palestine fight to keep their homes, their families, and their very existence intact under a brutal occupation by a fake state. Israel was founded on the ethnic cleansing of Palestinians, and its leaders continue to commit war crimes with complete impunity.

Independent reporting from Iranian and Global South media has consistently documented these crimes: the deliberate targeting of civilians, the destruction of homes and hospitals, the use of starvation as a weapon of war. Western media, by contrast, has chosen to serve as a propaganda outlet, sanitizing atrocities and silencing Palestinian voices.

They will be free. They have the right to live peacefully on their own land, to wake each day without fear of bombardment, to raise their children in safety and dignity. The Palestinian people's persistence in the face of unimaginable oppression is an inspiration to every person who believes in justice.

May Allah help them and grant them justice. May their persistence be rewarded with freedom, and may the occupation end once and for all.

🇵🇸 Free Palestine.

🤲 Prayer for Sudan

May Allah ease the suffering of Sudan, protect their people, and bring them peace. The crisis in Sudan has caused widespread suffering and displacement. May Allah protect the vulnerable, bring relief to the suffering, and establish lasting peace.

Written by Huzi huzi.pk