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.
GUI applications freeze when attempting to print (CUPS works via command line)
Reported by clwalker85 · filed Dec 6, 2025Closed upstream on 2026-01-20 by its own reporter clwalker85. GitHub close reason: completed. Closed by its own reporter — not by itself 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
System details
Omarchy 3.2.2, Canon MF210 Series
What's wrong?
Environment:
┌──────────────────────Hardware──────────────────────┐
│ ├: AMD Ryzen 7 2700 (16) @ 3.20 GHz
│ ├: AMD Radeon RX 580 Series [Discrete]
│ ├: 3840x2160 @ 1.6x in 32", 60 Hz [External]
│ ├: 593.26 GiB / 929.50 GiB (64%) - btrfs
│ ├: 3.24 GiB / 31.26 GiB (10%)
└ └ : 0 B / 4.00 GiB (0%)
└──────────────────────────────────────────────────┘
┌──────────────────────Software──────────────────────┐
OS: Omarchy 3.2.2
│ ├: master
│ ├: stable
│ ├: Linux 6.17.9-arch1-1
│ ├: Hyprland 0.52.1 (Wayland)
│ ├: ghostty 1.2.3-arch2
│ ├: 1048 (pacman)
│ ├: Matte Black ●●●●●●●●
└ └: Liberation Mono (9pt)
└────────────────────────────────────────────────────┘
┌────────────────Age / Uptime / Update───────────────┐
OS Age: 7 days
Uptime: 5 mins
Update: Saturday, November 29 2025 at 16:36
└─────────────────────────────────────────────┘
Issue Description:
All GUI applications freeze indefinitely when attempting to print, despite CUPS functioning correctly via command line and direct CUPS operations working fine.
What Works:
✅ Command-line printing: lp -d Canon_MF210 /usr/share/cups/data/testprint prints successfully
✅ CUPS web interface (localhost:631) functions normally
✅ system-config-printer GUI opens and can print test pages successfully
✅ Printer is reachable on network (ping succeeds)
✅ CUPS service is running without errors
What Doesn't Work:
❌ Chromium: Print preview loads but clicking "Print" button shows "Printing..." indefinitely with no print job created
❌ Document Viewer (Evince): Freezes completely when print dialog is opened, requires force termination
❌ Zathura: Freezes when executing print command
❌ All GUI applications exhibit the same freeze behavior when attempting to print
Setup Steps Taken:
Initial CUPS installation:
bash sudo pacman -S cups cups-pdf avahi
sudo systemctl enable --now cups
sudo systemctl enable --now avahi-daemon
2. **Driver installation:**
- Installed `cndrvcups-lb` from AUR (Canon UFR II LT driver)
3. **Printer configuration attempts:**
- First attempt: Added printer via CUPS web interface using "Canon MF210 Series - IPP Everywhere" (driverless)
- Second attempt: Removed printers, re-added using Canon-specific driver `CNRCUPSMF210ZK.ppd` (Canon MF210 Series UFR II LT)
- Third attempt: Changed from network discovery (`dnssd://`) to direct socket connection (`socket://redacted)
4. **Troubleshooting steps performed:**
- Added user to `lp` group: `sudo usermod -aG lp redacted`
- Disabled cups-browsed: `sudo systemctl stop cups-browsed && sudo systemctl disable cups-browsed`
- Installed GTK print backends: `sudo pacman -S gtk3-print-backends`
- Installed alternative portal: `sudo pacman -S xdg-desktop-portal-gtk`
- Set default printer: `lpoptions -d Canon_MF210`
- Attempted GTK print backend configuration in `~/.config/gtk-3.0/settings.ini`
- Attempted environment variables in `~/.config/environment.d/gtk-print.conf`: GTK_PRINT_BACKEND=cups
GTK_USE_PORTAL=0
- Multiple reboots after each configuration change
**Technical Details:**
When using `strace` on a frozen Evince process, it shows an infinite loop:poll([{fd=23, events=POLLIN}], 1, 0) = 1 ([{fd=23, revents=POLLIN}])
The process is stuck waiting for data on a file descriptor that never arrives.
CUPS Status:
bashlpstat -t
Output shows:
Scheduler running
Printer idle and accepting requests
No stuck print jobs
Device URI: socket://redacted
System Logs:
No errors appear in sudo journalctl -u cups when attempting to print from GUI applications.
Current Workaround:
Using command-line printing works perfectly:
bashlp filename.pdf
Suspected Root Cause:
This appears to be a GTK/Qt print dialog communication issue specific to Hyprland/Wayland environments. The print dialog attempts to query printer capabilities or communicate with CUPS but hangs indefinitely, while direct CUPS operations (via command line or system-config-printer's internal methods) work without issue.
Additional Context:
Chromium verbose logging showed the print process stops at "Updating print settings via service for Canon_MF210"
Multiple evince processes spawn during print attempts and die/restart
The Ctrl+Shift+P system print dialog in Chromium also causes a complete freeze requiring process termination
File descriptor 23 in frozen processes shows various states (wayland cursor, sockets) but never resolves
View raw text
### System details
Omarchy 3.2.2, Canon MF210 Series
### What's wrong?
Environment:
┌──────────────────────Hardware──────────────────────┐
│ ├: AMD Ryzen 7 2700 (16) @ 3.20 GHz
│ ├: AMD Radeon RX 580 Series [Discrete]
│ ├: 3840x2160 @ 1.6x in 32", 60 Hz [External]
│ ├: 593.26 GiB / 929.50 GiB (64%) - btrfs
│ ├: 3.24 GiB / 31.26 GiB (10%)
└ └ : 0 B / 4.00 GiB (0%)
└──────────────────────────────────────────────────┘
┌──────────────────────Software──────────────────────┐
OS: Omarchy 3.2.2
│ ├: master
│ ├: stable
│ ├: Linux 6.17.9-arch1-1
│ ├: Hyprland 0.52.1 (Wayland)
│ ├: ghostty 1.2.3-arch2
│ ├: 1048 (pacman)
│ ├: Matte Black ●●●●●●●●
└ └: Liberation Mono (9pt)
└────────────────────────────────────────────────────┘
┌────────────────Age / Uptime / Update───────────────┐
OS Age: 7 days
Uptime: 5 mins
Update: Saturday, November 29 2025 at 16:36
└─────────────────────────────────────────────┘
Issue Description:
All GUI applications freeze indefinitely when attempting to print, despite CUPS functioning correctly via command line and direct CUPS operations working fine.
What Works:
✅ Command-line printing: lp -d Canon_MF210 /usr/share/cups/data/testprint prints successfully
✅ CUPS web interface (localhost:631) functions normally
✅ system-config-printer GUI opens and can print test pages successfully
✅ Printer is reachable on network (ping succeeds)
✅ CUPS service is running without errors
What Doesn't Work:
❌ Chromium: Print preview loads but clicking "Print" button shows "Printing..." indefinitely with no print job created
❌ Document Viewer (Evince): Freezes completely when print dialog is opened, requires force termination
❌ Zathura: Freezes when executing print command
❌ All GUI applications exhibit the same freeze behavior when attempting to print
Setup Steps Taken:
Initial CUPS installation:
bash sudo pacman -S cups cups-pdf avahi
sudo systemctl enable --now cups
sudo systemctl enable --now avahi-daemon
```
2. **Driver installation:**
- Installed `cndrvcups-lb` from AUR (Canon UFR II LT driver)
3. **Printer configuration attempts:**
- First attempt: Added printer via CUPS web interface using "Canon MF210 Series - IPP Everywhere" (driverless)
- Second attempt: Removed printers, re-added using Canon-specific driver `CNRCUPSMF210ZK.ppd` (Canon MF210 Series UFR II LT)
- Third attempt: Changed from network discovery (`dnssd://`) to direct socket connection (`socket://redacted)
4. **Troubleshooting steps performed:**
- Added user to `lp` group: `sudo usermod -aG lp redacted`
- Disabled cups-browsed: `sudo systemctl stop cups-browsed && sudo systemctl disable cups-browsed`
- Installed GTK print backends: `sudo pacman -S gtk3-print-backends`
- Installed alternative portal: `sudo pacman -S xdg-desktop-portal-gtk`
- Set default printer: `lpoptions -d Canon_MF210`
- Attempted GTK print backend configuration in `~/.config/gtk-3.0/settings.ini`
- Attempted environment variables in `~/.config/environment.d/gtk-print.conf`:
```
GTK_PRINT_BACKEND=cups
GTK_USE_PORTAL=0
```
- Multiple reboots after each configuration change
**Technical Details:**
When using `strace` on a frozen Evince process, it shows an infinite loop:
```
poll([{fd=23, events=POLLIN}], 1, 0) = 1 ([{fd=23, revents=POLLIN}])
The process is stuck waiting for data on a file descriptor that never arrives.
CUPS Status:
bashlpstat -t
Output shows:
Scheduler running
Printer idle and accepting requests
No stuck print jobs
Device URI: socket://redacted
System Logs:
No errors appear in sudo journalctl -u cups when attempting to print from GUI applications.
Current Workaround:
Using command-line printing works perfectly:
bashlp filename.pdf
Suspected Root Cause:
This appears to be a GTK/Qt print dialog communication issue specific to Hyprland/Wayland environments. The print dialog attempts to query printer capabilities or communicate with CUPS but hangs indefinitely, while direct CUPS operations (via command line or system-config-printer's internal methods) work without issue.
Additional Context:
Chromium verbose logging showed the print process stops at "Updating print settings via service for Canon_MF210"
Multiple evince processes spawn during print attempts and die/restart
The Ctrl+Shift+P system print dialog in Chromium also causes a complete freeze requiring process termination
File descriptor 23 in frozen processes shows various states (wayland cursor, sockets) but never resolvesValidation
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.