Skip to content
Back to skills

Hyprland Debug

ASecurity

Debug Hyprland/Wayland issues. Use when theme switching fails, windows disappear, services crash, or displays malfunction.

  • 666 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 9, 2026
toolsgoshell

Works with

  • cli

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill hyprland-debug --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Hyprland Debug?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Hyprland Debug
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-hyprland-debug/badge)](https://www.skillsdirectory.com/skills/majiayu000-hyprland-debug)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: hyprland-debug
description: Debug Hyprland/Wayland issues. Use when theme switching fails, windows disappear, services crash, or displays malfunction.
---
<!-- @agent-architect owns this file. Delegate changes, don't edit directly. -->

<announcement>
"I'm using the hyprland-debug skill to diagnose Wayland/Hyprland issues."
</announcement>

<diagnosis_order>
1. Check Hyprland logs for errors (DRM conflicts, modesetting)
2. Check for process accumulation (multiple swaybg, waybar instances)
3. Check service logs for Wayland connection errors
4. Verify HYPRLAND_INSTANCE_SIGNATURE is current
5. Check monitor-related daemons for state-change loops
</diagnosis_order>

<log_locations>
Hyprland logs: /run/user/$(id -u)/hypr/*/hyprland.log
Hyprland socket: $XDG_RUNTIME_DIR/hypr/$HYPRLAND_INSTANCE_SIGNATURE/
User service logs: journalctl --user -u SERVICE
</log_locations>

<common_causes>
Windows disappearing: Multiple background daemons (swaybg) causing DRM page-flip conflicts.
Repeated modesetting: Monitor daemon applying config without checking current state.
Service crashes: Wayland connection lost during restart - often from upstream DRM issues.
Broken socket errors: Stale HYPRLAND_INSTANCE_SIGNATURE from crash/logout.
</common_causes>

<anti_patterns>
Restarting services with file watchers: Check logs for "reload listener" - if present, service auto-reloads.
Gentle kills for background daemons: Use SIGKILL + delay for clean replacement.
Monitor config without state check: Always check current state before hyprctl keyword commands.
SIGUSR2 for waybar theme changes: Doesn't re-fetch @imported CSS files - need full restart.
Modifying nix-managed configs: Symlinks to /nix/store are immutable - can't trigger inotify.
PartOf= for Wayland services: Causes services to stop during home-manager reload.
</anti_patterns>

<service_reload_methods>
Check bin/omarchy/ scripts for current implementations. General patterns:
- hyprctl keyword: Safe for Hyprland config changes without reload
- swaync-client -rs: CSS reload without service restart
- File watchers: Many services auto-reload on file change
- Full restart: Only when other methods don't work
</service_reload_methods>

<stale_session_fix>
Shell startup script in shell/fish/conf.d/ handles stale HYPRLAND_INSTANCE_SIGNATURE. Tests actual hyprctl connectivity and updates to working instance. tmux update-environment includes Wayland vars.
</stale_session_fix>

<verification>
After any fix: verify single instance of daemons with pgrep -c. Check Hyprland logs for new errors. Confirm services responding. Test the original failing operation.
</verification>

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.