omarchy icon indicating copy to clipboard operation
omarchy copied to clipboard

System intermittently freezes post 2.0 update

Open kanishkdudeja opened this issue 5 months ago • 5 comments

Things were working well on v1.13 but Walker intermittently freezes after updating to v2.

I'm not sure if it's specific to Walker but all the times it's happened to me, it's been when i am navigating the Walker menu.

The system is completely unusable since it just takes a couple of minutes to freeze after I've logged in and I have to do a hard reboot to be able to use it.

kanishkdudeja avatar Aug 30 '25 12:08 kanishkdudeja

what's the output of yay -Q | grep walker?

abenz1267 avatar Aug 30 '25 12:08 abenz1267

Happens to me as well and I can reproduce this consistently:

When activated via:

  • hyprland keybindings (super-alt-space, super-space) it never hangs and closes cleanly on Esc.
  • Omarchy icon in top left corner of the screen it hangs on Esc.
  • terminal omarchy-menu it hangs on Esc.

However when i run it exactly the same as the hyprland binding does (see below), it works correctly and closes on Esc without freezing:

hyprctl dispatch exec "omarchy-menu"

My walker version: walker-bin 0.13.26-1

ncr avatar Sep 01 '25 11:09 ncr

Thank you @ncr, I'm able to reproduce the same using the steps that you have provided above.

kanishkdudeja avatar Sep 01 '25 19:09 kanishkdudeja

Same issue here

UPDATE: no issue after updating linux kernel to Linux 6.16.5-arch1-1

Image

havheg avatar Sep 06 '25 08:09 havheg

@abenz1267 here's the output:

yay -Q | grep walker
walker-bin 0.13.26-1

This keeps happening for me intermittently while navigating through the Omarchy menu - the system completely freezes and needs a hard restart to be usable again.

cc @dhh

kanishkdudeja avatar Sep 06 '25 18:09 kanishkdudeja

Turns out that my system was freezing due to a kernel issue because of hybrid graphics being enabled by default.

I've not had a single freeze since I've disabled integrated graphics, so I'm closing this issue.

Thanks for the help everyone!

kanishkdudeja avatar Sep 14 '25 11:09 kanishkdudeja

Hey guys i still have the same issue in 3.0 and idk how fix it

EJTP avatar Oct 13 '25 20:10 EJTP

@EJTP if you haven't already, you could start by checking kernel logs:

journalctl -k -b -1 # For the previous boot

kanishkdudeja avatar Oct 14 '25 17:10 kanishkdudeja