# Omarchy: known issues context pack (KnownFix)
Generated 2026-10-26T10:18:14Z from github.com/omacom/omarchy. Auto-extracted; verify via links. Source: https://knownfix.ai/issues/omarchy/
Fields: severity (auto-estimate) | symptom | versions mentioned | workaround (quoted from issue/comments, if any) | fixed-in (if referenced).

## Active
- [MEDIUM] Update/reboot left keyring in invalid state, browser sessions and gh auth got cleared (https://github.com/omacom/omarchy/issues/5105)
  - symptom: On Omarchy master, Hyprland 0.54.2, kernel 6.19.8-arch1-1 After updating Omarchy and rebooting my laptop, my browser logins/sessions were cleared and my GitHub CLI auth was also gone I have not fully 
  - versions: 0.54.2
  - error: `Possible keyring evidence:`
  - workaround: I applied the documented workaround: blanked the `Default` keyring password via seahorse. [comment by @jparlay]
- [MEDIUM] Waybar update indicator stuck: pre-release tag (v4.0.0-beta3) always reported as an update even when up to date (https://github.com/omacom/omarchy/issues/6754)
  - symptom: Omarchy: 3.8.3 | Arch Linux | Waybar custom/update module: "exec": "omarchy-update-available" On Omarchy, Waybar shows the "updates available" icon when the system is not up to date
  - versions: 4.0.0-beta3, 3.8.3, 3.8.4
  - error: `Omarchy: 3.8.3 | Arch Linux | Waybar custom/update module: "exec": "omarchy-update-available"`
  - workaround: none stated
- [HIGH] Crash and restart after omarchy-system-lock (https://github.com/omacom/omarchy/issues/6223)
  - symptom: Omarchy 3.8.3 PC: Framework Desktop (AMD Ryzen AI Max 300 Series) CPU/APU: AMD Ryzen AI Max 385 w/ Radeon 8050S (Strix Halo, gfx11) GPU: amdgpu 0000:c2:00.0, VRAM 16384M (UMA), ATOM BIOS 113-STRXLGEN-
  - versions: 3.8.3, 00.0, 100.6.0
  - error: `--- journal ends, next boot starts ~1 min later, no panic/reset/coredump anywhere ---`
  - workaround: I changed only `blankProcess` in `Service.qml` from: [comment by @aledeniz (1 reactions)]
- [MEDIUM] Deletion of master branch breaks updates + manual install (https://github.com/omacom/omarchy/issues/12436)
  - symptom: The master branch in this repo was deleted apparently around September 14th
  - workaround: none stated
- [HIGH] gnome-keyring-daemon crashes with NULL client pointer in secret service (https://github.com/omacom/omarchy/issues/11590)
  - symptom: gnome-keyring-daemon crashed with SIGABRT on 2026-09-13 at 01:38:02 CEST while handling D-Bus requests
  - versions: 50.0-1
  - error: `gkd_secret_service_get_pkcs11_session: assertion 'client' failed`
  - workaround: none stated
- [MEDIUM] Migration 1786643346 loops after reboot on stale Chromium SingletonLock (https://github.com/omacom/omarchy/issues/6866)
  - symptom: Omarchy: 4.0.0rc5-1 Kernel: 7.1.8-arch1-3 CPU: AMD Ryzen AI MAX+ PRO 395 GPU: AMD Strix Halo / Radeon 8060S Migration 1786643346 repeatedly asks me to close the browser windows and continue even after
  - error: `no longer existed, and the socket target under`
  - workaround: none stated
- [HIGH] Shell (quickshell) SIGSEGV when a click reassigns a Repeater's array model — crash in VDMListDelegateDataType::createMis (https://github.com/omacom/omarchy/issues/11727)
  - symptom: The Omarchy shell (quickshell) segfaulted at 19:57:33 while I clicked on its UI (bar/panel element)
  - versions: 6.11.2, 0.3.1-1, 4.0.3-1
  - error: `→ QQmlBoundSignalExpression::evaluate (×3 nested signal/binding layers)`
  - workaround: none stated
- [MEDIUM] Screen on laptop not turning back on after suspend since 3.8 upgrade (https://github.com/omacom/omarchy/issues/5755)
  - symptom: Dell Pro Max 16 Worked well up until 3.8 upgrade today, now the screen wont turn back on after suspend (have to hard reset): Anyone else seeing this?/
  - versions: 3.8, 0.54.3, 1.4.2
  - error: `Info: 16-core Intel Core Ultra 7 265H [MCP] speed (MHz): avg: 400`
  - workaround: none stated
- [MEDIUM] Intel based Macbook keyboard doesn't respond on installation (https://github.com/omacom/omarchy/issues/2415)
  - symptom: MacBook Pro 13" (2020) with an Intel chip (1,4 GHz Quad-Core Intel Core i5) I downloaded the Omarchy (v3.0.2) ISO from the website and created a bootable USB using this guide
  - versions: 3.0.2
  - error: `I downloaded the Omarchy (v3.0.2) ISO from the website and created a bootable USB using this guide. It boots successfully — I see the Omarchy logo when the inst`
  - workaround: none stated
- [MEDIUM] Speaker output not working in Asus Zephyrus G14 after 3.4 update (https://github.com/omacom/omarchy/issues/4801)
  - symptom: When updated to lastest veriosn of Omarchy (3.4)
  - versions: 3.4
  - error: `When updated to lastest veriosn of Omarchy (3.4). The native laptop speaker is not working, which was working fine pre-update. Bluetooth works fine, and other e`
  - workaround: none stated
- [MEDIUM] Omarchy menu (SUPER+SPACE) renders pure black screen after 2026-10-10 Arch update — Qt 6.12 breaks quickshell qs.* singl (https://github.com/omacom/omarchy/issues/14946)
  - symptom: After the 2026-10-10 omarchy update (which pulled Arch's Qt 6.11.2 → 6.12.0 transition together with quickshell 0.3.1 → 0.3.2), pressing SUPER+SPACE shows a fullscreen opaque black rectangle instead o
  - versions: 6.12, 6.11.2, 6.12.0
  - error: `omarchy-shell[...]: WARN scene: @Commons/Border.qml[25:-1]: TypeError: Cannot read property 'menu.border-alpha' of undefined`
  - workaround: none stated
- [MEDIUM] Keyboard layout chosen in installer isn't applied to Hyprland/fcitx5 — desktop falls back to US (https://github.com/omacom/omarchy/issues/15006)
  - symptom: During installation I selected Swiss German as the keyboard layout
  - versions: 4.0.4-1
  - error: `even after I set`
  - workaround: `~/.config/hypr/input.lua`: `hl.config({ input = { kb_layout = "ch", kb_variant = "de" } })` - `~/.config/fcitx5/profile` with `DefaultIM=keyboard-ch-de`, then restart fcitx5. [issue body]

## Recently closed (with fix/workaround info)
- Qt 6.12.0 update breaks the shell: quickshell 0.3.1-1 still built against Qt 6.11.2 (https://github.com/omacom/omarchy/issues/14469); workaround: downgrade the qt6- packages plus fcitx5-qt, python-pyqt6, qt6ct and telegram-desktop from the pacman cache, then add them to IgnorePkg until quickshell is rebui
- SDDM greeter defaults to us keymap instead of the one selected on install (https://github.com/omacom/omarchy/issues/5986); workaround: Added the following to `/usr/share/sddm/hyprland.conf`:
- [Shell] Qt 6.12 upgrade breaks Commons Color singleton (shadowed by QtQuick Color), causing black screen on me (https://github.com/omacom/omarchy/issues/14989); workaround: Downgrade `qt6-` to `6.11.2` and `quickshell` to `0.3.1-1`.