Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Double Login Prompt Issue with Hyprland and SDDM
Reported by maietta · filed Oct 8, 2025Closed upstream on 2025-10-25 by ryanrhughes. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
What's wrong?
Double Login Prompt Issue with Hyprland and SDDM
Issue Summary
Users experience two consecutive login prompts when logging into Omarchy Linux with Hyprland and SDDM:
1. Standard SDDM login screen
2. Additional login prompt from uwsm (Universal Wayland Session Manager)
Root Cause: The Omarchy update system creates a hyprland-uwsm.desktop file that causes SDDM to prefer uwsm-managed sessions, creating nested session management.
Environment
- OS: Omarchy Linux
- Display Manager: SDDM
- Window Manager: Hyprland
- Session Manager: uwsm (Universal Wayland Session Manager)
- Update System: Omarchy built-in update mechanism
Steps to Reproduce
- Boot system to SDDM login screen
- Enter valid credentials and log in
- Observe second login prompt appearing after initial login
- Must log in again to access Hyprland session
Expected Behavior
After logging in via SDDM, Hyprland session should start directly without additional login prompts.
Actual Behavior
Two login prompts are required:
1. SDDM login screen (normal)
2. uwsm-managed session login prompt (unexpected)
Root Cause Analysis
Timeline of Events:
- September 14, 2025: uwsm package installed as part of system setup
- October 3, 2025: Omarchy update system created
hyprland-uwsm.desktopfile - October 3, 2025: SDDM began preferring uwsm-managed session, causing double login
Technical Details:
The issue stems from having two Hyprland desktop entries:
- /usr/share/wayland-sessions/hyprland.desktop (standard)
- /usr/share/wayland-sessions/hyprland-uwsm.desktop (uwsm-managed - created by Omarchy)
Key Evidence:
- The hyprland-uwsm.desktop file was NOT part of the original uwsm package
- File creation date: October 3, 2025 at 06:02:19
- Omarchy update system found at /home/nick/.local/share/omarchy/bin/omarchy-update
- Omarchy has uwsm configuration at /home/nick/.local/share/omarchy/config/uwsm/
- No pacman hooks or manual creation involved
SDDM is selecting the uwsm-managed session, which creates a nested session management scenario.
System Information
Operating System
$ uname -a
Linux omarchy 6.16.10-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 02 Oct 2025 19:26:36 +0000 x86_64 GNU/Linux
$ cat /etc/os-release
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rollingSystem Components
# Display Manager & Window Manager
$ pacman -Q sddm hyprland uwsm
sddm 0.21.0-6
hyprland 0.51.1-2
uwsm 0.23.3-1
# Session Information
$ echo $XDG_SESSION_TYPE
wayland
$ echo $XDG_CURRENT_DESKTOP
Hyprland
# Systemd Version
$ systemctl --version
systemd 258 (258-4-arch)Hardware
# CPU & Memory
$ lscpu | head -5
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 39 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 8
$ free -h
total used free shared buff/cache available
Mem: 31Gi 6.5Gi 18Gi 2.0Gi 8.8Gi 24Gi
Swap: 4.0Gi 0B 4.0GiDisplay Manager Status
$ systemctl status display-manager --no-pager -l
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; preset: disabled)
Active: active (running) since Wed 2025-10-08 07:41:53 PDT; 59min ago
Main PID: 900 (sddm)
Memory: 344.4M (peak: 349.9M)Available Sessions
$ ls -la /usr/share/wayland-sessions/
-rw-r--r-- 190 root 3 Oct 06:02 hyprland-uwsm.desktop
-rw-r--r-- 176 root 3 Oct 06:02 hyprland.desktopDesktop Entry Contents
hyprland.desktop:
[Desktop Entry]
Name=Hyprland
Comment=An intelligent dynamic tiling Wayland compositor
Exec=Hyprland
Type=Application
DesktopNames=Hyprland
Keywords=tiling;wayland;compositor;hyprland-uwsm.desktop:
[Desktop Entry]
Name=Hyprland (uwsm-managed)
Comment=An intelligent dynamic tiling Wayland compositor
Exec=uwsm start -- hyprland.desktop
TryExec=uwsm
DesktopNames=Hyprland
Type=ApplicationSDDM Logs
Oct 08 07:42:12 omarchy sddm[900]: Reading from "/usr/share/wayland-sessions/hyprland-uwsm.desktop"
Oct 08 07:42:12 omarchy sddm[900]: Session "/usr/share/wayland-sessions/hyprland-uwsm.desktop" selected, command: "uwsm start -- hyprland.desktop" for VT 1
Oct 08 07:42:12 omarchy sddm-helper[1910]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "uwsm start -- hyprland.desktop"Proposed Solutions
Solution 1: Remove uwsm-managed desktop file (Recommended)
# Remove the problematic desktop file created by Omarchy
sudo rm /usr/share/wayland-sessions/hyprland-uwsm.desktopSolution 2: Disable uwsm-managed session (Alternative)
# Rename to disable instead of removing
sudo mv /usr/share/wayland-sessions/hyprland-uwsm.desktop /usr/share/wayland-sessions/hyprland-uwsm.desktop.disabledSolution 3: Configure SDDM to prefer standard session
Create /etc/sddm.conf:
[General]
SessionCommand=/usr/share/sddm/scripts/wayland-session
SessionDir=/usr/share/wayland-sessions
Session=hyprland.desktopSolution 4: Check uwsm configuration
uwsm selectSupporting Evidence
SDDM Logs (Current Session):
Oct 08 07:42:12 omarchy sddm[900]: Reading from "/usr/share/wayland-sessions/hyprland-uwsm.desktop"
Oct 08 07:42:12 omarchy sddm[900]: Session "/usr/share/wayland-sessions/hyprland-uwsm.desktop" selected, command: "uwsm start -- hyprland.desktop" for VT 1
Oct 08 07:42:12 omarchy sddm-helper[1910]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "uwsm start -- hyprland.desktop"Desktop File Evidence:
$ ls -la /usr/share/wayland-sessions/hyprland*.desktop
-rw-r--r-- 190 root 3 Oct 06:02 /usr/share/wayland-sessions/hyprland-uwsm.desktop
-rw-r--r-- 176 root 3 Oct 06:02 /usr/share/wayland-sessions/hyprland.desktopPackage Installation Timeline:
# uwsm installed on September 14, 2025
[2025-09-14T19:16:03-0700] [ALPM] installed uwsm (0.23.3-1)
# Desktop file created on October 3, 2025 (not by package)
File: /usr/share/wayland-sessions/hyprland-uwsm.desktop
Modify: 2025-10-03 06:02:19.000000000 -0700Systemd Service Evidence:
● [email protected] - Main service for Hyprland
Main PID: 2105 (Hyprland)
CGroup: /user.slice/user-1000.slice/[email protected]/session.slice/[email protected]Omarchy Update System Investigation
Files Found:
- Update Script:
/home/nick/.local/share/omarchy/bin/omarchy-update - uwsm Config:
/home/nick/.local/share/omarchy/config/uwsm/ - Migration System:
/home/nick/.local/share/omarchy/migrations/(100+ migration scripts)
Evidence:
- Omarchy has built-in uwsm integration
- Migration system runs during updates
- Desktop file creation timestamp matches user's update activity
- No manual intervention or pacman hooks involved
Repository Investigation:
- Cloned Omarchy repository: No script found that creates
hyprland-uwsm.desktop - uwsm integration: Found in
omarchy/config/uwsm/with environment setup - Migration system:
omarchy/bin/omarchy-migrateruns scripts during updates - uwsm usage: Found in
omarchy/install/login/plymouth.shand migration scripts - Conclusion: Desktop file creation is likely from a dynamic migration script or uwsm package behavior not in the main repository
Impact
- Severity: Medium
- Frequency: Always (100% reproducible)
- User Experience: Significantly degraded due to double authentication requirement
Additional Context
This issue is specifically related to the Omarchy update system creating desktop files that conflict with SDDM's session management. The Omarchy update system appears to have a migration or configuration script that creates the hyprland-uwsm.desktop file during updates, causing SDDM to prefer uwsm-managed sessions over standard Hyprland sessions.
Investigation Notes:
- User only used normal applications (Cursor, web browsing, music) on October 3rd
- No manual system configuration or package installation
- Omarchy update system has extensive migration scripts (100+ files)
- uwsm integration is built into Omarchy's configuration system
Labels
bughyprlandsddmsession-managementuser-experienceomarchy-update-systemuwsm-integration
Priority
Medium - Affects user experience but has workarounds available. Issue is caused by Omarchy's update system, not user error.
View raw text
### What's wrong?
# Double Login Prompt Issue with Hyprland and SDDM
## Issue Summary
Users experience two consecutive login prompts when logging into Omarchy Linux with Hyprland and SDDM:
1. Standard SDDM login screen
2. Additional login prompt from uwsm (Universal Wayland Session Manager)
**Root Cause**: The Omarchy update system creates a `hyprland-uwsm.desktop` file that causes SDDM to prefer uwsm-managed sessions, creating nested session management.
## Environment
- **OS**: Omarchy Linux
- **Display Manager**: SDDM
- **Window Manager**: Hyprland
- **Session Manager**: uwsm (Universal Wayland Session Manager)
- **Update System**: Omarchy built-in update mechanism
## Steps to Reproduce
1. Boot system to SDDM login screen
2. Enter valid credentials and log in
3. Observe second login prompt appearing after initial login
4. Must log in again to access Hyprland session
## Expected Behavior
After logging in via SDDM, Hyprland session should start directly without additional login prompts.
## Actual Behavior
Two login prompts are required:
1. SDDM login screen (normal)
2. uwsm-managed session login prompt (unexpected)
## Root Cause Analysis
### Timeline of Events:
1. **September 14, 2025**: uwsm package installed as part of system setup
2. **October 3, 2025**: Omarchy update system created `hyprland-uwsm.desktop` file
3. **October 3, 2025**: SDDM began preferring uwsm-managed session, causing double login
### Technical Details:
The issue stems from having two Hyprland desktop entries:
- `/usr/share/wayland-sessions/hyprland.desktop` (standard)
- `/usr/share/wayland-sessions/hyprland-uwsm.desktop` (uwsm-managed - created by Omarchy)
**Key Evidence**:
- The `hyprland-uwsm.desktop` file was **NOT** part of the original uwsm package
- File creation date: October 3, 2025 at 06:02:19
- Omarchy update system found at `/home/nick/.local/share/omarchy/bin/omarchy-update`
- Omarchy has uwsm configuration at `/home/nick/.local/share/omarchy/config/uwsm/`
- No pacman hooks or manual creation involved
SDDM is selecting the uwsm-managed session, which creates a nested session management scenario.
## System Information
### Operating System
```bash
$ uname -a
Linux omarchy 6.16.10-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 02 Oct 2025 19:26:36 +0000 x86_64 GNU/Linux
$ cat /etc/os-release
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
```
### System Components
```bash
# Display Manager & Window Manager
$ pacman -Q sddm hyprland uwsm
sddm 0.21.0-6
hyprland 0.51.1-2
uwsm 0.23.3-1
# Session Information
$ echo $XDG_SESSION_TYPE
wayland
$ echo $XDG_CURRENT_DESKTOP
Hyprland
# Systemd Version
$ systemctl --version
systemd 258 (258-4-arch)
```
### Hardware
```bash
# CPU & Memory
$ lscpu | head -5
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 39 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 8
$ free -h
total used free shared buff/cache available
Mem: 31Gi 6.5Gi 18Gi 2.0Gi 8.8Gi 24Gi
Swap: 4.0Gi 0B 4.0Gi
```
### Display Manager Status
```bash
$ systemctl status display-manager --no-pager -l
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; preset: disabled)
Active: active (running) since Wed 2025-10-08 07:41:53 PDT; 59min ago
Main PID: 900 (sddm)
Memory: 344.4M (peak: 349.9M)
```
### Available Sessions
```bash
$ ls -la /usr/share/wayland-sessions/
-rw-r--r-- 190 root 3 Oct 06:02 hyprland-uwsm.desktop
-rw-r--r-- 176 root 3 Oct 06:02 hyprland.desktop
```
## Desktop Entry Contents
**hyprland.desktop:**
```ini
[Desktop Entry]
Name=Hyprland
Comment=An intelligent dynamic tiling Wayland compositor
Exec=Hyprland
Type=Application
DesktopNames=Hyprland
Keywords=tiling;wayland;compositor;
```
**hyprland-uwsm.desktop:**
```ini
[Desktop Entry]
Name=Hyprland (uwsm-managed)
Comment=An intelligent dynamic tiling Wayland compositor
Exec=uwsm start -- hyprland.desktop
TryExec=uwsm
DesktopNames=Hyprland
Type=Application
```
## SDDM Logs
```
Oct 08 07:42:12 omarchy sddm[900]: Reading from "/usr/share/wayland-sessions/hyprland-uwsm.desktop"
Oct 08 07:42:12 omarchy sddm[900]: Session "/usr/share/wayland-sessions/hyprland-uwsm.desktop" selected, command: "uwsm start -- hyprland.desktop" for VT 1
Oct 08 07:42:12 omarchy sddm-helper[1910]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "uwsm start -- hyprland.desktop"
```
## Proposed Solutions
### Solution 1: Remove uwsm-managed desktop file (Recommended)
```bash
# Remove the problematic desktop file created by Omarchy
sudo rm /usr/share/wayland-sessions/hyprland-uwsm.desktop
```
### Solution 2: Disable uwsm-managed session (Alternative)
```bash
# Rename to disable instead of removing
sudo mv /usr/share/wayland-sessions/hyprland-uwsm.desktop /usr/share/wayland-sessions/hyprland-uwsm.desktop.disabled
```
### Solution 3: Configure SDDM to prefer standard session
Create `/etc/sddm.conf`:
```ini
[General]
SessionCommand=/usr/share/sddm/scripts/wayland-session
SessionDir=/usr/share/wayland-sessions
Session=hyprland.desktop
```
### Solution 4: Check uwsm configuration
```bash
uwsm select
```
## Supporting Evidence
### SDDM Logs (Current Session):
```
Oct 08 07:42:12 omarchy sddm[900]: Reading from "/usr/share/wayland-sessions/hyprland-uwsm.desktop"
Oct 08 07:42:12 omarchy sddm[900]: Session "/usr/share/wayland-sessions/hyprland-uwsm.desktop" selected, command: "uwsm start -- hyprland.desktop" for VT 1
Oct 08 07:42:12 omarchy sddm-helper[1910]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "uwsm start -- hyprland.desktop"
```
### Desktop File Evidence:
```bash
$ ls -la /usr/share/wayland-sessions/hyprland*.desktop
-rw-r--r-- 190 root 3 Oct 06:02 /usr/share/wayland-sessions/hyprland-uwsm.desktop
-rw-r--r-- 176 root 3 Oct 06:02 /usr/share/wayland-sessions/hyprland.desktop
```
### Package Installation Timeline:
```bash
# uwsm installed on September 14, 2025
[2025-09-14T19:16:03-0700] [ALPM] installed uwsm (0.23.3-1)
# Desktop file created on October 3, 2025 (not by package)
File: /usr/share/wayland-sessions/hyprland-uwsm.desktop
Modify: 2025-10-03 06:02:19.000000000 -0700
```
### Systemd Service Evidence:
```bash
● [email protected] - Main service for Hyprland
Main PID: 2105 (Hyprland)
CGroup: /user.slice/user-1000.slice/[email protected]/session.slice/[email protected]
```
## Omarchy Update System Investigation
### Files Found:
- **Update Script**: `/home/nick/.local/share/omarchy/bin/omarchy-update`
- **uwsm Config**: `/home/nick/.local/share/omarchy/config/uwsm/`
- **Migration System**: `/home/nick/.local/share/omarchy/migrations/` (100+ migration scripts)
### Evidence:
- Omarchy has built-in uwsm integration
- Migration system runs during updates
- Desktop file creation timestamp matches user's update activity
- No manual intervention or pacman hooks involved
### Repository Investigation:
- **Cloned Omarchy repository**: No script found that creates `hyprland-uwsm.desktop`
- **uwsm integration**: Found in `omarchy/config/uwsm/` with environment setup
- **Migration system**: `omarchy/bin/omarchy-migrate` runs scripts during updates
- **uwsm usage**: Found in `omarchy/install/login/plymouth.sh` and migration scripts
- **Conclusion**: Desktop file creation is likely from a **dynamic migration script** or **uwsm package behavior** not in the main repository
## Impact
- **Severity**: Medium
- **Frequency**: Always (100% reproducible)
- **User Experience**: Significantly degraded due to double authentication requirement
## Additional Context
This issue is specifically related to the **Omarchy update system** creating desktop files that conflict with SDDM's session management. The Omarchy update system appears to have a migration or configuration script that creates the `hyprland-uwsm.desktop` file during updates, causing SDDM to prefer uwsm-managed sessions over standard Hyprland sessions.
### Investigation Notes:
- User only used normal applications (Cursor, web browsing, music) on October 3rd
- No manual system configuration or package installation
- Omarchy update system has extensive migration scripts (100+ files)
- uwsm integration is built into Omarchy's configuration system
## Labels
- `bug`
- `hyprland`
- `sddm`
- `session-management`
- `user-experience`
- `omarchy-update-system`
- `uwsm-integration`
## Priority
Medium - Affects user experience but has workarounds available. Issue is caused by Omarchy's update system, not user error.
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.