-
Notifications
You must be signed in to change notification settings - Fork 741
[Proposal] Update Omakub based on Omarchy #543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…cripts and font size switcher
Updated PR description |
wonderful, such an amazing work hope this could be merged someday 😄 |
At this point, I’d say the main implementations are complete, so I can now focus on the migrations. 😄 In the meantime, if anyone wants to try installing on a fresh Ubuntu setup, that would be very helpful—along with testing the available features. Any feedback or issues will be useful for fine-tuning the work. 🙏🏻
I hope so! 👀 |
Ultimately, I think it's due to an x11 session and NVIDIA card issue. If you try logging out and selecting Ubuntu (Wayland), it should work fine. |
Updated PR description |
…stallation script
Updated to |
This is a big body of work! But it's too much of a departure from the Omakub that I already consider to be in a great state. Feel free to do a fork and add this to a spin-off, though. But I can't take all this for Omarchy as-is. Thanks again for suggesting anyway! |
I can see which project is the favorite child 🙄 |
Note
This PR is now mostly complete.
The migration process between versions, however, cannot be tested properly until it’s available on an Omakub branch.
In the meantime, I’d still appreciate any feedback from those willing to try out fresh installations or test the new features, given the amount of work involved in the refactoring.
Although Omakub is close to completion, I believe it could benefit from a fresh approach, inspired by the work carried out with Omarchy. The structure, themes, and menus developed there not only provide more than what comes by default with Omakub and Ubuntu, but also make it easier to contribute to the maintenance and improvement of the ecosystem. In addition, they simplify the creation of themes and customizations, which are currently harder to implement in Omakub.
In my view, these changes would be an improvement for everyone who still relies on Omakub in their daily workflows.
Table of Content
Installation
For anyone interested in trying this out—and possibly contributing or sharing feedback—I’ve prepared an installation script.
Important
This is not a migration. Do not use it on machines already running Omakub. It is intended only for fresh setups or test environments (e.g. custom-built VMs).
Note
Installation on systems using LVM with disk encryption is not supported. See Known Issues.
To install Omakub as proposed in this PR, simply run:
curl -fsSL https://omakasui.org/omakub | bash
Like Omakub, the installation process takes quite a long time. You might want to grab a coffee while it runs. ☕
Hotkeys
The following hotkeys have been added:
Super
+Space
Super
+Alt
+Space
Super
+F
Super
+Ctrl
+Space
Super
+Shift
+Ctrl
+Space
Unified Menu
Among the features imported from Omarchy, the one that stands out the most is the Unified Menu.
While
gum
does a great job of providing a simple TUI with just a few commands, I believe a dedicated, more visually polished tool can serve as the real control center for Omakub.Taking inspiration from Omarchy, I rebuilt the menu entirely using what’s available in Omakub. The only significant change is the use of
wofi
instead ofwalker
. I’d rather wait for version1.0.0
(which currently requires compiling from source) to avoid introducing a heavy migration. In the meantime,wofi
is already available in the Ubuntu repositories.Screencast.from.2025-09-04.09-50-22.webm
App Launcher
With the introduction of
wofi
, we also took the opportunity to migrate the application launcher from ULauncher to it.This provides a single tool for managing on-screen launchers, improves compatibility, and ensures consistent styling.
Themes
In addition to the default themes, two new ones have been introduced:
osaka-jade
andcatppuccin-latte
.Osaka Jade
Catppuccin Latte
Extra Themes
Support for installing additional themes has also been added, following the same rules already in place for Omarchy:
Obviously, you can't use Omarchy themes. You'll need to create new ones, again following similar rules to Omarchy's.
Creating new themes no longer requires separate style installation scripts.
All that’s needed now are the appropriate
.theme
files.Some files are optional (for example: VSCode, Light/Dark, Chromium, and Cursor).
Here’s an overview of the files that should be included:
I’ve also created some test themes as examples:
omakub-sythwave84-theme
omakub-rose-pine-dark-theme
Synthwave '84
Rose Pine (Dark)
Boot / Login Screen
These components have also been updated, following the approach used in Omarchy. Full-disk encryption is not included, but GDM3 has been retained for consistency and ease of use.
Logos, positioning, and color choices were made at my discretion—and with limited expertise in this area. If anyone with more design experience is willing to help refine them, contributions would be very welcome.
Default Apps
Following the approach taken with Omarchy and the Omakase Doctrine, I’ve decided to remove the step of selecting applications during installation. Instead, Omakub will come preconfigured with the default apps from both Omarchy and Omakub.
To make customization easier, I plan to add the option to uninstall multiple apps or web apps at once. This way, new users will get a ready-to-use, functional system out of the box, while those who prefer can later tailor it by removing what they don’t need.
These are the default apps
What's Changed
Added
applications/
,bin/
,default/
,config/
,themes/
directories replacing old scattered structure.theme
configuration filesosaka-jade
andcatppuccin-latte
applications/
Changed
gnome.theme
,icons.theme
,tophat.theme
andvscode.theme
files instead of shell scriptsapplications/install/
and removers toapplications/remove/
install/terminal
andinstall/desktop
toinstall/packaging/
and installation configs intoinstall/config
.desktop
file now syncs with Omakub defaultsFixed
Removed
bin/omakub-sub/
structure.desktop
files, now integrated in Unified Menu or in packagesFixes and Closes
Known Issues
x11
andwofi
Similar to ULauncher,
wofi
doesn’t work properly when the session is running onX11
. This mainly affects users with NVIDIA graphics cards, where the system is usually forced to use Wayland (through a script in/install/login/gdm3.sh
).I’m looking into a way to enforce Wayland or to find a compatible alternative, but I’d rather take the time to properly understand the options.
In the meantime, if you run into issues with
wofi
on your first login, just log out and, on the next attempt, select Ubuntu (Wayland) from the bottom-right corner. After that, the system will always remember and use this option.Omakub Logo
I generated them using python3 scripts and my limited design knowledge, so they may not be the best and may have some irregularities. I'll defer to those with more experience and skill than me!
Boot and LVM
Apparently, if the disk is encrypted using LVM, the boot process hangs. This happens because LVM expects the password to unlock the disk before proceeding with the login.
A solution would be to either prevent installation when LVM is detected, or block the boot process and present a password entry form.
Roadmap