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.
Automatically update Nautilus gtk.css on theme switch or installation
Reported by HANCORE-linux · filed Oct 25, 2025Closed upstream on 2025-12-02 by its own reporter HANCORE-linux. 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
What do you need?
Description:
Nautilus does not currently refresh its gtk.css automatically when a new theme is installed or when switching between themes. This enhancement proposes adding a small script integration to ensure that Nautilus always reflects the selected theme immediately
Suggested solution:
Add a call to omarchy-theme-set-nautilus in:
~/.local/share/omarchy/bin/omarchy-theme-setomarchy-theme-set-nautilusThen add the script omarchy-theme-set-nautilus in:
~/.local/share/omarchy/bin/ Script:
#!/bin/bash
# This script applies the Omarchy GTK theme to Nautilus.
# Source and destination paths
SOURCE_THEME="$HOME/.config/omarchy/current/theme/gtk.css"
DEST_GTK4_DIR="$HOME/.config/gtk-4.0"
DEST_THEME="$DEST_GTK4_DIR/gtk.css"
# Create the GTK-4.0 directory if it doesn't exist
mkdir -p "$DEST_GTK4_DIR"
# Copy the theme file
if [ -f "$SOURCE_THEME" ]; then
cp "$SOURCE_THEME" "$DEST_THEME"
echo "Theme copied successfully."
else
echo "Source theme file not found: $SOURCE_THEME"
exit 1
fi
# Restart Nautilus to apply the changes
pkill nautilus
echo "Nautilus restarted."This script makes sure Nautilus updates its gtk.css automatically after each theme switch or installation.
Credits:
Solution tested and provided by Michael91 (Discord: Michael91#9276)
https://github.com/user-attachments/assets/e86293ff-abda-4294-be1f-2c932374d894
View raw text
### What do you need?
**Description:**
Nautilus does not currently refresh its gtk.css automatically when a new theme is installed or when switching between themes. This enhancement proposes adding a small script integration to ensure that Nautilus always reflects the selected theme immediately
_Suggested solution:_
Add a call to omarchy-theme-set-nautilus in:
```bash
~/.local/share/omarchy/bin/omarchy-theme-set
```
```bash
omarchy-theme-set-nautilus
```
Then add the script omarchy-theme-set-nautilus in:
```bash
~/.local/share/omarchy/bin/
```
Script:
```bash
#!/bin/bash
# This script applies the Omarchy GTK theme to Nautilus.
# Source and destination paths
SOURCE_THEME="$HOME/.config/omarchy/current/theme/gtk.css"
DEST_GTK4_DIR="$HOME/.config/gtk-4.0"
DEST_THEME="$DEST_GTK4_DIR/gtk.css"
# Create the GTK-4.0 directory if it doesn't exist
mkdir -p "$DEST_GTK4_DIR"
# Copy the theme file
if [ -f "$SOURCE_THEME" ]; then
cp "$SOURCE_THEME" "$DEST_THEME"
echo "Theme copied successfully."
else
echo "Source theme file not found: $SOURCE_THEME"
exit 1
fi
# Restart Nautilus to apply the changes
pkill nautilus
echo "Nautilus restarted."
```
This script makes sure Nautilus updates its gtk.css automatically after each theme switch or installation.
Credits:
Solution tested and provided by Michael91 (Discord: Michael91#9276)
https://github.com/user-attachments/assets/e86293ff-abda-4294-be1f-2c932374d894- e86293ff-abda-4294-be1f-2c932374d894
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.