fix: apply the GSK_RENDERER fix to the autostarted Walker service

[r-witz]

The menu takes several seconds to show up the first time after a boot, then every open after that is instant. Same thing reported in #2723.

I dug into it on my machine (Raptor Lake iGPU + RTX 4060 laptop) and it turns out the GSK_RENDERER fix from 30ddfed doesn't actually apply anymore. That commit moved GSK_RENDERER=cairo out of the Hyprland envs and into the line of omarchy-launch-walker that spawns the service:

But since Walker became a systemd autostart (c17bd85), the service is already running by the time you press the keybind, started from walker.desktop, without the variable. The pgrep guard always passes, so on a normal boot the cairo env never gets applied to anything.

So the fix is to set it in walker.desktop itself, plus a migration that re-copies the desktop file, reloads the user daemon so the generated unit picks up the new Exec, and restarts Walker.

Fixes #2723

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a migration to update Walker’s autostart configuration so it runs with GSK_RENDERER=cairo, addressing rendering issues for the autostarted Walker service.

Changes:

• Added a migration script to copy the updated walker.desktop into the user autostart directory and restart Walker.
• Updated walker.desktop to launch Walker with GSK_RENDERER=cairo.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
migrations/1781295157.sh	New migration that installs the updated autostart desktop entry and restarts Walker.
default/walker/walker.desktop	Updates the Exec line to force the Cairo renderer via an environment variable.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.