Please reconsider removing the Suspend menu option

[BitYoungjae]

First off, thank you so much for creating Omarchy. Ever since I discovered it, my M4 Pro 16-inch MacBook Pro has been sitting idle—I've completely switched over!

I was recently browsing the dev branch and noticed that the Suspend menu is being removed from omarchy-menu. (#3852, fc04525) While I don't know the full context, based on the commit message, it seems like systemctl suspend was causing issues on quite a few machines.

I'm actually one of those users who experienced problems with the Suspend feature. When resuming from suspend, all my running applications would crash and close due to "Flip event timeout" errors—apparently caused by some incompatibility between Hyprland and the nvidia-open driver.

In my case, I was able to resolve this with the following setup:

1. NVIDIA power management: Enabled nvidia-suspend.service, nvidia-resume.service, nvidia-hibernate.service, and nvidia-persistenced.service, plus set options nvidia_drm modeset=1 in /etc/modprobe.d/nvidia.conf

2. Hyprland suspend fix: Created custom systemd services that send SIGSTOP to Hyprland before NVIDIA suspends, and SIGCONT after NVIDIA resumes. This prevents Hyprland from trying to communicate with an already-suspended GPU driver. (Reference: hyprland-suspend-fix)

Since implementing these fixes, suspend/resume has been working on my machine so far—though I honestly can't say whether this is a proper solution or just a hacky workaround that happens to work for now.

If the Suspend menu is removed entirely, users like me who have taken individual measures to make this feature work will also be affected. As you likely know from your experience in the industry, removing a feature once it's been added requires careful consideration.

My suggestion: Would you please reconsider removing the Suspend menu entirely?

Even if a feature is useless for the majority of users, it might be something that a subset of users relies on heavily. There could be others like me who have found workarounds to make it work for their specific setup.

Furthermore, as I understand it, omarchy-menu is not an area that users can customize freely (like custom themes). It gets overwritten with updates, so users can't simply maintain their own version of the menu.

I apologize for the long message, but I wanted to kindly ask that this be reconsidered before the official 3.2.3 release.

Thank you for your time and for all the amazing work on Omarchy!

[SorenHJohansen]

I agree. I often use the menu to suspend my PC, and I haven’t had any issues—even with my NVIDIA 3080 GPU.

[lazzarello]

My use case on a Thinkpad X1 is to disable suspend for lid close and only suspend with the menu option. It was quite a surprise when that menu was gone today. Making a custom keybinding seems like a decent way around but isn't suspending a laptop a pretty useful feature to expose in the GUI?

[EERomeo]

I was already running a custom keybinding for suspend so no loss after the update, it just seems strange to take it out. Also I hear there was a setup printer option in the menu as well in previous versions, also strange to take that out!

[gregid]

I don't get the need for the change - if something doesn't work I don't use it. Why take the option away for those users that have suspend working correctly. At the very least can we have some instructions on how to reenable it so that it won't be overwritten with the next update?

[EERomeo]

I just added:

bind = SUPER SHIFT, S, exec, systemctl suspend

to my .config/hypr/bindings.conf
This way it does not matter what the menu changes to with future updates, I always have my custom keybind. And we already do pretty much everything by keybinds, why not suspend as well?

[gregid]

Thanks for this idea!

[jankeesvw]

I created an app that does this, I can start this from Walker

     [Desktop Entry]
     Name=Suspend
     Comment=Suspend the system
     Exec=systemctl suspend
     Icon=system-suspend
     Type=Application
     Categories=System;

[pvskp]

I do maintain a version of Omarchy's menu under my dotfiles. It's not ideal since I wouldn't be able to always enjoy the new features (because I need to "maintain" it), but helps with cases like this and I can aggregate new functionality that's not implemented by default. On my config, I just do:

bindd = SUPER SHIFT, E, Power menu, exec, ~/dotfiles/scripts/omarchy/pvskp-menu system

[jakegithub24]

How can I get back the 'suspend' option in omarchy-menu? I have recently updated Omarchy and 'suspend' option is removed from the omarchy-menu. I know I can close the lid or create a desktop entry or configure a keybinding, but omarchy-menu is comes handy when I don't wanna close the lid.

[Mitchell-Gerrard]

so in .local/share/omarchy/bin/omarchy-menu you can find in show_system_menu you can make it look like the old version
show_system_menu(){ case $(menu "System" " Lock\n󱄄 Screensaver\n󰜉 Suspend\n󰜉 Restart\n󰐥 Shutdown") in *Lock*) omarchy-lock-screen ;; *Screensaver*) omarchy-launch-screensaver force ;; *Suspend*) systemctl suspend ;; *Restart*) omarchy-cmd-reboot ;; *Shutdown*) omarchy-cmd-shutdown ;; *) back_to show_main_menu ;; esac } to add back suspend to that menu

[gregid]

The problem is it is in bin folder which means it will likely be overwritten in the next update(s)

[Mitchell-Gerrard]

Yes that is very true so you could keep a personal copy of the menu function some where and remember where the solution is for when updates happen (plus this discussion may still exist when needed). Possibly DHH could find a better solution in a future update that we wouldn't want to miss out on, so I'm hoping it is a temporary measure, and can be improved apon soon.

[jakegithub24]

so in .local/share/omarchy/bin/omarchy-menu you can find in show_system_menu you can make it look like the old version show_system_menu(){ case $(menu "System" " Lock\n󱄄 Screensaver\n󰜉 Suspend\n󰜉 Restart\n󰐥 Shutdown") in *Lock*) omarchy-lock-screen ;; *Screensaver*) omarchy-launch-screensaver force ;; *Suspend*) systemctl suspend ;; *Restart*) omarchy-cmd-reboot ;; *Shutdown*) omarchy-cmd-shutdown ;; *) back_to show_main_menu ;; esac } to add back suspend to that menu

Thanks mate, Even if it is gonna updated by new update, I can have that 'suspend' option at least for a moment.

[Dieterbe]

perhaps the menu could read a file like $HOME/.config/omarchy/menu.config, which contains customization settings (like entries to enable/disable).
this way you can you have customizations and enjoy "free updates"

[Numilani]

Making this configurable would be ideal, but even if that's not an option right now, I think removing it from all users because some users are having issues seems like the priority is backwards.

[Mitchell-Gerrard]

Removing suspend for everyone for this issue is strange, suspend is used widely, especially for those who use omarchy on portable systems.

[DarrenVictoriano]

I made a PR to allow user customization for omarchy-menu

https://github.com/basecamp/omarchy/pull/4012

[crmne]

Totally agree. Suspend is very important, and when you're using a desktop, you don't have the luxury of closing the lid to suspend.

I understand the team is not looking forward to get issues regarding suspend not working, but it's degrading the experience of most.

There could be a bunch of ways to get that working:

1. Split omarchy-menu so that we only customize the part we need, e.g.omarchy-menu-system
2. Add a config option or a menu somewhere to enable it/disable it

EDIT: This commit by @dhh solves it with option 1! 9e2ff7b

This is my .config/omarchy/extensions/menu.sh in case you're wondering:

#!/bin/bash

show_system_menu() {
  case $(menu "System" "  Lock\n󱄄  Screensaver\n󰒲  Suspend\n➜] Logout\n󰜉  Restart\n󰐥  Shutdown") in
  *Lock*) omarchy-lock-screen ;;
  *Screensaver*) omarchy-launch-screensaver force ;;
  *Suspend*) systemctl suspend ;;
  *Logout*) loginctl kill-session $XDG_SESSION_ID ;;
  *Restart*) omarchy-cmd-reboot ;;
  *Shutdown*) omarchy-cmd-shutdown ;;
  *) back_to show_main_menu ;;
  esac
}

[dhh]

Omarchy 3.3 will have a new Setup > Tweaks menu where you can bring back the suspend menu item: 9ae225a

[inad9300]

In case anyone else arrives here first, the menu option ended up as Setup > System Sleep > Enable Suspend: https://github.com/basecamp/omarchy/releases/tag/v3.3.0.

Adding on to previous comments, if my opinion amounts to anything, if the project really is about providing a great Linux experience, "it doesn't work, let's fix it" seems a better motto than "it doesn't work, remove it / sweep it under the rug".

[dhh]

You're ever so welcome to find something that Just Works across every desktop and laptop combination out there. If you find it, please open a PR 👌