Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-813GitHub issuePublicDecided· Out of scope

SDDM boot greeter clips on mixed displays and ignores Colemak/Russian layouts

Reported by backmeupplz · filed Sep 8, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

SDDM boot greeter clips on mixed displays and ignores Colemak/Russian layoutsrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

  • Omarchy 4.0.2-1
  • Hyprland 0.56.2-1
  • SDDM 0.21.0-7, using Omarchy's Wayland greeter
  • Laptop: Lenovo ThinkPad X1 Carbon Gen 10
  • Internal display (eDP-1): 1920×1200 at 60 Hz, scale 1.25
  • External display (DP-7): Lenovo Legion R34w-30, 3440×1440 at 60 Hz, scale 1.25
  • Session monitor rule: preferred mode, automatic positioning, scale 1.25
  • Session keyboard configuration:
  kb_layout = us,ru
  kb_variant = colemak,
  kb_options = compose:caps,grp:ctrl_space_toggle

Ctrl+Space switches between US Colemak and Russian. A custom topbar indicator displays the active layout and can also be clicked to cycle layouts.

What's wrong?

There are three related usability problems in the SDDM boot/login greeter:

  1. The greeter renders incorrectly with both displays connected. On the 3440×1440 external display it is centered, but on the 1920×1200 internal display the Omarchy logo and password field are shifted/clipped beyond the left edge. Both outputs use 1.25 scaling in the normal Hyprland session.
  1. The greeter does not use the configured keyboard layouts. The normal session starts with US Colemak, also supports Russian, shows the active layout in the topbar, and switches with Ctrl+Space or a click on that indicator. At the boot greeter, the password field instead behaves as US QWERTY, with no visible layout indicator and no way to switch layouts. This can make a correctly remembered password appear wrong.
  1. The password field has no reveal control. An eye button that reveals the password only while pressed would make layout-related input problems easier to diagnose while limiting accidental exposure. It should hide the password again on release or focus loss.

Steps to reproduce

  1. Boot with both the internal 1920×1200 display and external 3440×1440 display connected.
  2. Reach the SDDM login greeter.
  3. Observe the centered external output and clipped/offset internal output.
  4. Enter a password using Colemak key positions, or press Ctrl+Space to switch to Russian.

Expected behavior

  • The greeter is independently centered and correctly scaled on every connected output.
  • The configured Colemak/Russian layouts are available before login, with a visible current-layout indicator and a keyboard/click method to switch them.
  • The password field offers a momentary press-and-hold reveal button.

Relevant implementation details

The installed files match the current quattro branch:

  • default/sddm/hyprland.lua contains only miscellaneous/animation settings and no monitor or input configuration.
  • default/sddm/omarchy/Main.qml uses a fixed 640×480 root and a permanently masked TextInput; it has no output-aware layout, keyboard-layout indicator, or reveal control.

This overlaps with #10269 for the SDDM keyboard-layout problem. #2884 addressed a similar password-reveal request for the session lock screen, but the boot/login SDDM greeter still lacks that control.

Potential direction: generate/reuse a safe subset of the user's monitor and XKB settings for SDDM, make the QML responsive to each screen's dimensions/scale, and add a momentary password-reveal control.

I have intentionally omitted hostnames, usernames, network details, serial numbers, and photographs of the physical setup.

View raw text
### System details

- Omarchy `4.0.2-1`
- Hyprland `0.56.2-1`
- SDDM `0.21.0-7`, using Omarchy's Wayland greeter
- Laptop: Lenovo ThinkPad X1 Carbon Gen 10
- Internal display (`eDP-1`): 1920×1200 at 60 Hz, scale 1.25
- External display (`DP-7`): Lenovo Legion R34w-30, 3440×1440 at 60 Hz, scale 1.25
- Session monitor rule: preferred mode, automatic positioning, scale 1.25
- Session keyboard configuration:

  ```ini
  kb_layout = us,ru
  kb_variant = colemak,
  kb_options = compose:caps,grp:ctrl_space_toggle
  ```

  `Ctrl+Space` switches between US Colemak and Russian. A custom topbar indicator displays the active layout and can also be clicked to cycle layouts.

### What's wrong?

There are three related usability problems in the SDDM boot/login greeter:

1. **The greeter renders incorrectly with both displays connected.** On the 3440×1440 external display it is centered, but on the 1920×1200 internal display the Omarchy logo and password field are shifted/clipped beyond the left edge. Both outputs use 1.25 scaling in the normal Hyprland session.

2. **The greeter does not use the configured keyboard layouts.** The normal session starts with US Colemak, also supports Russian, shows the active layout in the topbar, and switches with `Ctrl+Space` or a click on that indicator. At the boot greeter, the password field instead behaves as US QWERTY, with no visible layout indicator and no way to switch layouts. This can make a correctly remembered password appear wrong.

3. **The password field has no reveal control.** An eye button that reveals the password only while pressed would make layout-related input problems easier to diagnose while limiting accidental exposure. It should hide the password again on release or focus loss.

#### Steps to reproduce

1. Boot with both the internal 1920×1200 display and external 3440×1440 display connected.
2. Reach the SDDM login greeter.
3. Observe the centered external output and clipped/offset internal output.
4. Enter a password using Colemak key positions, or press `Ctrl+Space` to switch to Russian.

#### Expected behavior

- The greeter is independently centered and correctly scaled on every connected output.
- The configured Colemak/Russian layouts are available before login, with a visible current-layout indicator and a keyboard/click method to switch them.
- The password field offers a momentary press-and-hold reveal button.

#### Relevant implementation details

The installed files match the current `quattro` branch:

- `default/sddm/hyprland.lua` contains only miscellaneous/animation settings and no monitor or input configuration.
- `default/sddm/omarchy/Main.qml` uses a fixed 640×480 root and a permanently masked `TextInput`; it has no output-aware layout, keyboard-layout indicator, or reveal control.

This overlaps with #10269 for the SDDM keyboard-layout problem. #2884 addressed a similar password-reveal request for the session lock screen, but the boot/login SDDM greeter still lacks that control.

Potential direction: generate/reuse a safe subset of the user's monitor and XKB settings for SDDM, make the QML responsive to each screen's dimensions/scale, and add a momentary password-reveal control.

I have intentionally omitted hostnames, usernames, network details, serial numbers, and photographs of the physical setup.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 11:12 UTC