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-2293GitHub issuePublicReceived

Splash screen displays off-centered in some setups

Reported by ryanrhughes · filed Jul 12, 2025Closed upstream on 2025-08-03 by its own reporter ryanrhughes. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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?
Not yet mapped to any requirement or component.
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?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

Splash screen displays off-centered in some setupsrevision 1 · captured 2026-10-04 11:26 UTC via poll

Some users have encountered the splash screen showing off-centered. This is a documented issue that can occur (ref: https://wiki.archlinux.org/title/Plymouth#Display_is_not_centered) and seems to be caused when 2 monitors are enabled but have mismatched resolutions.

Possible solution is to use something like the below code (credit @anoldguy) to discover the displays and intelligently set a configuration during install. Eg. we can probably assume the highest resolution monitor is the primary display we should show the loader on.

for dev in /sys/class/drm/card*; do
    if [ -f "$dev/status" ]; then
        status=$(cat "$dev/status" | tr -d '[:space:]')
        if [ "$status" = "connected" ]; then
            echo "$dev"
            edid-decode -n -s "$dev/edid" | tail -n 1
        fi
    fi
done

cat /sys/class/drm/card1-DP-1/enabled

Examples

<!-- Failed to upload "image.png" -->
Screenshot Source - 2 Monitors, Left is 1080 144hz, Right is 1440p 170Hz

When I boot the laptop that has a 2880 panel and it's connected to a 4k screen, the scaling is off, too

View raw text
Some users have encountered the splash screen showing off-centered. This is a documented issue that can occur (ref: https://wiki.archlinux.org/title/Plymouth#Display_is_not_centered) and seems to be caused when 2 monitors are enabled but have mismatched resolutions. 

Possible solution is to use something like the below code (credit @anoldguy) to discover the displays and intelligently set a configuration during install. Eg. we can probably assume the highest resolution monitor is the primary display we should show the loader on.

```
for dev in /sys/class/drm/card*; do
    if [ -f "$dev/status" ]; then
        status=$(cat "$dev/status" | tr -d '[:space:]')
        if [ "$status" = "connected" ]; then
            echo "$dev"
            edid-decode -n -s "$dev/edid" | tail -n 1
        fi
    fi
done
```

`cat /sys/class/drm/card1-DP-1/enabled`

### Examples
<!-- Failed to upload "image.png" -->
[Screenshot Source](https://discordapp.com/channels/1390012484194275541/1390012487000395859/1392837767658082435) - 2 Monitors, Left is 1080 144hz, Right is 1440p 170Hz

[When I boot the laptop that has a 2880 panel and it's connected to a 4k screen, the scaling is off, too](https://discordapp.com/channels/1390012484194275541/1390012487000395859/1392837929218474045)

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.

No decision has been recorded yet.