{"schema_version":1,"generated_at":"2026-10-26T10:18:14Z","issues_generated_at":"2026-10-26T10:12:02Z","lookback_days":45,"license_note":"Issue metadata from public GitHub repos.","harness":"omarchy","issues":[{"id":"omacom/omarchy#5105","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":5105,"title":"Update/reboot left keyring in invalid state, browser sessions and gh auth got cleared","url":"https://github.com/omacom/omarchy/issues/5105","state":"open","state_reason":null,"labels":["bug"],"created":"2026-03-23T18:06:58Z","updated":"2026-10-25T14:29:36Z","closed":null,"reactions":11,"thumbs_up":11,"comments":29,"severity":"medium","severity_reasons":["engagement 40","class:install/update","class:auth/session"],"topic":"install/update","classes":["install/update","auth/session"],"cosmetic_ui":false,"summary":"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 diagnosed the root cause, but this…","versions":["0.54.2"],"error_snippets":["Possible keyring evidence:"],"workaround":{"text":"I applied the documented workaround: blanked the `Default` keyring password via seahorse.","source":"comment by @jparlay","url":"https://github.com/omacom/omarchy/issues/5105#issuecomment-6251287775"},"fixed_in":null,"score":162.7,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#6754","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":6754,"title":"Waybar update indicator stuck: pre-release tag (v4.0.0-beta3) always reported as an update even when up to date","url":"https://github.com/omacom/omarchy/issues/6754","state":"open","state_reason":null,"labels":["bug"],"created":"2026-08-12T14:50:47Z","updated":"2026-10-08T03:56:19Z","closed":null,"reactions":12,"thumbs_up":12,"comments":7,"severity":"medium","severity_reasons":["engagement 19","class:install/update","class:crash/hang"],"topic":"install/update","classes":["install/update","crash/hang","self-host/headless"],"cosmetic_ui":false,"summary":"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. This icon is controlled by bin/omarchy-update-available…","versions":["4.0.0-beta3","3.8.3","3.8.4"],"error_snippets":["Omarchy: 3.8.3 | Arch Linux | Waybar custom/update module: \"exec\": \"omarchy-update-available\"","The problem is that the icon **never disappears**, even when the system is fully up to date.","If the remote version differs from the local version, the script prints `update available` and returns exit code `0`, causing Waybar to display the update icon.","This creates an endless loop:","In other words, the update checker is reporting an update that the stable channel **cannot and will not install**."],"workaround":null,"fixed_in":null,"score":122.7,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#6223","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":6223,"title":"Crash and restart after omarchy-system-lock","url":"https://github.com/omacom/omarchy/issues/6223","state":"open","state_reason":null,"labels":["bug","compatibility"],"created":"2026-07-14T20:38:58Z","updated":"2026-10-08T03:22:08Z","closed":null,"reactions":5,"thumbs_up":5,"comments":27,"severity":"high","severity_reasons":["title:breakage"],"topic":"crash/hang","classes":["crash/hang","install/update","network"],"cosmetic_ui":false,"summary":"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-001 SMU firmware: 0x0a640600 (100.6.0)…","versions":["3.8.3","00.0","100.6.0","7.1.3-arch1"],"error_snippets":["--- journal ends, next boot starts ~1 min later, no panic/reset/coredump anywhere ---","There is no clean shutdown in the journal (no unmounting sequence, no kernel panic, no amdgpu reset/timeout messages) — the journal just stops, consistent with a hard hang forcing an external/hardware reset.","Journal simply ends mid-stream, no error, no shutdown sequence:"],"workaround":{"text":"I changed only `blankProcess` in `Service.qml` from:","source":"comment by @aledeniz (1 reactions)","url":"https://github.com/omacom/omarchy/issues/6223#issuecomment-5362858718"},"fixed_in":null,"score":115.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#12436","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":12436,"title":"Deletion of master branch breaks updates + manual install","url":"https://github.com/omacom/omarchy/issues/12436","state":"open","state_reason":null,"labels":["bug"],"created":"2026-09-18T17:17:23Z","updated":"2026-10-13T16:41:59Z","closed":null,"reactions":15,"thumbs_up":15,"comments":10,"severity":"medium","severity_reasons":["engagement 25","class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"The master branch in this repo was deleted apparently around September 14th. This breaks the omarchy-update-git step for any system where the local git copy is set up to track the master branch. Since the documented flow for upgrading to…","versions":[],"error_snippets":[],"workaround":null,"fixed_in":null,"score":104.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#11590","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":11590,"title":"gnome-keyring-daemon crashes with NULL client pointer in secret service","url":"https://github.com/omacom/omarchy/issues/11590","state":"open","state_reason":null,"labels":[],"created":"2026-09-13T00:06:45Z","updated":"2026-10-22T01:44:00Z","closed":null,"reactions":2,"thumbs_up":2,"comments":11,"severity":"high","severity_reasons":["title:breakage"],"topic":"always-on/daemon","classes":["always-on/daemon","crash/hang","network"],"cosmetic_ui":false,"summary":"gnome-keyring-daemon crashed with SIGABRT on 2026-09-13 at 01:38:02 CEST while handling D-Bus requests. Signal: SIGABRT (from glogdefaulthandler calling abort()) Root cause: NULL client pointer in gkdsecretservicegetpkcs11session cascading…","versions":["50.0-1"],"error_snippets":["gkd_secret_service_get_pkcs11_session: assertion 'client' failed","gkd_secret_service_publish_dispatch: assertion 'client' failed","g_variant_new: expected GVariant of type 'v' but received value has type '(null)'","This is likely a gnome-keyring upstream bug (NULL pointer validation), but reporting here as well in case Omarchy's packaging or D-Bus integration is involved."],"workaround":null,"fixed_in":null,"score":91.4,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#14469","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":14469,"title":"Qt 6.12.0 update breaks the shell: quickshell 0.3.1-1 still built against Qt 6.11.2","url":"https://github.com/omacom/omarchy/issues/14469","state":"closed","state_reason":"completed","labels":[],"created":"2026-10-07T19:41:59Z","updated":"2026-10-08T17:13:48Z","closed":"2026-10-08T17:13:48Z","reactions":16,"thumbs_up":13,"comments":16,"severity":"medium","severity_reasons":["engagement 32","class:install/update"],"topic":"install/update","classes":["install/update","always-on/daemon","mcp/tools"],"cosmetic_ui":false,"summary":"AMD Ryzen 9 5900X, NVIDIA RTX 2080 Ti, Omarchy 4.0.4 Today's update pulls Qt 6.12.0 from extra, but quickshell 0.3.1-1 is still built against Qt 6.11.2. After the update and a shell restart: The bar is gone. Every menu (Super+Space…","versions":["6.12.0","0.3.1-1","6.11.2","4.0.4"],"error_snippets":["WARN scene: @plugins/bar/Bar.qml[81:-1]: TypeError: Cannot read property 'active' of undefined","WARN scene: @plugins/bar/Bar.qml[75:3]: Unable to assign [undefined] to QColor","WARN scene: @Ui/Button.qml[57:-1]: TypeError: Cannot read property 'background' of undefined","WARN scene: @Ui/PanelToolTip.qml[22:-1]: TypeError: Cannot read property 'background' of undefined","Today's update pulls Qt 6.12.0 from extra, but `quickshell 0.3.1-1` is still built against Qt 6.11.2. After the update and a shell restart:"],"workaround":{"text":"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 rebuilt.","source":"issue body","url":"https://github.com/omacom/omarchy/issues/14469"},"fixed_in":null,"score":84.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#6866","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":6866,"title":"Migration 1786643346 loops after reboot on stale Chromium SingletonLock","url":"https://github.com/omacom/omarchy/issues/6866","state":"open","state_reason":null,"labels":["bug"],"created":"2026-08-14T12:54:41Z","updated":"2026-10-08T04:17:47Z","closed":null,"reactions":9,"thumbs_up":9,"comments":4,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","network"],"cosmetic_ui":false,"summary":"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 Chromium is completely stopped…","versions":[],"error_snippets":["no longer existed, and the socket target under","was rebound to the pinned Copy URL extension id","Migration `1786643346` repeatedly asks me to close the browser windows and continue even after Chromium is completely stopped. Pressing Continue just returns to the same prompt.","There was no Chromium-family process running, PID `112033` no longer existed, and the socket target under `/tmp` no longer existed.","The migration nevertheless considers the profile open because `profile_open()` tests `-L \"$profile/SingletonLock\"`. That remains true for a stale symlink, so the `while affected_profile_open` loop cannot make progress re"],"workaround":null,"fixed_in":null,"score":83.3,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#11727","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":11727,"title":"Shell (quickshell) SIGSEGV when a click reassigns a Repeater's array model — crash in VDMListDelegateDataType::createMissingProperties","url":"https://github.com/omacom/omarchy/issues/11727","state":"open","state_reason":null,"labels":["bug"],"created":"2026-09-13T18:18:01Z","updated":"2026-10-24T21:29:20Z","closed":null,"reactions":1,"thumbs_up":1,"comments":12,"severity":"high","severity_reasons":["title:breakage"],"topic":"crash/hang","classes":["crash/hang","install/update"],"cosmetic_ui":false,"summary":"The Omarchy shell (quickshell) segfaulted at 19:57:33 while I clicked on its UI (bar/panel element). Quickshell's in-process crash recovery restarted the engine (\"Quickshell has been restarted\") and the bar came back by itself. No data…","versions":["6.11.2","0.3.1-1","4.0.3-1","6.11.2-3"],"error_snippets":["→ QQmlBoundSignalExpression::evaluate (×3 nested signal/binding layers)","→ QV4::Module::evaluate → QV4::Runtime::TypeofName::call","(bar/panel element). Quickshell's in-process crash recovery restarted the engine","The crash happened while the engine was handling a mouse release on a shell","Clicking a bar/panel widget should never take down the shell engine."],"workaround":null,"fixed_in":null,"score":78.4,"first_seen":"2026-10-25T09:11:37Z"},{"id":"omacom/omarchy#5755","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":5755,"title":"Screen on laptop not turning back on after suspend since 3.8 upgrade","url":"https://github.com/omacom/omarchy/issues/5755","state":"open","state_reason":null,"labels":["bug","compatibility"],"created":"2026-05-11T11:20:14Z","updated":"2026-10-08T01:59:37Z","closed":null,"reactions":6,"thumbs_up":3,"comments":7,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","always-on/daemon","crash/hang","auth/session"],"cosmetic_ui":false,"summary":"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","24.1.11"],"error_snippets":["Info: 16-core Intel Core Ultra 7 265H [MCP] speed (MHz): avg: 400","min/max: 400/5300:4600:2500","API: EGL Message: EGL data requires eglinfo. Check --recommends.","May 11 12:54:34 Laptop fprintd[8491]: Device reported an error during verify: Cannot run while suspended.","Anyone else seeing this?/"],"workaround":null,"fixed_in":null,"score":78.3,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#2415","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":2415,"title":"Intel based Macbook keyboard doesn't respond on installation","url":"https://github.com/omacom/omarchy/issues/2415","state":"open","state_reason":null,"labels":["bug","mac","compatibility"],"created":"2025-10-12T22:59:44Z","updated":"2026-10-07T22:25:16Z","closed":null,"reactions":7,"thumbs_up":7,"comments":8,"severity":"medium","severity_reasons":["engagement 15","class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"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. It boots successfully — I see the Omarchy logo when the…","versions":["3.0.2"],"error_snippets":["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 installation starts — but at the first step (language selection)"],"workaround":null,"fixed_in":null,"score":77.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#4801","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":4801,"title":"Speaker output not working in Asus Zephyrus G14 after 3.4 update","url":"https://github.com/omacom/omarchy/issues/4801","state":"open","state_reason":null,"labels":["bug"],"created":"2026-02-28T10:41:07Z","updated":"2026-10-16T07:41:56Z","closed":null,"reactions":7,"thumbs_up":7,"comments":8,"severity":"medium","severity_reasons":["engagement 15","class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"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 external audio peripheral works good","versions":["3.4"],"error_snippets":["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 external audio peripheral works good"],"workaround":null,"fixed_in":null,"score":77.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#14946","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":14946,"title":"Omarchy menu (SUPER+SPACE) renders pure black screen after 2026-10-10 Arch update — Qt 6.12 breaks quickshell qs.* singletons","url":"https://github.com/omacom/omarchy/issues/14946","state":"open","state_reason":null,"labels":[],"created":"2026-10-11T00:34:30Z","updated":"2026-10-22T09:56:47Z","closed":null,"reactions":2,"thumbs_up":2,"comments":6,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"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 of the menu. The menu itself is…","versions":["6.12","6.11.2","6.12.0","0.3.1"],"error_snippets":["omarchy-shell[...]: WARN scene: @Commons/Border.qml[25:-1]: TypeError: Cannot read property 'menu.border-alpha' of undefined","Color.foreground -> undefined (should be \"#cacccc\")","Color.menu -> undefined","Util.abs(-5) -> TypeError: Property 'abs' of object Util_QMLTYPE_3 is not a function","; same class of errors from user plugins:"],"workaround":null,"fixed_in":null,"score":73.3,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#15006","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":15006,"title":"Keyboard layout chosen in installer isn't applied to Hyprland/fcitx5 — desktop falls back to US","url":"https://github.com/omacom/omarchy/issues/15006","state":"open","state_reason":null,"labels":[],"created":"2026-10-11T10:05:35Z","updated":"2026-10-25T21:52:29Z","closed":null,"reactions":1,"thumbs_up":1,"comments":5,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"During installation I selected Swiss German as the keyboard layout. The installer used that layout correctly. After the first boot into the desktop, though, the keyboard was US English everywhere. The layout chosen in the installer should…","versions":["4.0.4-1"],"error_snippets":["even after I set","During installation I selected **Swiss German** as the keyboard layout. The installer used that layout correctly. After the first boot into the desktop, though, the keyboard was **US English** everywhere.","There's also a second problem. fcitx5 runs (`omarchy-fcitx5.service`) but there's no `~/.config/fcitx5/profile`, so it uses its default `keyboard-us` input method. Its virtual keyboard (`hl-virtual-keyboard-fcitx5`) stay"],"workaround":{"text":"`~/.config/hypr/input.lua`: `hl.config({ input = { kb_layout = \"ch\", kb_variant = \"de\" } })` - `~/.config/fcitx5/profile` with `DefaultIM=keyboard-ch-de`, then restart fcitx5.","source":"issue body","url":"https://github.com/omacom/omarchy/issues/15006"},"fixed_in":null,"score":72.7,"first_seen":"2026-10-22T09:27:06Z"},{"id":"omacom/omarchy#15779","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":15779,"title":"Ghostty installed via pacman doesn't launch from the app menu (D-Bus/systemd activation fails), works from a terminal","url":"https://github.com/omacom/omarchy/issues/15779","state":"open","state_reason":null,"labels":["bug"],"created":"2026-10-18T00:14:45Z","updated":"2026-10-23T02:49:26Z","closed":null,"reactions":1,"thumbs_up":1,"comments":2,"severity":"medium","severity_reasons":["class:always-on/daemon","class:install/update"],"topic":"always-on/daemon","classes":["always-on/daemon","install/update"],"cosmetic_ui":false,"summary":"After installing Ghostty (ghostty 1.3.1, Arch extra), clicking Ghostty in the app menu does nothing — no window, no error. Running ghostty (or /usr/bin/ghostty --gtk-single-instance=true) from another terminal opens a window fine. The…","versions":["1.3.1","0.56.2"],"error_snippets":["Exec=/usr/bin/ghostty --gtk-single-instance=true","ExecStart=/usr/bin/ghostty --gtk-single-instance=true --initial-window=false","app-com.mitchellh.ghostty.service: Failed with result 'protocol'.","Failed to start Ghostty.","After installing Ghostty (`ghostty 1.3.1`, Arch extra), clicking Ghostty in the app menu does nothing — no window, no error. Running `ghostty` (or `/usr/bin/ghostty --gtk-single-instance=true`) from another terminal open"],"workaround":null,"fixed_in":null,"score":71.6,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#12218","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":12218,"title":"RTX 5090 grey-screen freeze after 4.0.4 update; 6.9 million NVIDIA register errors displace kernel history","url":"https://github.com/omacom/omarchy/issues/12218","state":"open","state_reason":null,"labels":["bug","compatibility"],"created":"2026-09-17T04:01:48Z","updated":"2026-10-23T03:44:54Z","closed":null,"reactions":1,"thumbs_up":1,"comments":7,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","crash/hang"],"cosmetic_ui":false,"summary":"Omarchy 4.0.4-1 (updated from 4.0.3-1 earlier on the day of the incident) Kernel currently running after recovery: 7.2.5-3-omarchy; linux-omarchy 7.2.5-3 and headers installed during that update Previous stock kernel linux 7.2.3.arch1-3…","versions":["4.0.4","6.9","4.0.4-1","4.0.3-1"],"error_snippets":["T+0.000000 kernel: NVRM: gpuHandleSanityCheckRegReadError_GH100: Possible bad register read: addr: 0xb830b0, regvalue: 0xbadf3200, error code: Unknown SYS_PRI_ERROR_CODE","T+0.008030 kernel: NVRM: gpuHandleSanityCheckRegReadError_GH100: Possible bad register read: addr: 0xb830b0, regvalue: 0xbadf3200, error code: Unknown SYS_PRI_ERROR_CODE","T+49.729614 kernel: NVRM: gpuHandleSanityCheckRegReadError_GH100: Possible bad register read: addr: 0xb830b0, regvalue: 0xbadf3200, error code: Unknown SYS_PRI_ERROR_CODE","~T+16s steam: src/clientdll/steamengine.cpp (2665) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event signalled","This is a report of an observed graphics failure and severe kernel-log flooding after the update, **not a claim that the new kernel is the confirmed cause**. NVIDIA driver/firmware or hardware involvement remains possibl"],"workaround":null,"fixed_in":null,"score":70.5,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#13040","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":13040,"title":"omarchy-mise-install wrappers exec-loop forever when mise shims are on PATH after ~/.local/bin","url":"https://github.com/omacom/omarchy/issues/13040","state":"open","state_reason":null,"labels":["bug"],"created":"2026-09-23T16:41:32Z","updated":"2026-10-13T02:32:56Z","closed":null,"reactions":2,"thumbs_up":1,"comments":10,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","always-on/daemon","network"],"cosmetic_ui":false,"summary":"Intel i9-9880H, Intel UHD 630 + NVIDIA Quadro T2000 Mobile, Omarchy 4.0.4-1, mise-bin 2026.9.12-1 A wrapper generated by omarchy-mise-install can call itself forever. It never exits, and it pins a CPU core by running mise use -g about…","versions":["4.0.4-1","2026.9.12-1"],"error_snippets":["exec mise x \"<package>\" -- \"<bin>\" \"$@\"","timeout 5 codex --version; echo \"rc=$?\" # rc=124 (hangs)","timeout 5 codex --version; echo \"rc=$?\" # rc=0","mise use -g --quiet $package_arg || exit 1","bin_path=\\$(mise which --tool $package_arg $bin_arg) || exit 1"],"workaround":null,"fixed_in":null,"score":69.3,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#11899","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":11899,"title":"`omarchy setup security fingerprint` silently evicts a working libfprint fork, then \"succeeds\" against the stale daemon","url":"https://github.com/omacom/omarchy/issues/11899","state":"open","state_reason":null,"labels":["bug"],"created":"2026-09-15T04:06:31Z","updated":"2026-10-22T19:10:57Z","closed":null,"reactions":2,"thumbs_up":2,"comments":6,"severity":"medium","severity_reasons":["class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon","install/update","auth/session","network"],"cosmetic_ui":false,"summary":"This machine's fingerprint sensor — a Dell XPS 15 7590 with the Goodix 27c6:5395 (\"Goodix HTK32\") — has no driver in the pinned libfprint-git snapshot. The community fork libfprint-goodix53x5 (upstream, built on libfprint tag v1.94.10…","versions":["1.94.10"],"error_snippets":["01:39:34 installed libfprint-goodix53x5 → reader works, enrollment succeeds","(enroll/verify \"passed\" via the stale in-memory fork)","sudo fprintd-enroll","fprintd-enroll -f <finger>","`pacman -Q \"$pkg\"`, which is provides-aware — but **no fork can ever provide the"],"workaround":null,"fixed_in":null,"score":68.0,"first_seen":"2026-10-20T09:28:14Z"},{"id":"omacom/omarchy#12187","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":12187,"title":"Update to 4.0.4: NVIDIA hybrid laptop hard-freezes ~5 s after login once linux-omarchy is the default kernel (prebuilt nvidia-open has no modules for it)","url":"https://github.com/omacom/omarchy/issues/12187","state":"open","state_reason":null,"labels":["bug","compatibility"],"created":"2026-09-16T21:13:48Z","updated":"2026-10-12T18:09:10Z","closed":null,"reactions":1,"thumbs_up":1,"comments":4,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update","crash/hang","auth/session","always-on/daemon"],"cosmetic_ui":false,"summary":"Omarchy 4.0.3-1 → 4.0.4-1 (update ran 2026-09-16; 4.0.4 released 2026-09-15) - Lenovo laptop, hybrid graphics: Intel iGPU + NVIDIA RTX 4070 Max-Q (AD106M, 10DE:2860), supergfxctl/supergfxd + nvidia-powerd active, Hyprland/Wayland - Driver…","versions":["4.0.4","4.0.3-1","4.0.4-1","610.57.04-14"],"error_snippets":["modules exist only under /usr/lib/modules/7.2.3-arch1-3/extramodules/ (built for the stock kernel); there are no NVIDIA modules for","Boot correlation (all frozen boots were on 7.2.5-3-omarchy, all working boots on 7.2.3-arch1-3; journals end abruptly with zero kernel errors):","Identical lines at login in every frozen boot:","systemd-modules-load: Failed to find module 'nvidia_uvm'","supergfxd: ERROR supergfxctl::controller Action thread errored: The module nvidia_drm is missing"],"workaround":null,"fixed_in":null,"score":64.5,"first_seen":"2026-10-24T08:54:58Z"},{"id":"omacom/omarchy#15924","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":15924,"title":"Blur behind GTK4 windows is gone after the gtk4 4.24 update (only Glassy keeps it)","url":"https://github.com/omacom/omarchy/issues/15924","state":"open","state_reason":null,"labels":[],"created":"2026-10-19T04:57:52Z","updated":"2026-10-23T05:28:57Z","closed":null,"reactions":1,"thumbs_up":1,"comments":1,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","always-on/daemon"],"cosmetic_ui":false,"summary":"Intel Core i5-1335U / Iris Xe (HP Pavilion 15-eg3xxx), Omarchy 4.0.5, Hyprland 0.56.2, Wayland, gtk4 1:4.24.1 After the 2026-10-18 update, Hyprland stopped blurring the background behind Ghostty. The window is still translucent and the…","versions":["4.24","4.0.5","0.56.2","4.24.1"],"error_snippets":["return !surface->m_blurRegion.empty(); // empty region => no blur","zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs rtc_cmos.use_acpi_alarm=1","Topology cpus 1x dies 1 clusters 4 cores 10 threads 12 mt 2 tpc 2 st 8 smt enabled cache","Speed (MHz) avg 794 min/max 400/4600:3400 scaling driver intel_pstate governor powersave cores","Type spectre_v2 mitigation Enhanced / Automatic IBRS; IBPB: conditional; PBRSB-eIBRS: SW"],"workaround":null,"fixed_in":null,"score":61.8,"first_seen":"2026-10-25T09:11:37Z"},{"id":"omacom/omarchy#14237","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":14237,"title":"Left DisplayPort monitor intermittently blacks out after wake on RTX 5080; 60 → 120 Hz reset workaround","url":"https://github.com/omacom/omarchy/issues/14237","state":"open","state_reason":null,"labels":["bug"],"created":"2026-10-04T13:01:58Z","updated":"2026-10-18T09:53:10Z","closed":null,"reactions":2,"thumbs_up":2,"comments":6,"severity":"medium","severity_reasons":["class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon"],"cosmetic_ui":false,"summary":"Omarchy 4.0.4-1; Hyprland 0.56.2-2 (Wayland) Kernel: 7.2.5-3-omarchy CPU: AMD Ryzen 9 7950X3D; motherboard: ASUS TUF GAMING X670E-PLUS WIFI GPU driving both monitors: NVIDIA GeForce RTX 5080 (MSI), nvidia-open-dkms / nvidia-utils…","versions":["4.0.4-1","0.56.2-2","610.57.04-1","59.951"],"error_snippets":["hyprctl eval 'hl.monitor({ output = \"DP-2\", mode = \"2560x1440@60\", position = \"0x0\", scale = 1, transform = 1 })'","hyprctl eval 'hl.monitor({ output = \"DP-2\", mode = \"2560x1440@120\", position = \"0x0\", scale = 1, transform = 1 })'","systemctl is-enabled","The left monitor intermittently goes black and comes back after sleep/wake, while the right monitor continues working normally. The desktop remains usable on the right display. Expected: both displays should recover and ","The sleep/wake association is based on my observations; the exact trigger has not yet been isolated between system suspend/resume and display idle/DPMS wake. The available current-boot journal does not record an actual s"],"workaround":null,"fixed_in":null,"score":61.3,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#12944","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":12944,"title":"Cloned menu plugin loses its scoped shell API during shell startup - installed apps vanish from menu and search","url":"https://github.com/omacom/omarchy/issues/12944","state":"open","state_reason":null,"labels":["bug"],"created":"2026-09-22T20:06:24Z","updated":"2026-10-13T02:31:09Z","closed":null,"reactions":1,"thumbs_up":1,"comments":6,"severity":"medium","severity_reasons":["class:install/update","class:mcp/tools"],"topic":"install/update","classes":["install/update","mcp/tools"],"cosmetic_ui":false,"summary":"AMD Ryzen AI 5 340 w/ Radeon 840M (Framework), Omarchy 4.0.4-1, Quickshell 0.3.1-1, Hyprland 0.56.2, kernel 7.2.5-3-omarchy, Wayland. After cloning the menu plugin with the documented flow (omarchy plugin clone omarchy.menu), installed…","versions":["4.0.4-1","0.3.1-1","0.56.2","4.0.4"],"error_snippets":["Component.onCompleted: shell = null (expected)","Timer 500ms tick 1: shell = null (already revoked, stays null)","mergeAppRows: appLibrary = null (apps silently skipped)","4. No app rows appear; `omarchy menu summon apps` shows an empty submenu","Evidence from temporary instrumentation in the cloned `Menu.qml`:"],"workaround":null,"fixed_in":null,"score":58.9,"first_seen":"2026-10-25T09:11:37Z"},{"id":"omacom/omarchy#15831","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":15831,"title":"linux-omarchy 7.2.8-9: webcam broken on XPS 13 9340 (IPU6), HIMX1092 ipu-bridge entry blocks ISYS notifier without an hm1092 driver","url":"https://github.com/omacom/omarchy/issues/15831","state":"open","state_reason":null,"labels":["bug","compatibility"],"created":"2026-10-18T11:36:53Z","updated":"2026-10-23T03:35:12Z","closed":null,"reactions":1,"thumbs_up":1,"comments":2,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"Omarchy 4.0.5-1, linux-omarchy 7.2.8-9 (regression from 7.2.5-3) Dell XPS 13 9340, BIOS 1.29.0, Meteor Lake, IPU6-v4, Intel IVSC Webcam: OV02C10 (OVTI02C1, \\SB.PC00.LNK1) via IVSC → IPU6 CSI2 4 IR camera: Himax HM1092 (HIMX1092…","versions":["7.2.8-9","4.0.5-1","7.2.5-3","6.18"],"error_snippets":["node. Only 7 exist (6× CSI2 + IVSC CSI). PipeWire instead exposes ~48 raw ipu6 nodes, which fail with","entry (backport of mainline","ERROR V4L2 v4l2_device.cpp:92 'ov02c10 17-0036': Failed to open V4L2 device '': No such file or directory","ERROR CameraSensor camera_sensor.cpp:470 Failed to create sensor for 'ov02c10 17-0036: -2","ERROR SimplePipeline simple.cpp:1930 No valid pipeline for sensor 'ov02c10 17-0036', skipping"],"workaround":null,"fixed_in":null,"score":57.9,"first_seen":"2026-10-23T09:23:24Z"},{"id":"omacom/omarchy#2831","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":2831,"title":"mise python installation breaks AUR packages installations","url":"https://github.com/omacom/omarchy/issues/2831","state":"closed","state_reason":"completed","labels":["bug"],"created":"2025-10-25T01:52:15Z","updated":"2026-09-21T09:50:52Z","closed":"2026-09-21T09:50:52Z","reactions":10,"thumbs_up":10,"comments":9,"severity":"medium","severity_reasons":["engagement 19","class:install/update"],"topic":"install/update","classes":["install/update","network"],"cosmetic_ui":false,"summary":"11th Gen Intel(R) Core(TM) i5-1145G7 (8) @ 4.40 GHz, Intel Iris Xe Graphics @ 1.30 GHz [Integrated] Whenever a mise python version is installed, packages that depend on system python, like anki, will break builds and won't install: build…","versions":["4.40","1.30"],"error_snippets":["I would like to suggest pointing the python installation in the Menu > Install > Development to installing the `uv` python package manager directly instead of using `mise` to handle python. The current recommended workfl"],"workaround":null,"fixed_in":null,"score":57.4,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#15813","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":15813,"title":"Omarchy 4.0.5 / systemd 262: three TPM NvPCR services failed after update","url":"https://github.com/omacom/omarchy/issues/15813","state":"closed","state_reason":"completed","labels":["bug"],"created":"2026-10-18T08:39:41Z","updated":"2026-10-22T09:10:57Z","closed":"2026-10-22T09:10:57Z","reactions":3,"thumbs_up":3,"comments":4,"severity":"medium","severity_reasons":["class:always-on/daemon","class:install/update"],"topic":"always-on/daemon","classes":["always-on/daemon","install/update"],"cosmetic_ui":false,"summary":"Architecture: x8664 - CPU: Intel Pentium N3710 @ 1.60GHz - GPU: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 35) - Bootloader: Limine / UKI - Root filesystem: encrypted, Btrfs After updating…","versions":["4.0.5"],"error_snippets":["systemd-tpm2-setup-early.service","Failed to initialize NvPCR index: No such file or directory","Could not extend NvPCR: No such file or directory","Failed to start Early TPM SRK Setup.","Failed to start TPM NvPCR Product ID Measurement."],"workaround":null,"fixed_in":null,"score":56.3,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#5097","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":5097,"title":"Microsoft Edge crashes under Wayland with tile rule on hover","url":"https://github.com/omacom/omarchy/issues/5097","state":"open","state_reason":null,"labels":["bug"],"created":"2026-03-22T18:53:07Z","updated":"2026-10-08T00:25:46Z","closed":null,"reactions":4,"thumbs_up":0,"comments":6,"severity":"high","severity_reasons":["title:breakage"],"topic":"crash/hang","classes":["crash/hang"],"cosmetic_ui":false,"summary":"Microsoft Edge segfaults when hovering over images on certain sites (e.g. omarchythemes.com theme detail pages). The crash is caused by the interaction between Edge's native Wayland popup/overlay handling and the tile on window rule in…","versions":["0.54.2","1.5"],"error_snippets":["--enable-features=TouchpadOverscrollHistoryNavigation","--load-extension=~/.local/share/omarchy/default/chromium/extensions/copy-url","microsoft-edge-stable-flags.conf","microsoft-edge-flags.conf","--disable-extensions"],"workaround":{"text":"Create `~/.config/microsoft-edge-stable-flags.conf`:","source":"issue body","url":"https://github.com/omacom/omarchy/issues/5097"},"fixed_in":null,"score":55.7,"first_seen":"2026-10-22T09:27:06Z"},{"id":"omacom/omarchy#8701","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":8701,"title":"QT_QPA_PLATFORM=wayland;xcb causes SteamVR vrmonitor to abort on startup","url":"https://github.com/omacom/omarchy/issues/8701","state":"open","state_reason":null,"labels":["bug"],"created":"2026-08-28T01:14:16Z","updated":"2026-10-09T05:30:57Z","closed":null,"reactions":4,"thumbs_up":3,"comments":7,"severity":"low","severity_reasons":["low engagement"],"topic":"install/update","classes":["install/update","crash/hang","mcp/tools"],"cosmetic_ui":false,"summary":"On Omarchy 4.0.0-1, SteamVR's vrmonitor aborts during Qt GUI initialization because the session-wide environment sets: SteamVR's bundled Qt 5 installation provides only the xcb platform plugin. It treats wayland;xcb as one literal plugin…","versions":["4.0.0-1"],"error_snippets":["This application failed to start because it could not find or load the Qt platform plugin \"wayland;xcb\".","then exits with SIGABRT. The coredump stack reaches","QMessageLogger::fatal()","/usr/share/omarchy/default/hypr/envs.lua","with no new Qt platform-plugin error or new"],"workaround":null,"fixed_in":null,"score":55.6,"first_seen":"2026-10-22T09:27:06Z"},{"id":"omacom/omarchy#14136","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":14136,"title":"Quickshell exits with status 137 on wake from suspend, briefly flashing Hyprland lockdead screen","url":"https://github.com/omacom/omarchy/issues/14136","state":"open","state_reason":null,"labels":[],"created":"2026-10-03T12:07:56Z","updated":"2026-10-18T06:37:09Z","closed":null,"reactions":2,"thumbs_up":2,"comments":4,"severity":"medium","severity_reasons":["class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon"],"cosmetic_ui":false,"summary":"Apple MacBookAir5,2, Intel Core i5-3427U, Intel HD Graphics 4000, Omarchy 4.0.4-1, Hyprland 0.56.2, Linux 7.2.5-3-omarchy Upon opening the laptop lid and resuming from suspend (S3), the Omarchy lock screen briefly displayed Hyprland's…","versions":["4.0.4-1","0.56.2"],"error_snippets":["Oct 03 13:53:18 omarchy-shell[11045]: Omarchy shell exited with status 137; relaunching.","Upon opening the laptop lid and resuming from suspend (S3), the Omarchy lock screen briefly displayed Hyprland's emergency `lockdead.png` failsafe screen (*\"Oopsie daisy, it looks like you locked your screen but the lock","Reviewing journalctl logs revealed that the running Quickshell lock client (PID 1663) abruptly terminated with status **137** (`SIGKILL`) while processing rapid post-wake D-Bus property changes from NetworkManager access","Because the active `ext-session-lock-v1` client died while the compositor was locked, Hyprland engaged its failsafe lock screen (`/usr/share/hypr/lockdead.png`)."],"workaround":null,"fixed_in":null,"score":54.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#14635","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":14635,"title":"Menu is black after Qt 6.12.0 / quickshell 0.3.2 upgrade (Color singleton sub-objects undefined)","url":"https://github.com/omacom/omarchy/issues/14635","state":"closed","state_reason":"completed","labels":[],"created":"2026-10-08T22:48:07Z","updated":"2026-10-18T07:42:54Z","closed":"2026-10-18T07:42:54Z","reactions":4,"thumbs_up":4,"comments":9,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","always-on/daemon","mcp/tools"],"cosmetic_ui":false,"summary":"After upgrading to Qt 6.12.0, Super + Space opens the Omarchy menu as a fully black screen. The shell's Color singleton sub-objects (Color.menu, Color.tooltip, Color.bar, ...) evaluate to undefined, so every themed surface (menu, tooltips…","versions":["6.12.0","0.3.2","4.0.4-1","0.56.2"],"error_snippets":["@plugins/bar/Bar.qml[75:3]: Unable to assign [undefined] to QColor","@Ui/PanelToolTip.qml[22:-1]: TypeError: Cannot read property 'background' of undefined","plugins/menu/Menu.qml[87:-1]: TypeError: Cannot read property 'background' of undefined","plugins/menu/Menu.qml[91:-1]: TypeError: Cannot read property 'scrim' of undefined","@Commons/Border.qml[25:-1]: TypeError: Cannot read property 'menu.border-alpha' of undefined"],"workaround":null,"fixed_in":null,"score":54.8,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#14438","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":14438,"title":"Idle screensaver/lock never fire when shell.json idle timeout differs from defaults (Quickshell IdleMonitor timeout bug)","url":"https://github.com/omacom/omarchy/issues/14438","state":"open","state_reason":null,"labels":[],"created":"2026-10-07T12:38:25Z","updated":"2026-10-18T12:02:40Z","closed":null,"reactions":1,"thumbs_up":1,"comments":3,"severity":"medium","severity_reasons":["class:network"],"topic":"network","classes":["network","always-on/daemon","crash/hang"],"cosmetic_ui":false,"summary":"Intel i7-12800H, Intel Iris Xe + NVIDIA RTX A1000 Laptop GPU, Omarchy 4.0.4-1, Quickshell 0.3.1-1, Hyprland 0.56.2 If idle.screensaver or idle.lock in ~/.config/omarchy/shell.json differs from the built-in defaults so that the first idle…","versions":["4.0.4-1","0.3.1-1","0.56.2","0.3.1"],"error_snippets":["IdleMonitor { timeout: to; onIsIdleChanged: console.log(\"CHANGED idle=\" + isIdle) }","IdleMonitor { timeout: 10; onIsIdleChanged: console.log(\"CONTROL idle=\" + isIdle) }","timeout: root.firstIdleTimeoutSeconds","quickshell -p /usr/share/omarchy/shell ipc call idle disable && quickshell -p /usr/share/omarchy/shell ipc call idle enable","enabled: false"],"workaround":{"text":"`quickshell -p /usr/share/omarchy/shell ipc call idle disable && quickshell -p /usr/share/omarchy/shell ipc call idle enable` after the shell has loaded its config (and after each `shell.json` idle change).","source":"issue body","url":"https://github.com/omacom/omarchy/issues/14438"},"fixed_in":null,"score":54.4,"first_seen":"2026-10-25T09:11:37Z"},{"id":"omacom/omarchy#4120","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":4120,"title":"Thinkpad stalling after entering Omarchy credentials and rebooting","url":"https://github.com/omacom/omarchy/issues/4120","state":"closed","state_reason":"completed","labels":["bug"],"created":"2026-01-07T23:33:47Z","updated":"2026-09-12T17:25:06Z","closed":"2026-01-09T16:18:47Z","reactions":5,"thumbs_up":5,"comments":12,"severity":"critical","severity_reasons":["title:data-loss/security"],"topic":"auth/session","classes":["auth/session","install/update","network"],"cosmetic_ui":false,"summary":"Thinkpad T480, Omarchy 3.3.0 I upgraded to 3.3.0 today, and after I enter the login credentials, it waits for 2 minutes showing the login window, then reboots. I pressed Ctrl-Alt-7 to see the terminal while it was waiting, here is the…","versions":["3.3.0"],"error_snippets":["I upgraded to 3.3.0 today, and after I enter the login credentials, it waits for 2 minutes showing the login window, then reboots."],"workaround":null,"fixed_in":null,"score":53.4,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#14564","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":14564,"title":"Edge repo serves stale package database: hype missing, so omarchy update tries to replace it with an unrelated AUR package","url":"https://github.com/omacom/omarchy/issues/14564","state":"closed","state_reason":"completed","labels":["bug"],"created":"2026-10-08T09:32:27Z","updated":"2026-10-16T12:54:49Z","closed":"2026-10-12T06:18:03Z","reactions":4,"thumbs_up":4,"comments":9,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","network"],"cosmetic_ui":false,"summary":"AMD Ryzen 7 6800U, Radeon 680M (integrated), Omarchy 4.0.0.r6807.g902fd8a-1 (edge channel; now rolled back to r6720.g8e02fc8-1) Since around 2026-10-08 09:04 UTC, the edge repo database at https://pkgs.omarchy.org/edge/x8664/omarchy.db…","versions":["0.4.2-1","0.4.3-1","6.12","2.0.4"],"error_snippets":["skill) while helping a user troubleshoot a failed","https://pkgs.omarchy.org/edge/x86_64/omarchy.db",", so they can't get fixes such as #14553 (Qt 6.12","[omarchy] Server = https://pkgs.omarchy.org/edge/$arch","installed from the edge repo and"],"workaround":null,"fixed_in":null,"score":51.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#14836","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":14836,"title":"Startup cursor restore never runs after a reload wipes its Lua state; pointer stays invisible","url":"https://github.com/omacom/omarchy/issues/14836","state":"open","state_reason":null,"labels":["bug"],"created":"2026-10-10T09:39:06Z","updated":"2026-10-22T08:29:01Z","closed":null,"reactions":2,"thumbs_up":2,"comments":2,"severity":"low","severity_reasons":["low engagement"],"topic":"other","classes":[],"cosmetic_ui":false,"summary":"Omarchy dev channel (dev-linked checkout, integration build db439093), Hyprland 0.56.2, AMD Ryzen AI 9 HX 370 w/ Radeon 890M (GPD G1628-04). Two displays configured: internal eDP-1 panel plus a Vestel TV on DP-1. Session uses a plain…","versions":["0.56.2"],"error_snippets":["hyprctl eval","ever runs — including the final one #14610 adds. The 15 s timer recovery is gone too:","registrations do not survive a reload either. At the time of probing, DP-1 was no longer in","Probed the compositor's Lua state directly (via `hyprctl eval` writing through `io.open`, same method as the reload probe upthread in #14512):"],"workaround":null,"fixed_in":null,"score":50.0,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#7263","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":7263,"title":"Dual-boot install fails when the free space is on a different disk than Windows itself","url":"https://github.com/omacom/omarchy/issues/7263","state":"closed","state_reason":"completed","labels":["bug"],"created":"2026-08-17T11:54:40Z","updated":"2026-10-23T08:56:24Z","closed":"2026-10-23T08:56:24Z","reactions":7,"thumbs_up":7,"comments":6,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"AMD 5900x, RX9070XT, Omarchy 4.0.0 Omarchy: 4.0.0 ISO: omarchy-4.0.0.iso, SHA256 verified against the published checksum Boot media: SanDisk 64 GB USB written with balenaEtcher, Secure Boot disabled Machine: two NVMe drives — Samsung SSD…","versions":["4.0.0","465.8"],"error_snippets":["mount: /mnt/boot: fsconfig() failed: Can't find a SQUASHFS superblock on nvme0n1p3.","dmesg(1) may have more information after failed mount system call.","mounting the ESP failed (exit 32)"],"workaround":null,"fixed_in":null,"score":49.2,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#5986","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":5986,"title":"SDDM greeter defaults to us keymap instead of the one selected on install","url":"https://github.com/omacom/omarchy/issues/5986","state":"closed","state_reason":"completed","labels":["bug"],"created":"2026-05-27T19:52:51Z","updated":"2026-10-04T14:51:12Z","closed":"2026-07-18T19:43:12Z","reactions":6,"thumbs_up":6,"comments":6,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update","crash/hang","auth/session"],"cosmetic_ui":false,"summary":"Omarchy 3.8.2 (updated 2026-05-27) Hyprland 0.55.2 (was 0.54.3) hyprlock 0.9.5-4 (was 0.9.5-2) SDDM 0.21.0-7 (was 0.21.0-6) SDDM greeter rejects correct password after 3.8.x update — greeter falls back to us keymap because installer only…","versions":["3.8.2","0.55.2","0.54.3","0.9.5-4"],"error_snippets":["May 27 18:02:50 thinkpad sddm-helper[10526]: [PAM] authenticate: Authentication failure","May 27 18:02:50 thinkpad sddm[1223]: Authentication error: SDDM::Auth::ERROR_AUTHENTICATION \"Authentication failure\"","May 27 18:03:00 thinkpad sddm-helper[10545]: [PAM] authenticate: Authentication failure","May 27 18:03:08 thinkpad sddm-helper[10549]: [PAM] authenticate: Authentication failure","May 27 18:03:22 thinkpad sddm-helper[10620]: [PAM] authenticate: Authentication failure"],"workaround":{"text":"Added the following to `/usr/share/sddm/hyprland.conf`:","source":"issue body","url":"https://github.com/omacom/omarchy/issues/5986"},"fixed_in":null,"score":48.3,"first_seen":"2026-10-21T09:24:21Z"},{"id":"omacom/omarchy#14989","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":14989,"title":"[Shell] Qt 6.12 upgrade breaks Commons Color singleton (shadowed by QtQuick Color), causing black screen on menu and broken volume OSD","url":"https://github.com/omacom/omarchy/issues/14989","state":"closed","state_reason":"completed","labels":[],"created":"2026-10-11T07:37:35Z","updated":"2026-10-18T07:43:19Z","closed":"2026-10-18T07:43:19Z","reactions":4,"thumbs_up":4,"comments":6,"severity":"high","severity_reasons":["title:breakage"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"After upgrading to qt6-declarative 6.12.0-1 (and quickshell 0.3.2-1), opening the Omarchy menu (omarchy-menu toggle via SUPER + SPACE or SUPER + ESCAPE) causes a pitch-black screen with locked focus, and volume/brightness key adjustments…","versions":["6.12","6.12.0-1","0.3.2-1","4.0.4-1"],"error_snippets":["SUPER + ESCAPE","evaluates to","WlrKeyboardFocus.Exclusive","to crash with TypeErrors (","After upgrading to `qt6-declarative 6.12.0-1` (and `quickshell 0.3.2-1`), opening the Omarchy menu (`omarchy-menu toggle` via `SUPER + SPACE` or `SUPER + ESCAPE`) causes a pitch-black screen with locked focus, and volume"],"workaround":{"text":"Downgrade `qt6-` to `6.11.2` and `quickshell` to `0.3.1-1`.","source":"issue body","url":"https://github.com/omacom/omarchy/issues/14989"},"fixed_in":null,"score":46.1,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#8628","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":8628,"title":"Lock screen: password field loses focus after display wake, recoverable only with a mouse","url":"https://github.com/omacom/omarchy/issues/8628","state":"closed","state_reason":"completed","labels":[],"created":"2026-08-27T16:52:03Z","updated":"2026-09-20T20:07:50Z","closed":"2026-09-20T20:07:50Z","reactions":5,"thumbs_up":5,"comments":5,"severity":"medium","severity_reasons":["class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon","crash/hang","mcp/tools","network"],"cosmetic_ui":false,"summary":"After the lock screen blanks the display, waking it does not restore focus to the password field. Keystrokes go nowhere. The only way to recover is to click with a mouse or tap the touchpad, which defeats keyboard-only operation. Omarchy…","versions":["4.0.1-1","0.56.2","0.3.1-1"],"error_snippets":["In `shell/plugins/lock/LockView.qml`, focus is asserted in exactly two places:","`root.wakeRequested()`, but an unfocused `TextInput` never receives key events,","shell loads it without QML errors and password PAM auth is unaffected.","An event-driven alternative would be to call `lockView.forcePasswordFocus()`"],"workaround":null,"fixed_in":null,"score":44.1,"first_seen":"2026-10-24T08:54:58Z"},{"id":"omacom/omarchy#11458","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":11458,"title":"Hard freeze shortly after resuming from s2idle on Intel Ice Lake (i915) with kernel 7.2.3-arch1-3 (ASUS ZenBook UX325JA)","url":"https://github.com/omacom/omarchy/issues/11458","state":"open","state_reason":null,"labels":["bug","compatibility"],"created":"2026-09-12T12:48:46Z","updated":"2026-10-14T00:43:56Z","closed":null,"reactions":1,"thumbs_up":1,"comments":3,"severity":"high","severity_reasons":["title:breakage"],"topic":"crash/hang","classes":["crash/hang","always-on/daemon","install/update","mcp/tools","network"],"cosmetic_ui":false,"summary":"On Omarchy 4.0.3-1 with kernel 7.2.3-arch1-3, this laptop intermittently hard-freezes ~20-50 s after a successful s2idle resume. Suspend and resume both complete and log normally (PM: suspend entry and PM: suspend exit); the machine then…","versions":["4.0.3-1","7.2.3-arch1","7.2.3","7.1.9-arch1"],"error_snippets":["Sep 12 07:30:43 omarchy kernel: PM: suspend entry (s2idle)","Sep 12 07:30:48 omarchy kernel: PM: suspend exit","Sep 10 07:06:19 omarchy kernel: PM: suspend entry (s2idle)","Sep 10 07:06:23 omarchy kernel: PM: suspend exit","PM: suspend entry"],"workaround":{"text":"Pin/downgrade to kernel 7.1.9-arch1-2 (or use `linux-lts`) until a fixed kernel is available. - Try `i915.enable_psr=0` / `i915.enable_dc=0`, since the failure is in the post-resume display re-initialisation path. - Try `mem_sleep_default=deep` to move off s2idle.","source":"issue body","url":"https://github.com/omacom/omarchy/issues/11458"},"fixed_in":null,"score":42.4,"first_seen":"2026-10-25T09:11:37Z"},{"id":"omacom/omarchy#13394","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":13394,"title":"Lenovo ThinkPad does not shut down properly and slow startup","url":"https://github.com/omacom/omarchy/issues/13394","state":"open","state_reason":null,"labels":["bug","compatibility"],"created":"2026-09-27T10:07:20Z","updated":"2026-10-13T16:35:35Z","closed":null,"reactions":1,"thumbs_up":0,"comments":10,"severity":"low","severity_reasons":["low engagement"],"topic":"other","classes":[],"cosmetic_ui":false,"summary":"Laptop: Lenovo ThinkPad T460, CPU: Intel(R) Core(TM) i7-6600U (4)z, Graphics: Intel HD Graphics 520 / Skylake-U GT2, GPU driver: i915, Omarchy: 4.0.4-1 When I shut down the laptop: The screen turns off. The power button light turns off…","versions":["4.0.4-1"],"error_snippets":["Laptop: Lenovo ThinkPad T460, CPU: Intel(R) Core(TM) i7-6600U (4)z, Graphics: Intel HD Graphics 520 / Skylake-U GT2, GPU driver: i915, Omarchy: 4.0.4-1"],"workaround":null,"fixed_in":null,"score":42.2,"first_seen":"2026-10-19T18:38:33Z"},{"id":"omacom/omarchy#11744","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":11744,"title":"Idle wake is dead after a lock, and a clamshell-disabled internal panel survives resume unreconciled","url":"https://github.com/omacom/omarchy/issues/11744","state":"open","state_reason":null,"labels":["bug"],"created":"2026-09-13T22:32:05Z","updated":"2026-10-11T23:57:43Z","closed":null,"reactions":1,"thumbs_up":0,"comments":4,"severity":"medium","severity_reasons":["class:always-on/daemon"],"topic":"always-on/daemon","classes":["always-on/daemon","mcp/tools"],"cosmetic_ui":false,"summary":"Updated after the discussion below. The blank-to-link-drop mechanism v1b3m describes is confirmed on this machine too and belongs with #9078 and #10691, so I have split it out of this report. What remains here are the two findings that the…","versions":[],"error_snippets":["19:23:50 eDP-1 disabled=true (clamshell: lid closed + external monitor active)","19:24:17 eDP-1 re-enabled (watcher poll, 3 s later)","hl.dsp.dpms({ action = \"enable\" })","amdgpu ... DMCUB error","`lockSystem` in `plugins/services/idle/Service.qml` clears `idledThisCycle` at line 77 immediately before triggering the lock at line 80. `handleActiveSignal` then returns early on `!root.idledThisCycle` at line 159. So "],"workaround":null,"fixed_in":null,"score":41.0,"first_seen":"2026-10-26T10:12:02Z"},{"id":"omacom/omarchy#7596","harness":"omarchy","harness_name":"Omarchy","repo":"omacom/omarchy","number":7596,"title":"Quickshell unable to restart after latest update on Edge branch","url":"https://github.com/omacom/omarchy/issues/7596","state":"closed","state_reason":"completed","labels":["bug"],"created":"2026-08-20T09:26:35Z","updated":"2026-09-14T17:34:21Z","closed":"2026-08-21T11:19:13Z","reactions":5,"thumbs_up":5,"comments":7,"severity":"medium","severity_reasons":["class:install/update"],"topic":"install/update","classes":["install/update"],"cosmetic_ui":false,"summary":"i5-10400F, RTX 2080 Ti, Omarchy 4.0.0.r1787.g9455496-1 quickshell: symbol lookup error: quickshell: undefined symbol: ZN23QUntypedPropertyBindingC1EP23QPropertyBindingPrivate, version Qt6PRIVATEAPI 1) Tried reboot 2) Re-tried Omarchy…","versions":[],"error_snippets":["quickshell: symbol lookup error: quickshell: undefined symbol: _ZN23QUntypedPropertyBindingC1EP23QPropertyBindingPrivate, version Qt_6_PRIVATE_API"],"workaround":null,"fixed_in":null,"score":40.9,"first_seen":"2026-10-26T10:12:02Z"}]}